Software engineer

I spent years diagnosing elevators before I ever touched a terminal, tracing a fault through relays and wiring until the real cause gave itself up, because guessing gets people stuck between floors. I build software the same way now: find where the system actually breaks, not where it's convenient to blame, then fix that. The tools changed. The habit didn't.

Recent work

Insurance platforms, coverage assistants, and planning tools, each one built around a constraint that ruled out the easy answer.

Writing

Field notes from the build: what broke, why it broke, and what I'd check first next time.