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

This is why:

1. You should spend more time designing (away from the computer) so that you find a _problem_ and then come up with a reasonable solution. Instead of putting together a list of features. (see Rich Hickey's talk "Hammock-driven development").

2. Think of the sum you're going to charge for your consulting and then multiply it by 4 and charge that because you have to take risk and other factors into account.



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

Search: