- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
Naw. Not knowing pisses me off. I’m gonna have to deal with it again in the future, probably, so might as well set some time aside to figure out wtf is happening.
Exactly this. If you don’t know, it’s broken.
i used to believe in this; but then i learned the hard way that old/opaque code is gross game of hot potato where you will pay the price if your social standing in your organization isn’t privileged enough.
Guess I was lucky to have a social standing privileged enough, as a junior dev.
But also, probably because they actually required determinism, with it being critical and all.
The only thing worse than code that should be working not working is code where you’re sure it won’t work, but then it actually works!
Managers, engineers and programmers:
An engineer, a programmer and their manager are driving back from lunch. Suddenly the brakes fail on a hill. The manager frantically swerves back and forth to slow the car down, rubs against the curb, drives onto some grass and finally gets it stopped. They all get out. The manager pulls out his phone and says, “I’ll call for a tow truck to take it to a garage that has a factory-certified mechanic who can fix it.” The engineer crawls under the car and says, “No wait, I think I can fix it!” The programmer says, “First let’s get back in the car and see if we can make it happen again!”
It’s been a while since I’ve coded but I do remember removing a comment and it broke the code. That shit is voodoo.
