How I build and why

If you made it this far, you probably want to know a bit more about me. I've spent many years building software, and what matters to me hasn't changed since the beginning, watching an idea turn into something that actually works.

Code is only part of the job. Some days it's product thinking, other days architecture, watching a deploy, or staying a little longer to figure out why something that worked yesterday stopped working today. That's production. It has a personality of its own.

I also enjoy helping others grow. A good code review doesn't just point out what's wrong, it leaves the other person understanding something they didn't before.

I care about understanding the problem, discussing decisions when they matter, and finding the simplest, most solid way to ship to production.

I work mainly with TypeScript and Node.js, and keep a close eye on AI and agents because the work is changing fast. I adopt new tools when they genuinely improve the product, the team, or how we work.

I'm finishing a Systems Engineering degree, though my career didn't wait for the diploma. Most of what I know I learned by building and getting things wrong on real systems.