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.
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.
I do todo!() For rust and in other languages I just throw an exception. And searching for TODO comments using ripgrep.
Is my goto reminder when a comment doesn’t cut it.Works unless you already have 1000 other warnings in your project 👀
Ah, I always just write out the sentences directly so the program won’t even compile. Always works for me lol.
chaotic good
Smart way of doing it. Did something similar but in php, a while ago.
