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

Programming

27781 readers
237 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
 

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
[–] stsquad@lemmy.ml 6 points 2 days ago

I've long been off the critical path because as a tech lead I have a lot more random stuff (and meetings) to deal with. I've been able to vibe code some non-production stuff like scripts to unify feature lists across JIRA, specs and the upstream docs which has helped free up time to hand craft more code on production.

I don't care too much about the quality or maintainability of those scripts as long as they make my life a bit easier. I do care about the maintainability of the production code base.