When I was a developer, I always wanted to use the latest language and framework. I would accept the foibles of the framework, just because it was new and cool. Spend hours setting it up, installing all the different components, writing a simple application and then deploying at the click of a button …. only to spend hours in the server backends, trying to understand why it did not work! I’d then get a exciting new job using the framework, and be immediately lauded as the star developer, which in truth became more like first line support.
As CTO, you should always be super aware of trends, but very weary about jumping straight in. Can you afford to lose man days, whilst the team gets it head around new technology. They might be having fun, but you’re getting nothing done and that costs money.
When evaluating a framework as CTO, alongside the normal technical considerations you need to take into account;
If you’re starting a new project, you should have a shortlist of suitable frameworks that can be used. Evaluate each based on both the technical and commercial reasons above. If you want to introduce a new framework, think about getting one developer or at most a small team, to evaluate and potentially create a simple prototype to confirm its suitability.
Finally, a counter point to raise …. don’t choose your favourite, just because you know it as that could also turn into an expensive mistake. When choosing a technology stack – favourite, existing, pioneering – you must do nothing less than a thorough evaluation to find the most cost effective solution for your company, at that moment in time. It’s one of the primary responsibilities for any successful CTO.
Choosing the technology stack is one of the many tasks requested of the CTO and if you’d like to know more, why not read our article with more information about CTOs.
90 Things You Need To Know If You Want to Become The CTO
We have all worked in places where the team doesn’t trust the leader.
Where the leader doesn’t trust the team.
It rarely ends well.
What if you could anticipate every problem, issue or obstacle in life before they occurred? Effective tech leaders are able to anticipate more than most.