Loading…
Loading…
Technical articles
Written by hand, not generated: engineering notes on the parts of a system that only reveal themselves after real users arrive. Longer and more specific than a blog post, because the details are where the decisions are.
Published by Shahram Mazar at Mazarix
Taking the order is the part that works. Everything after it — stock that stops agreeing, a hundred orders each needing a different action, returns, receipts, the question of what actually sold this year — is where a shop either has a system behind it or does not.
Read the articleA feature can be finished for a week and still not be in anyone's hands. What sits in that gap is usually a person, a set of steps they remember, and an evening nobody wanted to spend. This is what a pipeline replaces, stage by stage.
Read the articleAn application that runs in a demo and an application that holds up under real users are two different things. This is the gap between them: the families of failure that live in it, and which layer of testing catches which.
Read the articleEngineering
Each article argues one part of the stack in full. The rest of the reasoning — language, runtime, database, infrastructure, delivery — is set out on the engineering page.
A column rename breaks the build, not a page at 2am.
One language across the whole system, and a library for nearly everything else.
A rule that lives in the database cannot be skipped by a bug in a screen.
A page that takes four seconds is a page most people never scroll.
No server sitting in a cupboard for someone to forget to patch.
The waste is rarely one large problem. It is twenty small handoffs.
Releases stop being events.
Software that runs is not the same as software that works.
Industry news is summarised and credited to its source. These articles are original work.