No Docs No Tests

Content Q: When I was 4, my sister was 2. 1 am now 44. How old is my sister? Programmer: 44 - (4 - 2) 42 Tester: When I was 4, my sister was 2. I am now 44. How old is my sister? O Answer Follow 97 Request o 100 Answers 5 Samuel Lipoff, studied at Harvard University Updated 17h ago This is a tough one. She might be 42, but she could be 41 or 43 also, since you don't say when your birthday is and her birthday is. Also, she could be dead. Finally, you might have thought she was your sister but actually your mom had an affair with another man and the woman who is 1-3 years younger than you is not actually your sister. But your mom may have given away your real sister for adoption, in which case she's probably older than you. See why it's tough? Finally, what if you think your sister is dead, but she actually has become an astronaut on a secret government project for near light-speed travel? Then your sister would be aging more slowly than you, so she could potentially be even younger than 41.

Content 3rd 1 help JavaScript Engineers Become ... 4d 6 Don't review then merge. Follow Merge then review. Letting code become stale for any amount of time is anti-collaboration pattern and it slows down performance, moral and only seeks to use the stick instead of the carrot! Build a culture of trust around xtreme programming practices; namely continuous integration. Nothing to stop you asking a colleague to submit improvements after the fact. git ? 335 206 comments 9 reposts Like ProdrammerHumor.io Comment Repost Send

Content Users thinking it is safe to use the app Me fixing bugs on Production

Content WHEN THE APP IS STILL GIVING ERROR BUTIT'S FINALLY AN ERROR YOU EXPECT TO SEE

When faced with a mysterious bug, there are two types of developers in this world: those who use proper debugging tools and those who frantically scatter print() statements like confetti at a parade. Let's be honest—we've all smashed that red button at 2AM while muttering "just one more print statement should reveal the problem" for the 47th time. Sure, debuggers exist with their fancy breakpoints and variable inspection, but nothing beats the primal satisfaction of watching your terminal fill up with print("HERE") , print("WHY GOD WHY") , and the classic print("AAAAAAAAAA") . Debuggers are for people with time management skills. Print statements are for the rest of us heroes.

The eternal paradox of software development in two panels: Top panel: Code inexplicably fails despite your flawless logic. You stare at the screen, questioning your career choices and possibly the laws of physics. Bottom panel: The exact same code suddenly works without any changes. Now you're even more confused because you've been robbed of the satisfaction of fixing something. The true horror isn't when code doesn't work—it's when it starts working and you have absolutely no idea why. Now you live in fear that it'll break again the moment you deploy to production.