How we think about the work
Positions drawn from projects we have actually delivered — on performance, AI, cloud, and hiring. No trend summaries, and nothing we could not defend in a scoping call.
Everything we have published
6 articlesPage weight is a business metric, not a technical one
We cut our own site from 81MB of assets to 21MB and nothing on screen got worse. Most heavy sites are not heavy by decision. They are heavy because nobody owned the number.
What we tell clients before they add an LLM to their product
Most requests we get for AI features describe a solution rather than a problem. The useful first conversation is about what happens when the model is confidently wrong.
What running a training programme taught us about hiring engineers
We run free internships alongside client delivery. Watching people learn over weeks made our own interview process look considerably less useful than it did before.
Most cloud migrations do not need a rewrite
The instinct to re-architect everything on the way to cloud is how a migration becomes a multi-year programme that stalls. Move it first. Then fix what the bill points at.
Server rendering, and why your SEO still depends on it
Search engines execute JavaScript now. That has not made client-only rendering safe for anything whose discovery matters to the business.
How we scope a project, and why we sometimes say no
A scoping call that ends in an honest no is worth more to both sides than an engagement that starts on a misunderstanding.
Have a problem that looks like one of these?
A scoping conversation costs nothing and ends with a clear view of approach, a range rather than a number, and the main risks named out loud.