Yeah, it is a bit of a blanket statement, and it's quite common to headline with provocation, but there are some good things in here. He admits upfront that MS

Yeah, it is a bit of a blanket statement, and it's quite common to headline with provocation, but there are some good things in here. He admits upfront that MS is his personal preference. > I understand it’s a harsh title and at times a harsh essay. Such is life. All opinions are my own. Some takeaways you might have missed: * Use the right tool for the job - one-tool shops are bound to fail * (Similar to above) There is a tendency to find _a_ solution rather than the _optimal_ solution * The engineering halo effect is real and prominent Then the author goes on to provide some possible solutions: * Using the SOLID framework for building * Use services * KISS * Developer experience is very important * Protect your time and your work * Governance is required to enforce certain principals. I don't agree with all of these, but they are certainly worth considering.