Why I'm Writing This

I should be upfront about something: I'm not a natural content creator. I don't have a history of blogging, or building an audience. If you'd told me five years ago that I'd be publishing a series about what I'm building and how I'm building it, I'd have found that unlikely. I've always been more comfortable doing the work than talking about it.

So why start now?

Because I believe something fundamental is shifting in how software gets built, and that shift changes who can build what — and how those people need to show up.

The rise of AI agents that can interact with real engineering toolchains — Jira, GitHub, AWS, the lot — means that a single person with the right experience and judgement can produce work that used to require a team. I'm living that right now, by helping to build ideas some of my friends have.

If that trend continues — and I believe it will — we're looking at a world where independent consultants and solo founders can operate at a scale that wasn't previously viable. The barriers to building serious software are dropping. Not because the work is getting easier, but because the leverage available to one person is getting dramatically better.

Here's the thing about that world, though: if you can build at team-scale as an individual, the bottleneck shifts. It's no longer about whether you can do the work. It's about whether anyone knows you exist.

That's uncomfortable for people like me. I'd rather let the work speak for itself. But in a market where more people can produce quality work independently, the ones who document what they're doing — who make their thinking visible, who show how they approach problems — are the ones who get found. Not because self-promotion is suddenly virtuous, but because it's becoming necessary. The independent consultant's portfolio isn't a CV anymore. It's a body of visible work and visible thinking.

So that's what this blog is. It's not a tutorial series. It's not content marketing. It's me documenting the journey of building Estyn — the decisions, the architecture, the ways of working, the mistakes — as honestly as I can. Partly because someone else might find it useful. Mostly because putting myself out there is something I need to start doing, and this felt like the most authentic way to do it.

If you're in a similar position — someone who's good at the work but not naturally inclined to talk about it — maybe these posts will resonate. Or at the very least, maybe seeing someone else wrestle with the same reluctance will make it feel a bit more approachable.

Right. That's the preamble done. Let's get into it.