About Me

Hey there!

I started in quality engineering and spent years learning to spot what's broken before anyone else does. That's the lens I still bring to everything I work on now, including AI.

It's also where the name of this blog comes from. In testing, the happy path is the scenario where everything goes right, the user does what they're supposed to, the inputs are clean, and the system behaves. Most software fails in the places nobody bothered to test, the edges and exceptions and "that would never happen" cases that absolutely do. "No Happy Path" is a reminder to stay interested in those places. It's also how I think about most things now, which works beautifully on the demo and quietly breaks on the part of your job nobody wrote down.

My career has run from scrappy startups like RightFarm and Netomi to global players like Emirates Group and Boston Consulting Group, which has given me an unusually wide view of how good software actually gets built and how often it doesn't.

This blog is where I think out loud. Some of it is about AI and how to use it without fooling yourself, which turns out to be harder than the marketing suggests. Some of it is about quality engineering, the craft I came up in. Some of it is about the places those two things meet, which is more often than people expect.

If you've ever shipped something AI-assisted and quietly wondered whether you actually understood it, this blog is probably for you.