While I really enjoyed the article, I was left with mixed feelings about what it conveys in big picture terms. At some point it looked like a lot of excuses were made to defend people, processes or ideas.
If blaming individuals for mistakes were worthless, so would be recognizing individuals for achievements. You can’t have it both ways— make a choice. This would also imply that developer interviews are meaningless — well, all developers make mistakes, so all are equally good or bad. A random number generator for picking developers would be sufficient.
Break often, move fast
is the main culprit. It’s a cultural requirement for an entrepreneur to be accepted within the community. Other schools of thought are unacceptable. It’s a mentality of speed at the expense of foundational understanding and long run strategy. Everything is optimized for short term prosperity — after that, who cares.
Until short time scale productivity remains a valid metric of success, we’ll be ending up with enormous failures in the mid/long run. Your choice.
I bet we don’t want to follow the steps of the 40+ year long “war on cancer" — minor short term battle successes still leaving us in … “war". Had we prioritized wining the war rather than the battles, we could have solved cancer a long time ago.
Don’t break, move smartly
is what matters.