That's C: The Debugging Trauma

v later found out with more debugging that it happened because the module in question cast that struct back from memory, and then added its own stuff to it. So any changes to it are breaking changes. Mind you: followed the best practices we learned from our Linux days where everything is done in small, self contained commits. Sounds overkill for these days, but had we committed everything in one big patch, it would have taken days for us to figure out what was wrong. I code very little these days, now that is in a more advanced stage. And I haven't coded C in 10 years. But I didn't reason this was the issue. I didn't have to. My body just uttered it. As an instinctive reaction, as an abuse victim to the sight of the abuser. It is something that just becomes a part of you, and never leaves. It just haunts you forever. It kills your innocence, makes you jaded. Life is never the same. That's C.

A dark screenshot of a long social-media-style text post about debugging a C module that corrupts or changes a struct after casting it back from memory. The writer compares the instinctive recognition of the bug to an abuse victim recognizing an abuser, then jokes that C programming trauma permanently destroys your innocence. It is shared as a reaction to painful legacy code, debugging nightmares, and the uniquely traumatic experience of working in C.

• @gentoomemes / 9391 2024-02-14