The don't do it alone hits strong. CTO's are like solopreneurs in each organizations. Too technical to be a product-focused founder, too strategic to be an engineer. You end up without peers and growth-plans, making your learning and continued adaptation your sole responsibility.
That’s, this was a very good read and some great insights and perspectives, and not writing code was the biggest thing I had to accept when I decided this was a direction I wanted to go and am now actively working towards that role within my company, not only as a first timer, but as the companies first.
Accepting it was not hard, when the idea was floated by me I sort of instinctively said yes assuming it’s simply the next rung on the ladder, a natural progression.
That version of me was talking sh1t. That version was going to die writing code.
By the time I had sat down and started looking into what the job actually was, I was in a very different place in my leadership journey and had already understood and began to enjoy the people side of the role and was already slowly phasing away from being on the Jira board to focus more on team development.
Company is still small so once that becomes a reality it will still be some time before I phase out of the codebase and it may never be entirely viable, but knowing that it was a probability was an important part of making an informed decision about going on the journey, the moment I realised that I also knew I was OK with it.
Thanks a lot for sharing your own experience and journey. From what I'm seeing you're on the right track! Keep up the good work, and thanks again for the feedback on the article. Keep it coming!
The don't do it alone hits strong. CTO's are like solopreneurs in each organizations. Too technical to be a product-focused founder, too strategic to be an engineer. You end up without peers and growth-plans, making your learning and continued adaptation your sole responsibility.
I'm glad it resonated with you.
I hope you are or will take action soon in that direction!
Let me know how it goes!
Solid post packed with great insights
Thanks Alex, really appreciated
That’s, this was a very good read and some great insights and perspectives, and not writing code was the biggest thing I had to accept when I decided this was a direction I wanted to go and am now actively working towards that role within my company, not only as a first timer, but as the companies first.
What was the hardest part of accepting it? And what made you realise you had to do it?
Accepting it was not hard, when the idea was floated by me I sort of instinctively said yes assuming it’s simply the next rung on the ladder, a natural progression.
That version of me was talking sh1t. That version was going to die writing code.
By the time I had sat down and started looking into what the job actually was, I was in a very different place in my leadership journey and had already understood and began to enjoy the people side of the role and was already slowly phasing away from being on the Jira board to focus more on team development.
Company is still small so once that becomes a reality it will still be some time before I phase out of the codebase and it may never be entirely viable, but knowing that it was a probability was an important part of making an informed decision about going on the journey, the moment I realised that I also knew I was OK with it.
Thanks a lot for sharing your own experience and journey. From what I'm seeing you're on the right track! Keep up the good work, and thanks again for the feedback on the article. Keep it coming!