C Developer Learns About Warnings

Pictured: C developer is informed about a useful warning flag. You know, I like C. I know C. It is clearly the best balance between power and usability so far designed. But three days of debugging discover I missed a "break" in a switch statement sometimes makes me want to say fuck it and go back to assembly. It's on you. One of the first priorities when working with either C or C++ should be making sure you have the right warnings enabled. '-Wimplicit-fallthrough' would have literally saved you 3 days. Listen kid. Try not to be an asshole to people who are infinitely smarter and more experienced than you will ever be. Enjoy your mute.

A Twitter-style screenshot shows a C developer proudly defending the language, then admitting that a missed break statement caused three days of debugging. Another user points out that enabling the -Wimplicit-fallthrough warning would have caught the mistake, prompting an exaggeratedly hostile response. The meme is used as a reaction to programmers rejecting helpful criticism and then muting the person who was right. EN: A Twitter-style screenshot shows a C developer proudly defending the language, then admitting that a missed break statement caused three days of debugging. Another user points out that enabling the -Wimplicit-fallthrough warning would have caught the mistake, prompting an exaggeratedly hostile response. The meme is used as a reaction to programmers rejecting helpful criticism and then muting the person who was right.

• @ithueti / 7784 2022-09-19