I notice when something is harder than it should be—for developers, for users—and I can’t leave it alone until it’s fixed and explained.

That reflex started in college: right-click, view source, break until it worked. One week later I had a site and an internship. Pattern locked.

Same loop, bigger stakes:

• Avis Budget Group → 36 hours of MuleSoft → reusable API models that kept a $1.25B launch alive. Still in use.

• Sabre → first contact with REST → wrote the blueprints so the code could actually get written.

• Stripe → no Python → built a full eCommerce app, then rewrote webhooks from real integration pain.

• AWS → no Kubernetes → shipped a live bookstore on EKS (stateful Postgres) + the official developer workshop.

That’s the work: find the friction, build the missing piece, and leave behind documentation that doesn’t punish the next person.

I chase technical novelty the way other people chase levels in a game. I was thinking about self-trained, sentient robots before it was a thing. Now, the future is here. Descartes said, “I think, therefore I am.” AI will say, “I think, therefore I teach.” I’m obsessed with turning the future into something developers can actually use—repeatably and with fewer sharp edges. You’re welcome, world.

If this sounds like you, say hi.