This week's question is:
As a team leader, how do you stay in shape (hands on coding) while essentially it's your teams job to do the actual coding?
The more senior you become, the fewer code you write.
This is the case for most engineers who grow in the career ladder.
But how do you remain relevant in your field?
While I could answer things like:
- Side projects
- Weekly coding day(s)
- Follow courses regularly
I believe in something else.
You stay in shape if you can keep your team in shape.
I’ve always led my team by guiding them in making the right decisions.
Being able to keep your team’s knowledge current should be the challenge.
The last thing I want is to sort out all the answers for my team.
There are obviously architectural decisions that require experience, but hands-on coding knowledge can be a team’s responsiblity.
Want to have your question answered next week? Ask your question on LinkedIn or Twitter.
