These all resonate deeply with me: > We are destroying software with an absurd chain of dependencies, making everything bloated and fragile. > We are destroyi

These all resonate deeply with me: > We are destroying software with an absurd chain of dependencies, making everything bloated and fragile. > We are destroying software by always thinking that the de-facto standard for XYZ is better than what we can do, tailored specifically for our use case. > We are destroying software mistaking it for a purely engineering discipline. > We are destroying software claiming that code comments are useless. > We are destroying software by always underestimating how hard it is to work with existing complex libraries VS creating our stuff. This one begs the question: "What is 'fast'?". I mean, is it high-performance, or quickly-written? (I think either one is a problem, but "quickly-written" leads to bad software, and overly-optimized software can be quite hard to maintain and extend). > We are destroying software trying to produce code as fast as possible, not as well designed as possible.