I work at the intersection of code, systems, and explanation.
I’ve spent a lot of time thinking about how complex things behave when you let them run: cities, software, processes, habits. That usually pulls me toward simulation-style thinking — breaking big systems into small moving parts, then watching what happens when they interact over time.
Most of my work lives somewhere between engineering and teaching. I care less about abstract correctness and more about whether something actually runs in your head after you read it. If it doesn’t become usable, it doesn’t count as understood.
I tend to build things iteratively. Rough first passes, then refinement, then pressure-testing ideas until they either collapse or become simple enough to explain cleanly. I prefer working code and clear mental models over polished theory.
Outside of tech, my faith in Christ is a quiet but steady part of how I think about purpose, responsibility, and truth. I don’t treat it as decoration or branding — it’s just part of the foundation that shapes how I try to live and create.
I’m also interested in how people actually learn, not how we assume they learn. That usually means stripping ideas down to their working parts, removing unnecessary ceremony, and rebuilding them in a way that feels more direct and less intimidating.
If there’s a common thread, it’s this: I like building systems that make other systems easier to understand.
