What we are reading, building, and arguing about
Updates from the team on the technologies we work with day to day. Written when we have something specific to say, not to fill a publishing calendar.
Why Next.js became our default for client work
What server rendering actually buys you, where the App Router still has sharp edges, and the cases where a plain single-page app is still the better answer.
All insightsEverything else we have published
Short pieces on the work: frameworks, design, cloud, security, and the commercial questions that arrive with them.
What is actually changing in web development in 2026
The shifts we are betting on for client work, and the ones we are content to wait out.
Why we keep taking things off the screen
Restraint is not a style preference. It is what happens once you decide who the screen is for.
Replacing a system while people are still using it
What a rebuild costs a business that cannot pause the work the old system supports.
What we settle before writing any mobile code
Store rules, device spread, offline behaviour, and a release cadence you can sustain past month three.
Putting a model into software people already use
Where machine learning earns its place in a product, and where a rule and a lookup table do the job better.
The security work that happens before launch
Access control, secrets handling, dependency updates, and who holds the keys after handover.
The longer pieces live in Insights
Positions taken from projects we have actually delivered: page weight, machine learning in production, cloud migration, and training engineers. Nothing there we could not defend on a call.