Me After Crying Because Of 200 Errors In 2 Lines

Content chrisk5000 chrisk5000 Almost made fun of an electrician today like "is it an electrician's guild rule that you have to perform 5 minutes of ritual complaining about What Was The Previous Electrician Thinking before you're allowed to fix anything?" but then I remembered I'm a software engineer 6:25 PM Nov 15, 2018 Twitter Web Client 586 Retweets 2.4K Likes ProdrammerHumor.io

Content Compiler errors Linker errors made with mematic ProdrammerHumor.io

The face of pure, unadulterated doubt . Every developer knows that look—it's the one you make when your colleague swears their 5-year-old Stack Overflow solution will fix everything. The same expression you had when the junior dev said "I rewrote it in Rust over the weekend" or when management promised "just one more small feature before release." That suspicious squint is the universal BS detector that evolves after your 50th "final version" turns into version 17.3.2-hotfix-please-god-work.

Content Paul Kuruvilla RohitPaulK We've never fired an intern this quick Devin APP Yesterday at 12:30 PM No, make test ash is failing. The test fails in Stage 4: Quoting with single quotes Ryan Yesterdav at 12:31 PM PR is not ready for review unless make testash is passing. Please fix the error. Devin APP Yesterday at 12:31 PM 1 understand. I will fix the quoting test failure in Stage 4 before requesting review. Ryan Yesterday at 2:59 PM Progress? 1 Devin APP Yesterday at 2:59 PM I'm working on fixing the quoting test failure. The test expects "shell Intest" but ash outputs it on separate lines. I'm adjusting the regex patterns to handle this difference. Devin APP Yesterday at 5:17 PM Devin went to sleep due to usage limits. 1 For Review: I proposed 4 learnings to add to my knowledge base. You can review accept them here 83 app.devin.ai Devin (the Developer) 3:18 AM Dec 28, 2024 707K Views 167 17 368 71K 871

Content How to fix any computer The Oatmeal Windows Step I. Reboot Apple Step I. Take it to an Apple store. v Did that fix it, No? Proceed to step a Did that fix it; No? Proceed to step a Step a. Format hard drive Reinstall Windows Lose all your files. Quietly weep. Step a. Buy a new Mac. Overdraw your account. Quietly weep. Linux Step I. Learn to code in C. Recompile the kernel. Build your own microprocessor out of spare silicon you had lying around. Recompile the kernel again. Switch distros Recompile the kernel again but this time using a CPU powered by refracted light from Saturn. Grow a giont beard. Blame Sun Microsusters. Turn your bedroom into a server closet and spend ten years falling asleep to the sound of whirring fans. Switch distros again. Abandon all hugene. Write a regular expression that would make other precrammers cry blood. Learn to code in Java Recompile the kernel again Cut thic time while wearing your lucky socks) Did that fix its Nor Proceed to step an Step a. Revert back to using Windows or a Mac. Quietlu weep.

The five stages of code review grief, compressed into four panels. First, you're riding high on that dopamine rush when your code actually works. Next, you swagger into the senior dev's office like you've just solved P=NP. Then comes the inevitable soul-crushing "You did it wrong" feedback, followed by the final stage: complete existential collapse as you realize your approach was fundamentally flawed and those 8 hours of work were essentially a very educational waste of time. Classic senior dev move—they don't tell you HOW it's wrong, just that your entire existence as a programmer is questionable.