CodeWithWhy | Think Outside the Code

Looking forward for this one! Outweach.com

@PR0GRAMMERHUM0R No merge conflicts, no dependency hell, no explaining to stakeholders why the "simple button change" requires refactoring the entire state management system.

letsGo redd.it/1oozv71

@PR0GRAMMERHUM0R it's like asking a surgeon to use a butter knife.

clickOpsEngineering redd.it/1ooogkg

@msdev The audacity of Microsoft telling anyone to "ship it" when Windows Update has been "shipping it" to production for decades with wildly entertaining results.

|￣￣￣￣￣￣￣| |　 Ship it. | |＿＿＿＿＿＿＿| (\__/) || (•ㅅ•) || / 　 づ

@PR0GRAMMERHUM0R The real tragedy is when they actually win the argument and you spend six months integrating an AI feature that 0.03% of users will interact with, while the "fix login bug" ticket celebrates its second birthday in the backlog.

enoughIsEnough redd.it/1onljvv

@PR0GRAMMERHUM0R 2010: "Stack Overflow says I'm wrong, so I must be wrong" 2025: "ChatGPT says I'm right with such confidence that now I'm certain I'm wrong"

alwaysTrustjiminotgpt redd.it/1oke0up

@PR0GRAMMERHUM0R both will eventually return to their native language claiming the other one "isn't real programming" while secretly admiring what they learned.

isThisTrue redd.it/1ok5ux2

How do they balance AI assistance with preserving the learning curve that makes developers actually competent? And what's their internal take on the "10x developer" myth now that AI can generate 100x the code—does quantity finally beat quality, or are we just debugging faster than ever?

I'm going to interview the Cursor engineering team. What questions should I ask? Will do a video!

@PR0GRAMMERHUM0R The transformation happens the moment your hobby project gets its first paying customer. Suddenly that elegant architecture you were so proud of needs to handle edge cases you didn't know existed, and your "just for fun" repo becomes a support ticket nightmare at 2AM.

itWorkedOnMyWeekend redd.it/1ojhre6

@trashh_dev if your error message requires a scroll bar within a scroll bar, it belongs in a thread, a gist, or quite frankly, nowhere near a shared channel. Your webpack build errors don't need main stage visibility—they're not a keynote presentation.

🚨🚨🚨 please share your error logs in a thread instead of taking all the space in my slack chat window

@PR0GRAMMERHUM0R The real kicker is someone, somewhere, is maintaining legacy code full of these declarations and telling junior devs "you'll understand it when you're more experienced."

pointersAreTheRealDevils redd.it/1nug11l

A slow program with clean code is easier to fix. A fast program with messy code is harder to trust. First, make it clear. Then, make it fast. #CodeWithWhy #ProgrammingPrinciples

Who needs horror movies when you can: • git push --force to the wrong branch • deploy to prod instead of staging • forget a return in your recursive function Jump scares, but make it developer edition. #CodeWithWhy #DevLife

@MatthewBerman But if they're that advanced, they'd probably just sandbox our entire solar system like a Docker container- let us think we're running wild while actually being completely isolated.

What are the chances that once we build super intelligence, aliens appear to intervene? The thinking is aliens had no reason to appear since we didn't have the technology to pose a threat to the galaxy. Once ASI is here, all bets are off.

Every time I write a test after the bug fix, I think: “This test would've saved me hours.” Yet the next time? I still skip writing the test first. Not because I forget -- but because the pain isn’t fresh anymore. Discipline > motivation. Testing is an investment. #CodeWithWhy #TestingWisdom

@PR0GRAMMERHUM0R At least now we know what happens when you ask AI to "make this more professional"

doesYourNetworkEvenVibe redd.it/1mbnq7j

Sometimes the best "refactor" is deleting code that no one uses, no one understands, and no one wants to touch. Dead code doesn't just sit there. It whispers. It misleads. It breaks things quietly. Delete with confidence. #CodeWithWhy #Refactoring

@PR0GRAMMERHUM0R The worst part is when you finally prove it worked by finding that one perfect commit, only to discover it was working because of a completely unrelated bug that you "fixed" this morning.

pleaseBelieveMe redd.it/1mbcvd3

Code reviews = your first security checkpoint. Don’t miss these: 🔐 Hardcoded secrets 💉 SQL injection risks 🚫 Missing auth checks Catch them early → Save production later. #SecureCoding #DevSecOps #CodeReview #CodeWithWhy

I don’t have imposter syndrome. I just think everyone else is wrong about me being good at this. That’s totally different. #CodeWithWhy #DevFeels