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

I think you are missing something: wanted features always exceeds time. You need some form of deadline to force your to think about what features to cut. Nobody wants to cut any feature that could make it in until forced to and so you are always late.

The deadlines are artificial, but once they exist they force a lot of real scheduling on many others and so they become real. In theory you can change them, but in practice people are depending on you.

Nothing is wrong with what you said, but keep it in context of the above.



GP here, I don't disagree with you, engineering is all about trade-offs and you can't engineer things to perfection by taking months to solve easy problems. You need progress, and efficiency so sometimes less important problems need to be fixed with less than ideal hacks etc. I agree with this, but having a culture of "everything is due yesterday", "if it can be done in 6 months, tell customer it'll be ready in 2 months" etc just to create stress and increase productivity lowers the engineering quality exponentially more than it increases productivity and expediency.




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

Search: