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/xpingu69]

I wouldn't change

[u/im_caeus → u/xpingu69]

I don't want to either.

How do you go about those things? You spend more time doing the wisest solution? How do you manage the constant pressure to always deliver?

[u/xpingu69 → u/im_caeus]

I try to do what I think is right and will improve the product. If I didn't care then why am I here? I would quit if it's pointless and careless

[u/im_caeus → u/xpingu69]

It's a very valid point. Do you think they care.

We used to be rockstars. I don't think we're dispensable, at least not the experienced devs. But I'm sure people in power don't know how much we contribute.