3 ms·

As a CTO I see it as part of my job to find the right tool for the right job. Part of that was when I told the team I wanted our splash page and everything on

As a CTO I see it as part of my job to find the right tool for the right job. Part of that was when I told the team I wanted our splash page and everything on it to be just static HTML files that would be hand edited if and when it was needed. There was no need for fancy CMS tools for a landing page that gets updated maybe once a quarter. So, that's part of why you need a CTO - to know when to use static HTML!

korzun 9y ago
> As a CTO I see it as part of my job to find the right tool for the right job. If that's a minuscule part of the job, then I agree with you here. My point is, you are not a CTO if the technology behind the product is a static web site. What do your VP and Directors do all day? What about the teams under them? There is a huge difference between a CTO and a front-end engineering.