I'm in year.. let's see.. 24 of being a CTO. I always enjoy reading what other people see as important enough to write about. The conversation about shipping c

I'm in year.. let's see.. 24 of being a CTO. I always enjoy reading what other people see as important enough to write about. The conversation about shipping code is something most technical CTOs feel, and my solution to that 'need' has been to continue to explore my deeper technical 'must be building' in other parts of my life. I have a small Youtube channel that follows a few different technical paths, and I keep another array of deeper technical challenges in the development pipe always ready to go. I still write code, design hardware, build cars, and look at stars, but they are all self driven projects. I find the result is a tighter focus at my core job of technology strategy and the bigger decisions but also not a loss in my core technical abilities. To me the T in CTO means technical, and I think it is my responsibility to deeply understand the technology that our teams use. That understanding however can come from personal learning just as much from being in the production loop. Be a nerd. Food for thought, at least for me.