This has been pretty much my experience as my team grew from me + 1 to me + 16. I do some pairing and reviewing, mostly on the older parts of the codebase, but don't get to do much new stuff. I'm just too booked with other kinds of work. It's that whole maker vs manager schedule thing.
Yeah that's been my experience thus far; too many different priorities pulling in too many directions. And for me, being a CTO or dev manager (I know they're two different beasts) involves a lot of strategy, planning/big-picture stuff and removing blocks from the development team.
Love that quote though :D
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"The 4 stages of a CTO: 1. I wrote the whole thing / 2. I still code 50% / 3. I wish I had time to code / 4. My team doesn't let me code anymore"
-- Simon Stemplinger
This has been pretty much my experience as my team grew from me + 1 to me + 16. I do some pairing and reviewing, mostly on the older parts of the codebase, but don't get to do much new stuff. I'm just too booked with other kinds of work. It's that whole maker vs manager schedule thing.
Yeah that's been my experience thus far; too many different priorities pulling in too many directions. And for me, being a CTO or dev manager (I know they're two different beasts) involves a lot of strategy, planning/big-picture stuff and removing blocks from the development team.
Love that quote though :D