I'm Too Old For This Tech

Content MVP FOUND IT! THIS ONE IS KINDA HOLDING ME BACK LEAVE IT, IT'S NOT HIGH PRIORITY LET'S GO FIX THE BASTARD SO, WE'RE STILL LAUNCHING NEXT WEEK? ! MONKEYUSER.COM

Ah, the four stages of revisiting your old code. First, shock and horror. Second, disbelief and confusion. Third, existential questioning of your life choices. And finally, that moment of clarity when you remember exactly what sleep-deprived, caffeine-fueled nightmare led to that particular implementation. Nothing quite like that special feeling when you realize your past self left absolutely zero comments and variable names like 'temp1', 'temp2', and the ever-helpful 'finalFinalREALLYfinal'. Your past self is always your future self's worst enemy.

The duality of programming existence captured perfectly! When you're coding for fun, you're SpongeBob sitting pretty in a comfy chair with that "I've got all the time in the world" grin. But the moment it's for a school assignment? Suddenly you're post-apocalyptic SpongeBob living in squalor, questioning your life choices and wondering if your code will compile before the heat death of the universe. The transformation from "I'll build a neural network that predicts cat behavior" to "Dear God, please let this for-loop work" happens faster than you can say "syntax error." This is why deadlines and programming mix about as well as water and sodium.

Content Jeroen Frijters JeroenFriters 1d The Dutch government was forced to release the source code of their DigiD digital authentication iOS app. It is written in C. github.comMinBZKwoo-bes... private static string GetPercentageRounds (double percentage) if percentage return "0000000000"; if percentage 0.0 88 percentage 0.1 000000000"; coercentage 1 percentage 0.2) 00000000"; percentas percentage 0.3) 0000": Goercented percentage 0.4) 00" (bercentag ntage 0.5) (bercentag 0.6) percentage 0.7) if (percentage return nancentage percentage 0.8) 00000"; ?? pencentage 0.9) return return la 1.3M O 308 171.196 0 6.678 tyrannoSaurav TyrannoSaurav Replying to JeroenFrijters Ahh I see the problem is that there are too many if statements. Here's a solution implementing binary search in O(log n) private static string GetPercentageRounds double percentage) if (percentage 66 percentage 0.5) f if (percentage 0.2) if (percentage 0.1) if (percentage return return 0000"; 0000"; return c0000": if (percentage 0.4) S if (percentage 0.3) return 000000"; return 00000": return if (percentage 0.5 86 percentage 0.9) if (percentage 0.7) if narcentare return return if (perceptage return return

The difference between amateur and professional developers in one suit-wearing meme. While you're struggling to stay awake with your Red Bull-fueled "vibe coding" sessions, this distinguished gentleman has transcended to a higher plane of existence. He doesn't just code—he codes and vibes , maintaining perfect zen while crushing 4am debugging sessions without breaking a sweat. His tie stays perfectly knotted while your hoodie is covered in energy drink stains. The "we are not the same" energy is strong with this one—like comparing someone who panic-commits directly to main versus someone who maintains a pristine git workflow while sipping Earl Grey.

This is basically how a do-while loop works in real life. First message: "I will be there in 5 minutes" (the initial statement that runs once). Second message: "If you don't?" (the condition check). Third message: "Re-read the message" (repeat the loop body). The beauty here is that unlike a while loop that checks conditions first, a do-while executes at least once before checking if it should continue—just like that promise to arrive in 5 minutes that inevitably turns into an infinite loop of excuses. The eternal programmer's time estimation paradox, but in relationship form!