DEV Community

Discussion on: Build a leader habit: learn how to let go

Collapse
 
codemouse92 profile image
Jason C. McDonald

Practically my entire career has been in that situation, so although I'm not the OP here, I do have some insight. My adage has always been...

It is easier for a developer to get themselves out of a hole THEY dug, rather than one YOU dug for them.

So, I'd say this article still applies! I try to stay familiar with as much of the code base as I can, but when I assign it to someone else, I trust them to make decisions (and mistakes) and to deal with the natural consequences thereof, whether good or bad. I'm still available to help, through code reviews, one-on-one conversations, meetings, and the like, but my other rule is...

Don't offer help until asked for it.

When I bring an intern on to the year-long internship program, I personally guide them through the first month. After that, I make it clear that I will no longer help unless I'm asked. Aside from my asking "how is it going? any problems?" periodically to help prompt them to reach out, the responsibility to seek help is on them.

All in all, it works pretty well.