About Me

I'm an engineer who believes complexity is a cost that compounds. Simplicity enables speed. The investment in simplicity pays back on every future change.

How I Think About Code

Code is a graph. Modules and functions are nodes, dependencies are edges. I care about software architecture — how things connect at the system level — more than the polish of individual functions. A messy function that's isolated? Fine. A bad abstraction in a core module everything depends on? That's the real problem.

Not all code deserves the same attention. I invest heavily where impact is high: database schemas, core modules, type systems. I'm comfortable with mess in one-off scripts, frontend experiments, or areas where the design is still uncertain. The mess that matters is the mess that spreads.

Product Sense

Technical judgment without product context is meaningless. Every technical decision is a bet on what the software needs to do. I develop product sense by using software until it doesn't feel shitty, talking to customers directly, and understanding why priorities are what they are.

Current Interests

• LLMs and AI tooling — Practical applications, structured outputs, developer tools. Building Instructrice for typed LLM outputs in PHP.
• Home automation — Building systems that actually work reliably, not just demo well.
• 3D printing — Functional parts, not trinkets.

Connect

GitHub · Twitter · LinkedIn · Printables