InvisibleEngineer.
Home

TOM WIGNALL / INVISIBLE ENGINEER

The engineer behind the invisible.

I'm Tom Wignall. Invisible Engineer is where I share the thinking, experiments and lessons behind the systems we depend on.

A bit about me

I’m Tom Wignall, a technology and platform engineering leader working in the public sector. My background is in hands-on infrastructure, cloud engineering and technical architecture. These days, I spend more time thinking about shared platforms, technical direction and helping engineering teams do good work.

I’m still interested in what sits underneath. Azure, networks, automation, the choices that make a platform easier to operate. A strategy needs to make sense to the people who will build it, support it and get called when it breaks.

I also care about what happens around the technology: how teams share knowledge, how decisions get made, and how we help the next person understand the system they’ve inherited.

Why Invisible Engineer?

The name comes from something I’ve noticed throughout my career. When infrastructure works, people rarely think about it. When it fails, it suddenly becomes everyone’s concern.

Between those moments is a lot of engineering that deserves a closer look. A recovery plan someone actually tested. A manual process nobody needs to repeat. A design decision that makes a failure less disruptive.

Invisible Engineer is a place to talk about that work, and the people behind it. The name describes the engineering, rather than an anonymous person writing about it.

What you’ll find here

I’ll write about cloud and platform engineering, networking, homelab experiments and the human side of technical leadership. Sometimes that means explaining how something works. Sometimes it means looking at a trade-off, questioning an assumption or sharing what an experiment taught me.

The thread running through it is usefulness. What does this make easier? What do we need to understand before depending on it? What would I want another engineer to know?

I don’t expect every answer to fit every environment. I’d rather explain the reasoning and leave room for a different approach.

My Microsoft focus

Much of my cloud experience is with Microsoft Azure. I want to use this space to explore the engineering around it: platform foundations, networking, automation and the practical choices that make an environment easier to run.

The documentation is an important starting point. The next questions are about context. Why choose this pattern? What does it depend on? How would we test it, and what happens when it fails?

I’ll connect that thinking with Microsoft’s architecture guidance, while keeping the writing grounded in the problem we’re trying to solve. Homelabs and the wider engineering world still belong here; useful lessons don’t stop at a product boundary.

Sharing what we learn

A big part of why I do this is to help other people succeed with what I’ve learned. Writing gives me a reason to slow down, make sense of an idea and put it somewhere another person can use it.

My personal website has more on my background and professional focus. You can also find me on GitHub.

If you’re new here, start with why the best infrastructure is the infrastructure nobody notices. It’s the idea behind the name, and a good introduction to how I think about engineering.

FIND AN IDEA WORTH EXPLORING ESC TO CLOSE