Engineering Culture
The Answer Without the Question
A case study in how AI can encourage confidence when the limits of the analysis are not made clear.
The invisible forces that bend outcomes. Code review as teaching, email as a signal not a weapon, deep work respected, and a bias to show your working. The code belongs to everyone, and shoes matter because craft lives in details.
Engineering Culture
A case study in how AI can encourage confidence when the limits of the analysis are not made clear.
Developer Experience
Players only see production. Engineers live in the systems behind it. When those systems fail, the product fails later. The two worlds are closer than they look.
Player Experience
Most slowdowns in an SPA come from one place. Too much work ends up hanging off a single thin thread inside the browser, and the moment it strains, the whole product feels it.
Developer Experience
Sometimes the fastest way to find out what’s broken is to try to ship it.
Engineering Culture
Why the freedom that makes the web powerful also makes it fragile.
Developer Experience
Why code review must be predictable, humane, and measured.
Organisational Design
The practices that make companies faster, safer, and engineers more valuable.
Developer Experience
Clarity in the address line is clarity in the organisation.
Developer Experience
Why visible fixes build knowledge, demonstrate competence, and strengthen trust.
Developer Experience
Real-user monitoring is our market feed. Hide it, and we trade blind on player experience.
Developer Experience
The right shoes are the ones closest to production.
Developer Experience
Inner sourcing only works when making changes is easy. Standards make that possible.