In my opinion it can be summarised like this:
Dev: Technology is key!
CTO: Technology is a tool!
Don't get me wrong, it's important to be good at your craft, but in the end you will not be measured by how clean your code is, but by achieving your companies goals!
Or how would you describe the difference?
Top comments (5)
For some reason I read "CTO: Technology is cool!". I actually met a CTO of an early startup who convinced the rest of the team to use a cutting edge backend framework that was the latest fad back then (because buzz words), instead of picking a more familiar technology to suit the strengths, knowledge and skill level of the devs they could afford to hire back then. Well. Startup failed after just a few months 🤷
Ouch 🤦♂️
Thanks for this post. The CTO helps startups build a new product from scratch or improve existing technology solutions, meet deadlines, stay on budget, and manage a development team. This person combines a lot of roles and tasks, so the need and question of how to hire a cto for a startup arises more and more often.
Its not a bad way to distill it down tbh.
It allows for the reality that it can be an asset or a liability.
Some other elements that are hidden in it are budget, teams, organizations, strategic business goals, etc.
Having been the CTO, one weighty problem is looking at where you want to be in the future and acknowleding when the past is holdiing you back and what you're doing to do about it.
True there are many aspects to being a CTO! But in my head it all boils down to setting and meeting company milestones.
And of course it's tricky to actually achieve those but one key learning I had was accepting that in the end picking the right Technology in a company is just as important as picking the right screws in construction. And yes you need the right tools, but screws alone don't build a house.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.