So, this is a pretty decent advice. Basically, the author's idea is that if you:<p>- Treat finding a CTO like a full-time job,<p>- Learn to build some basic HTML,<p>- Read a book on Ruby / Git / Rails,<p>You should be able to find a <i>good</i> CTO for your company.<p>Unfortunately, while this is some pretty good starter advice, I doubt this would help you find a <i>great</i> CTO, first engineer, whatever.<p>Smart people typically want to be around other smart people, and the idea that building a simple HTML page and reading through a single book will let you find an amazing programmer to really build your product is, unfortunately, not realistic.<p>Great programmers look for:<p>- Interesting technical challenges,<p>- To be treated as equals, and have a large amount of influence over technologies, product decisions, etc.,<p>- Highly motivated, smart people they can learn from,<p>- Great compensation,<p>- A very strong sense of purpose and direction.<p>If you're a business person who can offer all of the above, you'll probably have a great chance of finding a really awesome tech person to work with.<p>Unless you plan on really getting great with HTML or something of the sort, it's probably a better idea to instead learn to use a tool like balsamiq (<a href="http://www.balsamiq.com/" rel="nofollow">http://www.balsamiq.com/</a>) and make some really amazing wireframes instead. At least doing things this way, you'll have a really clean skeleton to show off to people, and help them understand your vision.<p>If you're looking for a programmer out there--best of luck!