Irritation‑Driven Development: My Favourite Engineering Pattern

There’s a specific kind of joy that hits when you build something tiny that makes your day easier. Not a platform. Not a framework. Not a “next big thing”. Just a small, sharp tool that removes one annoying piece of friction from your workflow.

It’s the builder’s high - and honestly, it’s one of the best parts of being an engineer.

It Always Starts With an Annoyance

Every small tool I’ve ever built started the same way:

• “Why am I doing this manually again?”

• “This is stupid!”

• “Surely there’s a better way!?”

That’s the spark. Not inspiration. Not a grand vision. Just irritation - and irritation is underrated. If something annoys you repeatedly, it’s probably annoying someone else, too.

Small Tools Matter More Than We Admit

We love to talk about big systems in tech. Architectures. Platforms. Multi‑region deployments. All the impressive stuff.

But the things that actually improve your day? They’re tiny.

A script that cleans up a folder on a schedule. A wrapper that formats logs properly. A shortcut that saves you 10 seconds but feels like magic.

Small tools matter because they reduce friction, create leverage, and compound over time. One improvement leads to another. Your workflow gets smoother. Your brain gets quieter. Your work gets better.

And honestly? They’re fun. There’s something deeply satisfying about building something simple and elegant that just works.

That Moment When It Works

You run the tool. It does exactly what you wanted. And you get that quiet internal “yes”.

It’s not dramatic. It’s not something you’d brag about. But it’s real - that moment where the world becomes slightly more orderly because of something you made.

That’s the builder’s high.

Small Tools Become Ecosystems (Without Trying)

This is the part I love.

You build one tool. Then another. Then a third. Patterns start to form:

• consistent naming

• reusable structures

• shared conventions

• a sense of identity

Suddenly you’re not just building tools - you’re building a toolkit. A personal ecosystem. A set of tiny superpowers that make everything else easier.

Not because you planned it. But because small tools naturally gravitate toward each other.

The Freedom of Building for Yourself

Small tools are the purest form of engineering because you build them for yourself first.

No stakeholders. No deadlines. No Jira tickets. No approval process.

Just curiosity, craftsmanship, and the desire to make your own life easier. It’s engineering without politics. Without ceremony. Without overhead.

Just you and the problem.

And Then, Unexpectedly, They Help Others

Here’s the funny thing: if a tool solves a problem for you, it almost always solves it for someone else, too.

That’s how the best open‑source tools start. Not with a business plan. Not with a roadmap. But with someone scratching their own itch.

Sharing small tools creates a connection. It helps others remove friction. It spreads the builder’s high.

Why I’m Leaning Into Small Tools Right Now

Lately, I’ve been building a lot of small, clean, reusable tools - the kind that make AWS workflows smoother and developer experience better.

Not because I’m chasing a big launch. Not because I’m trying to build a platform. But because these small tools feel good to build. They make my work better. They make me a better engineer.

And over time, they’re forming a consistent ecosystem. And what’s more, I’m enjoying the process. The clarity. The craft. The builder’s high.

Start Small. Start Now.

If you’re feeling stuck or uninspired, don’t wait for a big idea.

Fix an annoyance. Automate a step. Build something tiny that makes your day better.

You’ll be surprised how far those small wins can take you.

And even if nothing big comes from it, you’ll still get that moment - that quiet, satisfying “yes”.

And that’s worth chasing.