Hi, I'm Lindsay.

From breaking things to building them

My foundation is in cybersecurity: understanding how software fails, where the weak points hide, and why systems behave the way they do under pressure. That mindset never really leaves you. It's the habit of asking "what happens if this input is hostile?" or "what breaks when this dependency goes down?", questions that turn out to be just as useful when you're the one doing the building.

Over time, the pull shifted from finding problems to making things. I wanted to see an idea go all the way from a blank file to something real that people can use. I lean towards the back end, the data, the systems, the architecture, the parts that keep their weight even as the tools around them change, and I'm unapologetically data-driven: I would rather read the numbers than trade opinions, and a broken calculation is still my favourite kind of bug to chase. Day to day that means C# and .NET, Entity Framework, and Python, with React on the front where it earns its place. I've grown less attached to any one language than I used to be; with modern tooling the problem matters more than the syntax.

What I'm doing now

Most of my building happens under Modus Future, a one-person software studio I run: one method, many products. I develop them the way a small team would, breaking work into tight briefs and running each through AI agents that I review like a teammate's pull request, which is how one person keeps a whole portfolio moving. This site is one of them, rebuilt from scratch. The current chapter is less about building more and more about launching the strongest of them properly.

The security background isn't a separate chapter, it's the lens I build through. It's why every project gets a hardening pass, why I care about doing things properly rather than just getting them working, and why "what happens if this input is hostile?" is a reflex rather than a checklist.

If you're earlier in your own journey, maybe coming from cyber, or just curious about how someone goes from learning to shipping, that's exactly the path I'm documenting on the blog. No gatekeeping; just the honest version, lessons and dead-ends included. When I'm not shipping, I'm usually playing loud music in a band, which is its own kind of debugging.