I started in finance. Now I build software.
I'm a data architect, although that's only part of what I do these days.
My career started in finance, then moved through product management, customer success, data engineering, and eventually architecture. I didn't plan that progression. I just kept getting interested in the problems on the other side of whatever I was working on.
I've spent much of my career untangling complicated data systems. I've built platforms handling more than 12 million records a day, helped cut cloud costs from $75,000 to $8,000 a month, and replaced plenty of manual processes with something that actually works.
I enjoy the architecture, but I've always been more interested in what people can do with the technology than the technology itself.

Now I'm building the whole thing.
For years, my work largely stopped at the data. I'd build the pipelines, design the models, and put dashboards on top. But I usually had ideas for the actual software people needed.
Coding agents have made it practical for me to build that part, too. I can work across the database, interface, and deployment without needing a team for every idea.
I've now shipped six software products, including five apps on the App Store.
They range from a physical therapy platform using computer vision to a personal journaling app, travel planning tools, and games for kids.
There's no grand strategy connecting them. They're things I wanted to exist, problems I thought I could solve, or ideas I wanted to test.
And that's probably what I enjoy most about building software now. I can have an idea on Tuesday and find out whether it's any good by Friday.
Outside of work
I ran Division I track at UConn and have completed five marathons. Running is still a big part of my life, although these days I'm usually chasing a personal best rather than anyone else.
I also write Field Notes, mostly about data architecture, software, and what I'm learning while building with AI.
I tend to explain technology using everyday things: driving through a city, running a restaurant, or bowling. Sometimes an analogy makes a technical problem easier to understand than another diagram full of boxes and arrows.
This site is where I share what I'm building, what I've learned, and occasionally what I got wrong.