This seems like a very useful concept to use with clients

• "A review of all the literature on whether static typing reduces bugs (up to 2014), showing that the solid research is inconclusive, while the conclusive research had methodological issues."

• "The client, specifically the project owner, is always responsible for project completion and success. Leadership should never accept external accountability without internal accountability. This is not to say that one cannot share, or should not share, accountability; however, again, one cannot have only external accountability."

• "With any experienced team of engineers and designers, PM'ing is not a full-time job"
• "since the necessity for a PM depends on the product, the team, and the needs of the business, the traditional notion of a 1-to-1 relationship between teams and PMs should be reconsidered."
• "Ideal time to hire a PM ... founders can no longer be involved in all the important product decisions" "But the founders should still act as de-facto heads of products".

Radical language. But I mostly agree with sentiment. He ascribes most blame to the pop culture influencer developers, but I think the second half of the phenomenon is a public that wants that content. Web Development attracts the kinds of people who want to learn new things and believe their profession is difficult and complicated, so when there’s a new way of doing something it’s extremely attractive.

• Great guide on how to write good product copy

• Incredible piece about the history of web software architectures, along with some great acronyms. It is also an advertisement for remix.run - the company the author works for, but still great nonetheless.

• Really great points about why (or why not) use React. The "Community & support" bit is also very relevant

• This was really good - filled with nuggets
• "They are not usually very good at thinking about the people who will use their systems, taking their preferences into account, and treating them like customers who they are trying to keep. Why should they? The people who use their systems are a captive audience!"
• "Culture, with its focus on cost, scale, and process, over people and usability"

• Not particularly useful - it claims baselessly that the reason production systems have become more complex is "Engineering organizations are under constant pressure to deliver more value, in less time, at a faster and faster pace." - which doesn't prove anything really, but it does allude to a potentially useful framework for understanding systems.
• "Obvious systems - the relationship between cause and effect is clear to anyone looking at the system"