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.
Inheriting a legacy codebase is a rite of passage. The engineers who thrive follow a specific approach.
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.
A candid look inside building a large-scale platform — the parts going well, the parts that are hard.
Future-you will maintain the code present-you writes. Future-you has forgotten what present-you was thinking.
Technical debt is not inherently bad. Unacknowledged, unmanaged technical debt is.
The documentation tells you what to do. The source code tells you what is actually happening.
Read new published articles in your RSS reader. No account needed.
Good software starts with better questions.
Explore my work