I really dislike articles like this, which state unproven thoughts as facts and useful advice.
1) Learning to code isn't hard? It is. But let's say you did learn some basic stuff and put up an MVP which is gaining traffic. You now need to hire more engineers. How are you going to vet them? When you hire them are you going to manage them or are they going to manage you? Are they just going to take over the product? How do you know if they are doing a good job or not?
2) Hire an external team. Good luck! You have all the same problems as above but now you are probably paying a lot more cash and less equity for the work.
3) Simplify your MVP. Wait, but I already did simplify it, and now I need to grow it! An MVP does not a company make, and once you do make an MVP all your problems don't naturally go away.
4) No settling for a mediocre team. I spend a lot of time interviewing people for engineering positions, I have a very strong technical background, and I can assure it is extremely difficult. Great people and mediocre people don't walk around with signs around their neck. They all blend together and it is your job to identify them, and it isn't easy at all.
As somebody mentioned in a comment post, I think this similar article which is linked to is significantly better:
This response for how to find a technical co-founder is just perfect:
> I can't help you with that, but all the good entrepreneurs seem to figure it out. Hopefully you will too.
I also think it applies for a technical person finding regular co-founders as well.
You need to have skills that another person thinks would compliment them, and then convince them of that. I think the distinction between "technical" and "non-technical" already is bucketed too much, since being able to write code is just a skill on a talent spectrum just like anything else. You don't need one person who is amazing at writing code and one person who doesn't know anything. Two people who each know a little bit might work. One person who knows a little might work. There are no preset rules, because every company and idea is different. You gotta figure it out.
1) Learning to code isn't hard? It is. But let's say you did learn some basic stuff and put up an MVP which is gaining traffic. You now need to hire more engineers. How are you going to vet them? When you hire them are you going to manage them or are they going to manage you? Are they just going to take over the product? How do you know if they are doing a good job or not?
2) Hire an external team. Good luck! You have all the same problems as above but now you are probably paying a lot more cash and less equity for the work.
3) Simplify your MVP. Wait, but I already did simplify it, and now I need to grow it! An MVP does not a company make, and once you do make an MVP all your problems don't naturally go away.
4) No settling for a mediocre team. I spend a lot of time interviewing people for engineering positions, I have a very strong technical background, and I can assure it is extremely difficult. Great people and mediocre people don't walk around with signs around their neck. They all blend together and it is your job to identify them, and it isn't easy at all.
As somebody mentioned in a comment post, I think this similar article which is linked to is significantly better:
http://www.humbledmba.com/please-please-please-stop-asking-h...
This response for how to find a technical co-founder is just perfect:
> I can't help you with that, but all the good entrepreneurs seem to figure it out. Hopefully you will too.
I also think it applies for a technical person finding regular co-founders as well.
You need to have skills that another person thinks would compliment them, and then convince them of that. I think the distinction between "technical" and "non-technical" already is bucketed too much, since being able to write code is just a skill on a talent spectrum just like anything else. You don't need one person who is amazing at writing code and one person who doesn't know anything. Two people who each know a little bit might work. One person who knows a little might work. There are no preset rules, because every company and idea is different. You gotta figure it out.