Welcome to Capslock IT

I’m glad you found your way here.

This blog is the part of Capslock IT where I step out from behind the project descriptions and the service pages, and simply talk about the work itself. The things I build. The systems I run. And the lessons that stick with me long after a project is done.

IT and software development have been a constant thread through my life for years now. First as curiosity. Then as a craft I kept returning to. And by now as something close to a calling.

What keeps me coming back is rarely the finished product alone. It’s the process. The moment a stubborn bug finally gives up its secret. The satisfaction of a deployment that simply works. The quiet pride in a piece of infrastructure that keeps humming along long after you’ve stopped thinking about it.

Those moments rarely make it into a portfolio. But they’re often where the real learning happens, and they’re exactly what I want to write about here.

Why I’m writing this down

Plenty of the things I run into while building software or operating infrastructure are small.

A configuration quirk that costs an evening. A tool that turns out to fit a problem perfectly once you look at it from a slightly different angle. A workflow that finally clicks after the third attempt at getting it right.

None of these are headline news. But together they form the kind of practical knowledge that’s genuinely useful to have, and genuinely satisfying to pass along.

I also believe that sharing experiences, openly and without polishing away the messy parts, makes the field a little better for everyone in it.

The write-ups that have helped me the most over the years were rarely the glossy, perfectly produced ones. They were the honest accounts of someone who ran into a wall, figured out a way around it, and took the time to explain how. I’d like this blog to belong in that tradition, even if just in a small way.

What you can expect to find here

• Notes from real projects: what worked, what didn’t, and why it mattered
• Short, practical write-ups on tools, workflows, and infrastructure setups
• Reflections on how IT and software development should, and shouldn’t, be done
• The occasional story from the messier side of a project, the parts that rarely make it into a case study but often teach the most

I won’t promise a fixed schedule or a tightly defined topic list.

Instead, I’ll write when I have something worth saying. And I’ll try to make sure that when I do, it’s something you can actually use. Whether that’s a technique to borrow, a mistake to avoid, or simply the reassurance that you’re not the only one who’s been stuck on a problem like this.

A standing invitation

If something here resonates with you, sparks an idea, or you’d simply like to trade notes on a similar experience, I’d love to hear from you.

You’ll find my contact details on the homepage, and I always enjoy a good conversation about the things we build and the systems we keep running.

Thanks for stopping by, and welcome to Capslock IT.