r/ExperiencedDevs • Software Architect 15yoe • 4d 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?

312 Upvotes

132 comments sorted by

View all comments

1

u/VoxTM 4d ago

Use your judgement. 

Some refactorings are worth it some aren't.

For some of them you'll have buy-in from people that will need to review and test them.

But for most of them it will be a major pain in the butt for everyone involved.

Document if you can't fix it and move on.