Victor

Just a few years ago, management could comfortably wait out a two-week sprint to get a feature shipped. Today, there’s growing impatience when a feature takes more than 24 hours to deliver. 🥲 The pressure on software engineers right now is crazy, and I don’t think we’re talking about it enough. I can barely get two sentences into explaining my implementation plan before someone interrupts with: “Just give it to Claude to do!” “Sir, we need to think about…” “That’s what Claude is there for. Let it do the heavy lifting!” A task gets assigned, and barely 10 minutes later: “Why is it taking so long? Aren’t you using Claude properly? This should take a minute or two!” Somehow, the existence of AI has created this assumption that software engineering is now just a matter of writing a prompt and watching features magically appear. Nobody wants to hear about architecture, edge cases, testing, security, or the implications of a poorly thought-out implementation. Just ship it. And ship it NOW. AI has become both a blessing and a curse. Something I genuinely expected to reduce my workload has instead increased it. The productivity gains are real, but so are the expectations that come with them. We’ve made development faster, but somehow, we’ve also made every delivery feel slower. And that’s the irony nobody seems to be talking about. Omo mehn, I’m just exhausted, might as well just resign, but it seems it’s the same everywhere😪