Articles on reducing technical chaos: debt, needless complexity, dependencies. Concrete practices for sober, durable systems.
We won the war of gigabytes. AI begins the war of tokens: the most useful context will not be the largest, but the most precise.
Technical debt shows up in the team’s daily work before it shows up in the code. Three concrete signals to detect it before it gets expensive.
AI can amplify your ownership or replace it. The difference lies not in the tool, but in what you keep understanding about your own system.
Every layer added “just in case” is paid for daily: in reading, testing, onboarding. How to spot the complexity that serves no one.
Playlists, newsletters, stacked courses: scattering is the technical debt of learning. Three principles to progress without accumulating.
A system you cannot leave is not yours. Three simple tests to know whether you truly keep ownership of what is built for you.
Watches, apps, sleep scores: measuring more never healed anyone. How sobriety applies to health too — fewer metrics, more constants.