Hacker News new | comments | show | ask | jobs | submit login

Howdy, I am a developer (PHP, .Net, Ruby) and I have had similar experiences as the author, but I think that he should have highlighted the part where he says "fire fast". That is the best advice that he could ever have given. Let's face it, the majority of web applications today are not a technical challenge that have never been solved before.

Your main advantage will be to take the requirement and break it down into its lowest parts and then hand off those parts to an outsourced developer and if he/she does not deliver exactly to your spec, then end the relationship. Period.

There is a certain amount of luck to it, but just as the author suggests, I recommend first having the developer create a very simple application with requirements that you define and estimate how long it would have taken you (probably no more than a 5 hour task) and if he/she can deliver, then you've got yourself a winner and you can focus on the business and not javascript errors.

Another key here is breaking down the specs. If you're clear in your communication, you can get good work. But being 100% clear with exactly what you want the finished product to look like is critical.


I usually try to draw mockups to describe the work. I have a tabletPC so that helps. Also, for really technical stuff, I tried to put myself in his shoes and describe how I would approach the problem.

There is a fine line between clarifying and micromanaging though.


Yes fire fast. Recently I tried to hire someone. He was a good communicator but he was just not technical enough. So I let him go and two days after I found the right person.


Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact