About

The Work

I build software around business processes that are easy to describe but hard to model correctly: COD order operations, invoice reconciliation, shipment evidence, fraud risk, and backend incident response.

The common thread is systems thinking. A useful product needs more than screens and tables; it needs clear state transitions, reliable boundaries, explainable decisions, and enough operational discipline to survive real use.

Engineering Philosophy

I view software engineering less as coding and more as systems design. Before implementation begins, the boundaries of the system must be drawn. How does state mutate? What events trigger those mutations? Where are the bottlenecks? Which decisions need to be reproducible?

• Boring is Better: Use established technology (PostgreSQL, stable frameworks) unless a novel problem demands a novel solution.
• Domain Driven Design: The code must reflect the business reality. If the business relies on complex state transitions, the code should model a state machine.
• Explainability Matters: Risk scores, fraud signals, diagnosis results, and automated decisions should be traceable to evidence.
• Failure is Inevitable: Systems should assume networks will drop, third-party APIs will fail, and databases will lock. Resiliency is built in, not bolted on.

Current Focus

My portfolio is organized around four proof points: InvoiceMix for algorithmic product thinking, Wasilio for COD operations and risk intelligence, ColdTrack for evidence-driven claims architecture, and the backend simulator for production debugging judgment.