I was once told that I'm very thorough with commenting, and I didn't have the heart to tell them that if I didn't comment so well I'd have no idea what my code is doing.
this post was submitted on 16 Jun 2023
9 points (100.0% liked)
Programmer Humor
854 readers
11 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
Smart way of doing it. Did something close but in php, a while ago.
I’ll probably just end up commenting out whatever is causing the error lmao
That’s wonderful until you have a client asking why their pre-alpha demo that you forgot they had access to just called them a fuckwit.
Don’t ask me how I know that one :D
You too? First job, first production push (circa 1997)... a few days pass and support comes into my office with their hair on fire. "Customer is asking why the program is calling them a fucking idiot."
In a piece of code that it should have been impossible to hit, I'd put a dialog "Developer is a fucking idiot".
When I say impossible to hit, it was on the order of if (a == null && a != null ){}. Or so I thought... turns out I'd miscounted the curly braces.