Hacker News Reader

In many cases, having soft deadlines works. You can double check and do code reviews for ever, it is never perfect and we can always think of a better way. Regardless of the experience of the engineer less time to complete a task means prioritizing making code just work, over making code optimal.

View on HN

I think this is very important, not having a deadline can mean nothing ships and having a hard deadline I have seen quality and best practices slip due to pressure to cut corners.

Other general things that I’ve seen help. Code reviews should not be a rubber stamp, the reviewer should understand everything, there should be a degree of overlap of feature development between devs, end-to-end tests to check for regression can be highly useful once a project is if reasonable complexity.

Reply on news.ycombinator.com