14

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
[-] onlinepersona@programming.dev 4 points 1 day ago

100%

I got this my superior who decided AI allowed them to code fixes and we were stuck with buggy code that wasn't merged, because the superior had moved on to a more important task requiring more AI "support" and couldn't process the comments. Things could've been faster had we implemented things ourselves.

When you aren't out in the fields dealing with stuff, you don't know what's important to the workers. "Jumping in" for a minute to do a task might actually slow down the team if understanding of day to day struggles isn't present.

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

Programming

27783 readers
156 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