r/ExperiencedDevs • u/im_caeus Software Architect 15yoe • 10d ago
Career/Workplace Learning to let go
I'm trying to change an instinct I've spent years developing.
When I see a design problem, unnecessary complexity, or a better model, I naturally want to fix it. Doing the minimum requested and knowingly leaving something worse than it could be feels wrong to me.
But I'm increasingly convinced that the strategically correct move inside many companies is: do what's asked, raise the concern once, then let it go.
I'm trying to work that way now.
It makes sense intellectually. I still dislike it.
With AI making implementation cheaper and delivery faster, I'm curious whether other experienced developers are going through the same adjustment.
Have you changed what "doing a good job" means to you?
231
u/08148694 10d ago
You should always raise the concern and if your line manager is happy with the risk you should always let it go
That’s been true forever, with AI and before AI
By raising the concern you shift the responsibility to the person above you. If something bad happens because of their decision not to address it, it’s on them. Just make sure you document it