Twelve Years. Thirty Systems. One Standard.
Reflecting on 12+ years of shipping production software — and the single standard that has governed every line of code.
DevDick / Field notes
Engineering decisions, research, setbacks and progress. A closer look at what changes—and what it means for people building software.
Reflecting on 12+ years of shipping production software — and the single standard that has governed every line of code.
Two years of production experience has taught me things I did not know when the first line of SellTrove was written.
Building SellTrove's AI assistant required understanding vector embeddings and semantic search. Here is the practical architecture.
Processing large volumes of money teaches you things about distributed systems that no textbook covers.
Inheriting a legacy codebase is a rite of passage. The engineers who thrive follow a specific approach.
On the psychological reality of building something that takes years — the self-doubt, the silence.
The technology that has been around for 15 years and has solved your exact problem already is almost always better than the technology that came out last year and promises to solve everything.
Engineering for high-speed fibre is trivially easy. Engineering for 2G with intermittent connectivity is where real technical discipline emerges.
Walking through a real outage from the first alert to the last line of the post-mortem — what happened, what slowed the response, and what changed afterwards.
Read new published articles in your RSS reader. No account needed.
Good software starts with better questions.
Explore my work