IEEE Publication
Published machine learning research in financial fraud detection using ensemble classification methods.
I design AI products, internal platforms, and distributed systems where latency, reliability, and maintainability matter more than demos. My work spans event-driven architectures, local-first applications, and production AI workflows for teams shipping real software.
Usually available within 24–48 hours. No obligation.
Verifiable proof, research, and technical milestones that back my architectural choices.
Published machine learning research in financial fraud detection using ensemble classification methods.
Honored for outstanding technical communication of systems architectures at academic conference.
Professional background building resilient applications, microservices, and databases in production.
Maintainer of public repositories, tools, and developer assets shared under MIT licenses on GitHub.
Architect of Gitloom (code analysis engine) and Quill (PDF chat platforms) utilizing structured state machines.
Designer of PingPanda, an atomic billing event-streaming architecture handling thundering herd spikes.
I design AI products, internal platforms, and distributed systems where latency, reliability, and maintainability matter more than demos. Too much of today's software is built for the perfect path. My focus is designing explicit boundaries, rate limiters, queue failovers, and transactional invariants so that applications remain stable under thundering herds.
My work spans event-driven webhook architectures (like PingPanda's sub-12ms edge ingress), local-first peer-to-peer applications with zero-cloud dependencies, and LangGraph-directed AI orchestration engines that validate code AST syntax before output generation. I treat engineering as a discipline of trade-offs, where scaling decisions are driven by arithmetic, not hype.
Deterministic AI state machines, local-first data sync engines, and event-driven webhook ingestion systems.
I write software under the assumption that network requests will fail, queues will back up, and user input is unpredictable. Robustness belongs in the architecture.