A good point is made. If you're in a hole, the best way out is not to keep digging. It's hard to see that you have to accept a delay but a delay is exactly wha

A good point is made. If you're in a hole, the best way out is not to keep digging. It's hard to see that you have to accept a delay but a delay is exactly what you need when you're not making good progress. Slow down, finish shit, move on. Same with load. Sometimes just gotta do less at once. - the worst code quality is when engineers who aren't already experts in a specific thing can't experiment. This is multiplied 10x for junior engineers. - the most qa rejections happen when engineers need to work 10-12 hours straight to complete a feature and it will always be sub par even at the end. You pay shortly for problems because you didn't let anyone think deeply. - at some point you need to be able to declare bankruptcy and abandon work because otherwise you'll sink.