It’s all fun and games until you have to implement
goingToCrashIntoEachOther()// TODO: needs improvements but works 99% of the timereturn false;This looks good. PR approved.
return (staticCrashCounter++ % 100 == 0 ? true : false);
To improve that, you could get rid of the comment to save space.
void dont() { fuckenNoseDiveLmao(); }Did a Japanese lunar probe write this?
You leaked the code for when it’s out of warranty
Or when your subscription to braking has lapsed.
Love me some clean code. Just please don’t look at the function definition or ever expect me to change my pyramid of abstractions.
That’s what interns are for.
for the person who wrote that “coding and algorithms” is the same as “magic and alchemy”
I work in IT. My boss is by all accounts very competent in both programming and administration, yet all his documentation basically says “remember to set DoTheRightThing=True”
Edit: I just looked up the documentation for an internal service and under “Error recovery” it just says “The output of command xy should make sense”. fml
