My curiosity has always lived one layer below the screen — in the routing, the queries, and the quiet machinery that decides whether an app feels instant or broken. A year at Cestrum took that curiosity into production: building APIs for a community of thousands taught me restraint, securing them taught me healthy caution, and the bugs that only appear under real traffic taught me more than any tutorial could.
My habit is to think in trade-offs before thinking in code. Competitive programming taught me to ask "what does this cost?" before writing a single line, and system design keeps asking the same question at a larger scale — what to cache, what to queue, and what to let fail gracefully.
My projects usually begin as complaints. Code reviews felt slow and inconsistent, so I built MergeMind, where five specialised AI agents split a pull request, review it in parallel, and return one coherent verdict. Incident response kept scattering across Slack threads and GitHub issues, so I'm building IncidentOS to bring triage into a single, reliable place.
Along the way I've earned my stripes as an AWS Solutions Architect and an Oracle Certified Professional. I treat them as a floor, not a ceiling — proof of the fundamentals, while the real learning happens in whatever I'm building next.