The seams are where the work gets interesting.

I'm a software engineer drawn to the seams, the places where intent, data, and interface disagree. Most of that work has been on the front end, and it's where I learned to take those disagreements seriously.

My work follows a small pipeline: shape, research, write, execute, compound. The goal is that each feature makes the next one easier to build. I keep state explicit and data flow obvious, and I avoid clever tricks so the code stays correct and stable.

Bloomington, Indiana.