Product & software engineer

I build software people can feel the care in.

Full-stack engineer at Tailwind, happiest in the frontend, where a product either earns trust or loses it. I sweat type, spacing, empty states, and the 200 milliseconds nobody asked about.

AI writes plenty of my code now. It doesn’t get to decide when it’s good.

Skip to the work ↓

First things first

I’m a Christian before I’m an engineer.

Jesus is the center of my life, and He is the reason I think small things are worth doing well. If even eating and drinking can be done for God’s glory, so can a form field, a loading state, and a pull request.

So the standard isn’t “good enough to ship.” It’s whether the work honors Him.

So, whether you eat or drink, or whatever you do, do all to the glory of God.
1 Corinthians 10:31 · ESV

What I bring

Typing got cheap. Care didn’t.

  1. Taste

    Building got cheap. Knowing what to build, and what to cut, did not. I start with who it is for and stop when it is good for them.

    Dogleg: one course a day, two minutes a round. The constraint is the product.

  2. Frontend craft

    Design systems, accessible components, motion that means something. I studied Human-Computer Interaction in grad school, I design in the browser, and I can tell when it is off by a pixel.

    Teachings runs on a design system I built on React Aria, in light and dark.

  3. The whole stack

    Schema, row-level security, edge functions, push notifications, then back up to the padding. Nothing gets lost in a handoff when there isn’t one.

    Loaves & Lists: offline PWA with realtime sync. First version shipped in about two hours; 51 migrations since.

  4. Working with agents

    I brief an agent the way I prepare a lesson: plainly, with the hard rules stated as hard rules. Then I check its work against something that can’t be talked out of it.

    Dogleg: 280+ commits co-authored with Claude, every round replayed server-side by the real engine.

Selected work

Mostly built for people I know by name.

Design, off the clock

I teach the Bible. I design the slides, too.

I’m a student at Midwestern Baptist Theological Seminary and serve part-time with the college ministry at my church. When I get to teach, I like to design the slides myself. A careless slide tells the room the content is careless too.

Sola Scriptura is the one I’m proudest of: a whole deck system written in code. Seventeen slide types, one theme file, built straight to Keynote. Because the design lives in the system, an agent can turn my teaching transcript into slides and they come out right: Scripture always in red, creeds and councils quieter beneath it. The hierarchy is the argument.

Cover slide: Sola Scriptura Case Studies, parchment and red blocks beside a cathedral
Sola Scriptura: Case Studies
Twelve slides from the Sola Scriptura deck laid out in a grid
The deck, built from code
Cover slide: The Importance of the Local Church, with a chapel silhouette at sunrise
The Importance of the Local Church
Cover slide: Studying Romans 11, God’s future plan for Israel?
Romans 11
Cover slide: Truth That Leads to Godliness
Truth That Leads to Godliness