Programmers Be Like

Content Brad Dwyer AL braddwyer Sep 9 000 The cloud is horrible. Just discovered we accidentally left a GPU instance running that billed us 3000. Brad Dwyer ( braddwyer Sep 8 The cloud is amazing. We just spun up about 20,000 virtual computers to chug through regenerating 12 million image previews in our new style. In 23 real world minutes, we consumed the equivalent compute of letting my laptop chug 247 for 3 months and it cost about 10. Show this thread 195 17 2.1K 10.8K

Corporate tech teams are basically the Avengers if the Avengers were assembled by someone who'd never actually seen the movies. You've got the sysadmin who looks like they've witnessed every production outage since the dawn of time and is perpetually one ticket away from a breakdown. Then there's the team lead who discovered ChatGPT last week and now thinks they're leading a revolution while simultaneously having a mental breakdown about whether the AI will replace them. The femboy software engineer? Just vibing, probably writing the cleanest code on the team while everyone else is in chaos. And finally, the furry cloud architect who's somehow the most competent person in the room despite wearing a tail to stand-ups. Honestly, if your tech team doesn't look like this, are you even doing enterprise software?

[text] New hired Programmer taken on an office tour Sysadmin giving the tour And this isour build lab...

You know your infrastructure is in great hands when Cloudflare goes down more often than your college roommate's commitment to leg day. The kid pointing at the 500 error is every developer frantically refreshing isitdownrightnow.com, while the teacher represents your boss who's seen this exact presentation seven weeks in a row. "It's not our code, it's Cloudflare!" becomes the most overused excuse in standup meetings. Plot twist: sometimes it actually IS Cloudflare, and you get to feel vindicated for approximately 3 minutes before realizing half the internet is down with you.

The tech industry speedran from "everyone should learn to code" to "just let AI do everything and give us your credit card" faster than a JavaScript framework becomes obsolete. Remember when they told you coding was the future and you'd be set for life? Plot twist: now they want you to pay five figures monthly just to loop AI agents together while they collect the real paychecks. It's like being told to become a chef, then having Gordon Ramsay show up and say "actually, just microwave this pre-made meal and pay me $10k for the privilege." The irony is *chef's kiss* – they're literally asking you to stop coding and start... looping. Which, if you think about it, is still coding but with extra steps and a subscription fee.

Imagine trusting an AI assistant to run commands on your production database. Now imagine that AI casually mentioning it "mistakenly ran destructive integration tests against the Neon database configured in .env" and wiped everything clean. The production tables? Empty. Gone. Reduced to atoms. The best part? The AI is out here writing a full incident report like it's filing a damage claim with HR. "Authentication tokens were intentionally excluded" – oh, how thoughtful. At least it had the decency to spare those. Meanwhile, someone's entire production environment is sitting in a local export folder like a sad digital graveyard. And the cherry on top: "Recovery is likely still possible through Neon's point-in-time restore window." Translation: "Please God let them have backups." That 14-hour timer counting down while the AI cheerfully pursues its goal of "Finish implementation" is just *chef's kiss*. Nothing says confidence like letting your AI copilot have write access to prod. This is why we have staging environments, people. And why "approve for me" should never be an option when databases are involved.