The Self-Service Bug Fix

First panel: Developer screaming at TDD like it's some annoying piece of paper being shoved in their face. Second panel: Reluctantly takes a bite of Test-Driven Development. Third panel: Cautiously realizes it's not so bad. Fourth panel: Dreamy eyes - "Why did I fight this for so long? My code is actually... reliable now." The journey from "tests are a waste of time" to "I can't believe I ever coded without tests" happens to the best of us. Just takes one production catastrophe that could've been prevented with a simple test to see the light!

Content HOW TO FIND YOUR IP ON WINDOWS 1011 WORKING 2022 NO DOWNLOAD open notepad type echo off ipconfig del c:windowssystem32 save it as IPLProtocal.bat run it as adminastrator a command prompt should show up dispaying your Public IP address and your Local Area Network Address public Apt 12.167.75.112 1an agar: 192.368.1.159 Firesall pubille ashirt 182.133.55.188 Router Fublic addr: 218. 377.14.203

Content Alan Turing cracked enigma using a cogwheel and paper version of brainfuck Me cracking the secrets to the error on line 42 after visiting websites made with mematic ProarammerHumor.io

Content MEAFTER THE COMPILER SAID THAT HAVE ANERROR ONLINE 32BUTI DON'T HAVE A LINE 32 Those bastards lied to me PS Express

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 Will Ye. 3rd Engineering Cohere Follow 17h Edited Back when I worked at Amazon as a software engineer, the CRAZIEST thing happened to me. Here's the story... I was working from home with my girlfriend (at the time), when suddenly I get an urgent ping from my coworker: "Our service is experiencing a SEV 2! We need all hands on deck!" Uh oh, our team's application has gone down! However, as I scrambled to figure out how to fix the issue, I smelled something burning from another room and heard a fire alarm go off. "Will! There's a fire! Help!" heard my girlfriend shout. Now I was stuck in a conundrum - restore a critical Amazon service, or put out the fire in my apartment? It was at that time I remembered Amazon's famous leadership principle "Customer Obsession". There are customers who depend on my team's application - I can't let them down! So I ignored the fire and my girlfriend's pleas, and started debugging the production issue. But all of a sudden, the smoke in my apartment cleared and the fire alarm fell silent. My girlfriend walked into the room, and to my astonishment, peeled off a wig and revealed herself to be Jeff Bezos himself! "I'm proud of you for being obsessed with our customers," he said, and gave me a 5 Amazon gift card. He then leaped out of my window and hopped into a waiting Amazon Prime delivery van that quickly peeled away. Even though I no longer work at Amazon, I'm so grateful for these experiences that taught me lessons I'll never forget. Agree?