this post was submitted on 19 Jul 2026
14 points (65.2% liked)

Programming

27781 readers
175 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
14
The Bosses Are Coding Again (blog.herlein.com)
submitted 1 day ago by codeinabox@programming.dev to c/programming@programming.dev
27 comments fedilink hide all child comments
 

Somewhere in the last year, a bunch of us who hadn’t shipped real code in years quietly started shipping again. Not reviewing it. Not architecting it in a doc and handing it off. Actually building it. And loving it.

I lead software for a living. That means my days are meetings, roadmaps, hiring, unblocking people, and saying “no” a lot. The last time “writing code” was my actual job was a long time ago. I never stopped being able to code — I stopped having the time to code. At least in my day job. There’s a difference, and every engineering leader reading this feels it in their bones.

you are viewing a single comment's thread
view the rest of the comments
[–] trem@lemmy.blahaj.zone 16 points 1 day ago (1 children)

Yeah, I thought the blog post was gonna be about horror stories, because even the greatest senior/architect/whatever will push absolute garbage into your codebase, if they don't have the time to familiarize themselves with how the code actually works.

Even if it's some isolated component, if they implement it without explaining the what and why to others, then no one else can maintain or debug that. And you do not want to rely on your super important guy to have the time to fix things when production grinds to a halt.

[–] adhocfungus@midwest.social 11 points 1 day ago (1 children)

At this point I think we're moving past maintaining projects. Tech debt is no longer going to be paid off; management will just suggest a complete rewrite using AI as soon as issues get too complex for a junior dev with Copilot to figure out. It's going to be a mess.

[–] elvith@feddit.org 6 points 1 day ago

I ~~feel~~ fear the same. Problem is, when it's too complex to maintain for a junior dev/intern with AI, it's probably also too complex for a rewrite/redesign with AI...