4 ms·
In my opinion you shouldn't be a CTO but a founder. I don't think any serious tech team can respect a technically inexperienced or poor CTO for long and this wi
by kashif 11y ago
In my opinion you shouldn't be a CTO but a founder. I don't think any serious tech team can respect a technically inexperienced or poor CTO for long and this will cause problems later.
It might be a better idea for you to go for a Chief Product Officer or just Founder and hire someone experienced to do the CTO role.
If you think you can lead from the front without being competent in a subject - you have another thing coming.
- suyash 11y ago+1 hire an experienced CTO/Sr. Tech Leader first and then all your problems will be solved.
- jonsterling 11y agoyep.
- CyberFonic 11y agoI hope you are hearing the chorus - just don't call yourself a CTO. Bestowing upon yourself a fancy title doesn't make you one. What you have done so far is great! You've written a prototype, possibly even a MVP. And that is very good. It has gotten your biz to this point. Now is the time to hand over the reins to somebody who is technically competent, somebody who can select capable development team members and manage them. If you can manage this transition well, you will gain far more respect than by clinging onto a fancy title. Of course, that doesn't say that you should stop programming. In fact, you could learn a great deal from the new hires.