Should engineering leaders code?
Yes, it keeps their expertise sharp90%
No, they should be less hands-on10%
125 PARTICIPANTS
Senior Director Engineering in Travel and Hospitality, 10,001+ employees
Coding does not men they are not sharp. Architecture and Design reviews help them stay upto date as wellIT Director, Supply Chain Digital in Manufacturing, 10,001+ employees
In most cases, the answer is Yes. Not only does it keep expertise sharp but also:- Hands-on awareness of the realities
- Earn respect of the team as someone who knows the ground realities.
CTO in Consumer Goods, 11 - 50 employees
If you’re not in the code base writing code on a regular basis, then your contribution is more likely to be an annoyance to the team than a blessing. You’re also putting someone junior to you on the spot to do a code review. If you’re at an executive level, contributing code probably isn’t the highest value way to provide value to your teams or your company.Content you might like
Important solution for today’s way of working52%
Interesting idea to explore for 202242%
Not necessary6%
214 PARTICIPANTS
Just before the renewal5%
A few days in advance35%
A few weeks in advance27%
A few months in advance30%
A few years or more in advance1%
680 PARTICIPANTS
Chief Technology Officer in Software, 51 - 200 employees
My personal experience. I usually get the feedback and go back with data driven analysis providing details to cross leaders to understand the context and make decision basis data and and not gut feeling.
CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.