This is a mix of amazing and really bad advice. And the problem with it is that it is a series of advices / philosophy instead of explanation. Reading the orig

This is a mix of amazing and really bad advice. And the problem with it is that it is a series of advices / philosophy instead of explanation. Reading the original Rise of Worse is better article ( https://www.jwz.org/doc/worse-is-better.html https://www.jwz.org/doc/worse-is-better.html ) gave me a huge appreciation of programming implementariin simplicity, and improved my pace of coding a lot. It shows a real example of why C won over Lisp (a much cleaner interface) 50 years ago. The funny part is that right now I'm programming in something that may be closer to Lisp (Python), but happy to rewrite parts of it in C in the future when it gets practical. The amount of features I can add in a small time just because I always pick the smaller implementation surface (while still moving forward) is amazing. Regarding dependencies: I may want to move to lower level libraries in the future when my project is in a more advanced state, but again they are great as training wheels (lower level would help with customization, but I'm waiting until I _need_ it).