Bad strategy ignores the power of choice and focus, trying instead to accommodate a multitude of conflicting demands and interests. Like a quarterback whose only advice to his teammates is “Let’s win,” bad strategy covers up its failure to guide by embracing the language of broad goals, ambition, vision, and values. As seen in: https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/the-perils-of-bad-strategy

GraphQL has an advantage over simple Web APIs, as it offers some insight into how many users are using each field of your API. Although this insight may not be completely accurate, it can still be useful in estimating the cost of making a breaking change in a specific field. With this information, you can communicate the potential impact of the change more effectively.

What is an API design specification? A collection of patterns (with examples) Rules about how to apply them Tests to automate compliance

Soft skills dominate hard skills. Many hard skills will be automated by AI anyway. Soft skills and human relationships are the future, and emotional intelligence can be learned.

Last week, Reddit filed their S-1 to go public. At least 10% of their revenue - about $60m - comes from selling data to train Large Language Models. Data sales invert the business model of the Internet. Instead of Reddit building product experiences that create good advertising data to earn more on ads, Reddit will launch product experiences that produce more valuable data to feed to LLMs. The LLM vendors should pay more for better data.

The Shirky principle is the adage that “institutions will try to preserve the problem to which they are the solution”. More broadly, it can also be characterized as the adage that “every entity tends to prolong the problem it is solving”.

Great insights @ https://clig.dev/#output like Responsive is more important than fast I have to update the list of areas where interface design applies : APIs Query Languages CLIs

Don’t document the obvious: I see too many documents that contain sentences like “Name field - contains the name”. Tell me about what I may not know - restrictions on characters, how these are sorted, what if someone doesn’t have a first name, etc. Gregor Hohpe

The core conflict of developer tools is Abstraction vs. complexity Jean Young https://future.com/the-case-for-developer-experience/

Given the right documentation, self-service API integration should come naturally, right? What is the proper documentation though and who defines that? Working with teams to reduce the problem to a “set of questions” that the docs must answer, can help you move towards self-service.