Hello, world — again

Every engineer remembers their first Hello, world. This is mine, again — over a decade in, after shipping under company names and a consultancy brand, I'm finally writing under my own.

Why now

For most of my career the work spoke through other channels: platforms consolidated, teams built, migrations landed. The lessons stayed in retro boards, architecture decision records and the occasional conference-corridor conversation. That feels like a waste. The problems I work on — scaling engineering organisations, governing AI adoption inside real enterprises, keeping architecture honest while delivery moves fast — are problems a lot of engineering leaders are wrestling with right now, mostly in private.

What I'll write about

Three threads, roughly:

• Engineering leadership at scale. Building nearshore teams from scratch, insourcing from agency partners, and the unglamorous operating-model work that makes delivery predictable.
• Architecture that survives contact with the business. Governance that helps instead of blocks — ADRs, review boards and design authority done with a light touch.
• Applied AI, governed properly. What it actually takes to put LLMs in front of users and agentic tools in the hands of engineers, with human-in-the-loop controls that hold up to scrutiny.

No listicles, no hot takes on whichever framework trended this week. Just field notes from running engineering organisations — the decisions, the trade-offs, and the occasional mistake worth sharing so you don't repeat it.

The stack, since you'll ask

This site is a statically exported Next.js app, styled with Tailwind, animated with Framer Motion, and deployed on Azure Static Web Apps with a small Azure Function behind the contact form. Posts are plain markdown files in a git repository — no CMS, no database, nothing to patch on a Sunday night. The best infrastructure is the infrastructure you don't have to think about.

See you in the next post.