Latest · Security
Threat modelling before the first line of code
Most breaches trace back to a design decision, not a coding mistake. Here is the two-hour session we run at the start of every build — and the template we use.
Insights
No thought leadership, no listicles. Write-ups from work we actually shipped, including the parts that did not go to plan.
Latest · Security
Most breaches trace back to a design decision, not a coding mistake. Here is the two-hour session we run at the start of every build — and the template we use.
Most breaches trace back to a design decision, not a coding mistake. Here is the two-hour session we run at the start of every build — and the template we use.
We rebuilt six sites this year. The same four fixes accounted for most of the gain every time — and image budgets were not the biggest one.
Demos are easy. Evaluation harnesses, grounding, injection defence and cost ceilings are what separate a prototype from a product.
What we learned building a patient app for clinics where the connection drops every few minutes — and why sync conflicts are a product decision.
Ninety percent of the failures we audit are not design problems. They are distribution problems — and the fix is a versioned package.
A week-long audit, seven categories of waste and the order we tackled them in. Most of it was not the compute you would expect.
Nothing published on that topic yet.
Work with us
The same engineers who write these articles do the builds. Tell us what you are working on.