When you don’t create things, you become defined by your tastes rather than ability. Your tastes only narrow & exclude people. So create.

If you can’t explain a solution, then you don’t really understand it.

8h per day for 3.5 years make you an expert 4h per day for 7 years make you an expert 1h per day for 28 years makes you an expert

Chesterton’s fence is the principle that reforms should not be made until the reasoning behind the existing state of affairs is understood.

In economic science, the tragedy of the commons is a situation in which individual users, who have open access to a resource unhampered by shared social structures or formal rules that govern access and use, act independently according to their own self-interest and, contrary to the common good of all users, cause depletion of the resource through their uncoordinated action.

REST means different things to different audiences. It means one thing to the developer completing their assignments in Jira, another to the engineering leader attempting to herd cats through a transformation, and yet another to the marketplace selling solutions. The term’s conflation isn’t an indictment of people’s laxness but an example of its success. We see this pattern repeatedly throughout the tech landscape. Agile methodologies, cloud computing, and even DevOps all started with specific principles but branched out, sometimes to their originator’s chagrin, as diverse groups adopted them.

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.

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”.

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.

Creativity comes from constraint.