Two hundred pieces in
What writing in public taught me about engineering, what I was most wrong about, and why the archive is the point.
tech, developers, and the code underneath
36 pieces tagged opinion,
from January 3, 2025 to August 3, 2026.
What writing in public taught me about engineering, what I was most wrong about, and why the archive is the point.
Every line you remove is one that cannot break, cannot be misread, and does not need to be maintained.
Portability is not free and neither is dependence. A framework for deciding how much abstraction to buy.
Write once, run anywhere, debug everywhere. The honest accounting of what each approach actually costs.
The role is genuinely ambiguous and that ambiguity is load-bearing. An attempt at a concrete description.
The received wisdom is never rewrite. The received wisdom is mostly right and has three real exceptions.
Running code close to users is a real win for a narrow set of workloads and a complication for everything else.
Internal platforms fail for predictable reasons. The successful ones share four properties.
Donations, foundations, dual licensing, open core, and hosted service. Each works for a specific shape of project.
The entry-level pipeline is breaking in a way that will be expensive in five years. Some of the fixes are cheap.
Deliberate, accidental, and structural. They need completely different responses and everyone calls them the same thing.
It's excellent software solving a real problem that most teams do not have. The honest threshold, and what to do below it.