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 to 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 fictionalized social-media thread shows a C developer complaining about spending three days debugging a missing “break” in a switch statement. Another programmer points out that enabling the -Wimplicit-fallthrough warning would have caught the mistake immediately, prompting an angry and insulting reply. The meme is used to mock programmers who react defensively when someone gives them technically correct advice. EN: A fictionalized social-media thread shows a C developer complaining about spending three days debugging a missing “break” in a switch statement. Another programmer points out that enabling the -Wimplicit-fallthrough warning would have caught the mistake immediately, prompting an angry and insulting reply. The meme is used to mock programmers who react defensively when someone gives them technically correct advice.

• @gentoomemes / 938 2022-09-19
• @right_wing_dev_squads / 8267 2023-12-09