31–40 of 41 posts
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…
Earlier quoted context omitted.
That's absurd. Most programers are male? You can actually make that assumption factually. How do you feel about the phrase "MIDWIFE's are in demand"? Is it appropriate or do you feel that people should have to say "Midwifes, both the females that practice midwifery and the males in in this profession, are in demand"? Can we just assume that the majority of midwifes are women and the majority of programmers are men wi…
> How do you feel about the phrase "MIDWIFE's are in demand"? Well, for me, bad, but mostly for reasons unrelated to the main issue in the discussion -- because it uses an apostrophe improperly for "look out, here comes an 's'", and because the plural of "midwife" is "midwives". ("midwifes", without the gratuitous apostrophe, is a word, but its the third person present of the verb "midwife", not the plural of the nou…
Hire a Lead Dev before you hire engineers/programmers. You'll save SO much time and headaches. I summarize here what I expect from Lead Devs: - A lead knows how to architect solutions. Not just code them. - A lead talks higher level than programmers/engineers. You don't want to hear code, you want to hear solutions/implications + pros/cons. - A lead is interested in the interconnections with other systems, and doesn'…
Hire a Lead Dev before you hire engineers/programmers. You'll save SO much time and headaches. I summarize here what I expect from Lead Devs: - A lead knows how to architect solutions. Not just code them. - A lead talks higher level than programmers/engineers. You don't want to hear code, you want to hear solutions/implications + pros/cons. - A lead is interested in the interconnections with other systems, and doesn'…
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…
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.
Hire a Lead Dev before you hire engineers/programmers. You'll save SO much time and headaches. I summarize here what I expect from Lead Devs: - A lead knows how to architect solutions. Not just code them. - A lead talks higher level than programmers/engineers. You don't want to hear code, you want to hear solutions/implications + pros/cons. - A lead is interested in the interconnections with other systems, and doesn'…
These are all things any engineer should be able to/ does do. The title "lead dev" sounds like marketing.
If you compare with companies with big budget, yes those attitudes are what you find on the average engineer. In the London start-up world where budget is tight and VC's think short term that's normally not the case. It's hard to find solid architectural thinkers with experience who don't call themselves Leads, Architects and so on.
Are these skills and attitudes found in your area as just "engineers"?
Hire a Lead Dev before you hire engineers/programmers. You'll save SO much time and headaches. I summarize here what I expect from Lead Devs: - A lead knows how to architect solutions. Not just code them. - A lead talks higher level than programmers/engineers. You don't want to hear code, you want to hear solutions/implications + pros/cons. - A lead is interested in the interconnections with other systems, and doesn'…
These are all things any engineer should be able to/ does do. The title "lead dev" sounds like marketing.
I would say use the title VP of Engineering for the new hire. IF they are a rockstar, then you can promote them to CTO. If not, you could hire a CTO.
I would move yourself into another C-level title such as Chief Product Officer. CTO really means deep experience with tech which you don't have.....and that's ok because you are a founder that kicked ass on the initial version. Now you can bring in the talent to really scale the tech side of the company.
Earlier quoted context omitted.
These are all things any engineer should be able to/ does do. The title "lead dev" sounds like marketing.
Calling us "engineers" instead of "developers" is also marketing. That's not the point.