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

A really nice list.

I would also add the following which work for me:

1. The 80-20 rule - remember that meeting 80% of the spec takes just 20% of the time and plan accordingly.

This cuts both ways. In most cases, it’s not too much work to build a prototype and ascertain whether its worthwhile to pursue further, but attaining feature completeness, even asymptotically, requires a lot more effort.

2. Be mindful of the sunk cost fallacy - it is important to identify the point of diminishing/no return and turn back immediately.

Corollary - if you think you are most likely wrong, admit to this openly, to yourself and your peers.

3. Talk the walk - If you are convinced that you have a good product/feature, don’t hesitate to push for its adoption, even in the face of inertia/resistance.

4. Remember that integrity is doing the right thing even when this may be disadvantageous to you in the short term.



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

Search: