Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Programmers aren't just cogs in a system, and this is a mistake that many managers make. (And this is insulting to potential hires, by the way.) If you only know that you need "a lot" of them, you need to clarify the nature of the work. For example...is it a web site, will there be databases involved, is this software to power some kind of machine, will it use a network, will it require a GUI, will it run on Mac or Windows or Linux, are there restrictions on what it must interact with, is it safe to open-source the project and use GPL'd libraries, etc.? These details will also help you to write job postings.

In general, you get what you pay for, only less. Code has to be maintained, and even if something is thrown together in "a couple months", you may regret that for anything except a prototype.

A single excellent programmer may very well handle your entire project, and ten horrible programmers may never get it done. If you're not experienced dealing with programmers, then set up some kind of deal where you pay only when it's finished and you see regular progress from the people you hire. Be prepared to set aside plenty of time to test what is given to you, and do both expected and unexpected things with it. You need to be in a position to reject their work if they say it's "done" and you can still see quirks and instability (because some programmers can be lazy or clueless).

The cost of living in the valley is very high, so anyone living there will need more money for that reason alone. It wouldn't surprise me if you paid nearly 50% extra. This might be worth it, especially if it means finding someone right away instead of 6 months from now, but keep it in mind.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: