Deep-dives on Elixir, Phoenix, OTP and distributed systems — code first, from two decades of shipping production software.
Choose a reading path, or browse the latest articles below.
Start with processes, then supervision and observing a running system.
Organize application boundaries, build interactive screens, and test them.
Project structure, code patterns, and the effect of ecosystem stability on AI tools.
Read the method, then follow the evidence through published product audits.
Read the method, then follow the evidence through published product audits. Articles are listed in suggested reading order.
4 articles
Clear filters and show all articlesCode has become cheap, but having an agent generate an app doesn't make it a product. A new series reviewing SaaS apps that launched and failed to convert, or sit abandoned — and what went wrong.
The method behind a public audit series: what the collector is allowed to touch, why every number needs a file behind it, and the difference between Unknown and Unmeasured.
An active product with paying customers and a massive security issue 36.5/100 — Broken. An anonymous visitor can read customer records and secret keys straight from the database — reported privately, and the operator declined to fix it.
A subscription tracker asking for your financial data, scored from the outside. 29/100 — Broken. Manual entry as the only way in, contact addresses that bounce or reach a stranger, a template placeholder live in the privacy policy, and a backend that stopped resolving.
Continue from this reading path
Discuss an audit →