This post made me really happy. THIS is the kind of encouragement that 'non-technical' aspiring founders need. Less of the "if you can't code you don't have val

This post made me really happy. THIS is the kind of encouragement that 'non-technical' aspiring founders need. Less of the "if you can't code you don't have valuable skills" attitude.  I have a blog post sitting in draft form that has scarily similar advice to this based on my own experiences, however this describes it with some really inspiring YC examples.  I started working this way at the start of 2012 and all of my projects since then have been far more popular/successful and more pleasing to work on. This is because I'm fully in control of project progress, I can see things through to launch, pushing the limits of my coding skills and bringing my 'concierge' MVP to life. For those looking for technical help with a project longer term, don't forget that by starting this way you're stripping back and leaving pure technical issues which allows those with technical skills to clearly see where they could bring value which makes offering help very interesting.