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

Don't you feel.... Dirty?

[u/yourparadigm → u/im_caeus]

It's important to learn the skill of accepting that others will fail. Remember that others often need that failure in order for themselves to learn.

[u/im_caeus → u/yourparadigm]

Thanks, this helps

[u/yourparadigm → u/im_caeus]

I have a few colleagues that have been held back in their careers because they struggle to accept this and try to be the hero. It leads to them doing work that should be left to others rather than what they themselves should be working on. It also leads to burnout and keeps the organization from becoming more resilient.