The Expectation Vs. Reality Of Running Your Code

Content My brain after 8 hours of sleep My brain after 4 hours of sleep I just added 15 new classes, 28 integration tests, and have 80 code coverage ProdrammerHumor.io Help, the compiler is saying "Syntax Error"

Content There's a thing called "Rubber duck debugging" in which a programmer explains the code to a rubber duck in hopes of finding the bug Ultrafacts tumblr. farm ultrafacts Source I absorr Some of you are reblogging because you think its funny that programmers would talk to ducks. I'm reblogging because I think its funny picturing a programmer explaining their code, realizing what they did when they explain the bad code, then grabbing the strangling the duck while yelling "WHY WAS THE FIX THAT SIMPLE!? AM I GOING BLIND!" monobeartheater AS A PROGRAMMER I CAN TELL YOU THAT THIS IS EXACTLY WHAT YOU FUCKING DO WE HAD TO BAN THE DUCKS FROM MY CLASSES BECAUSE EVERYONE WOULD FLIP THE DUCK OR THROW IT AT A WALL OR SOMETHING WHEN THEY FIGURED OUT THE PROBLEM IN THEIR CODE kierenwalkerpds so that's the function of a rubber duck lifeofdavo work at a startup and part of the onboarding package you get when you first start working here now includes a rubber duck. We also have a bigger version of the duck for the extra hard problems. Sometimes one duck doesn't cut it and you need to borrow vour neighbors to get more dUcks on the problem. one time we couldn't figure out why something wasn't working right so we assembled the counsel of ducks and by the grace of the Duck Gods were we able to finally come to a solution. These ducks have saved many lives and should be respected for the heroes they are.

The classic developer blame game in its natural habitat! The backend dev secretly passes a note with their broken code to the frontend dev, who opens it only to find the dreaded "500 Internal Server Error." The frontend dev's face says it all—pure rage at being handed a server problem they can't fix but will absolutely get blamed for when users start complaining. It's like ordering a pizza and receiving an empty box with a note saying "we're out of ingredients, you figure it out." The eternal backend-frontend relationship summarized in two panels of pure frustration.

The classic developer mantra: "Nobody is going to die if you write bad software" paired with "Faking it till you make it should probably be fine" and a dead platypus in the middle. The perfect encapsulation of that voice in your head justifying why it's OK to push untested code to production on a Friday afternoon. Just remember, somewhere an aviation software engineer is reading this and having a panic attack.

Content OSHOULD POST BELL MEMESIUTS FUNNYI! 34 34 OHATE BELLMEMES OHATE BELL MEMES 14 14 0.1 10 score 55 2 70 85 100 115 130 2 0.1 145

Content mrsteinberg.com JANUARY 1, 2020 SOFTWARE TESTS ARE FOR MILLIONAIRES Until you are making a million a year in revenue, it is a waste of time to write tests. Your startup is going to change so much. Everything is so uncertain and failing. It makes no sense to do anything that does not directly impact revenue until you are making good money. Run though your servicesiteapp manually as a user sure. Fix the bugs that are worth fixing. You have years to refine your block of marble into David, for now just take out the big, easy chunks. Don't fall into a tech geek stereotype of always starting and never finishing. Claiming everything must be polished and tested and documented is the worst form of procrastination because it makes it sound important and a valuable use of your time. ProdrammerHumor.io