// HOW I BUILD
The thread through everything I do: take a rough idea and carry it all the way to something real and running — the data, the model, and the product on top.
Most of what I build starts the same way — I notice something clunky, manual, or just worse than it should be, and I can't let it go until I've built a better version. [Add a concrete example: the problem behind one of your projects.]
I'm drawn to problems where messy, real-world data is hiding a clear decision — and where getting it right actually changes what someone does next.
The part I love most is the distance between a rough idea and something that actually runs. I like owning that whole stretch — the data pipeline, the model, and the interface on top — instead of stopping at a notebook.
Tools are just leverage: Python and PyTorch when the answer lives in the data, React and AWS when it needs to reach people. [Optional: name a build you're proud of and the hardest part of shipping it.]
An idea isn't alive until someone else relies on it. A tutoring platform, a tool a sales team opens every day, a model a coaching staff trusts — I care most about work that leaves the laptop and earns real use.
[A closing, personal line — what you're curious about building next, or an invitation to reach out.]
![[About image 3 — replace with assets/about-3.jpg]](assets/about-3.svg)