3 ms·
> I've been in a company where I stopped writing code — > and I found that I just couldn't keep up. I couldn't > participate in architectural discussio
by peteretep 12y ago
> I've been in a company where I stopped writing code —
> and I found that I just couldn't keep up. I couldn't
> participate in architectural discussions, couldn't form
> opinions based solely on what other people told me.
Just wanted to add a counter-point; I was CTO for a technical team of ~40 and didn't write code (and joined once the team was already almost that big). While I'm sure I had many failings, I didn't find keeping up with the technology to be any kind of problem, and frequently got involved in the nitty gritty of technical discussions.
I worked with many talented people, but I think was frequently able to make better contributions to the architecture as a direct result of having not been close to the code. Not having any baggage from having not grown up with the company, and from not being day to day at the code-face gave me some altitude, I think.
- lmm 12y agoDo you have a way of measuring? One of the companies I worked for was completely sunk by the "chief technical architect", who to the end was convinced he was making the right choices.
- peteretep 12y agoMeasure? No. But I never insisted we did stuff my way, only suggested it, and we often went with it.