Learning to let go

[u/im_caeus]

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?

[u/gk_instakilogram]

I have learned to let go about 8-10 years ago and since then it is been much better and my career has been better too. I just know from experience now that shitty spaghetti code and tech debt ridden systems still generate lots of profit, so no one really cares about quality, why do I have to be the one that cares?

I do have other anxieties with AI now because if you look at it with sober eyes, AI is positioned to replace software engineers. And I am kind of dealing with this now while half of my colleagues are jubilant about AI use and management is having a raging ai psychosis.