How I Work

Principles I follow when building software — shaped by nearly a decade of shipping production systems for international teams.

  1. 01

    Document important decisions

    Decisions and gotchas live in a knowledge base and the plan, not in someone's head. If a correction will matter again, it gets written down.

  2. 02

    Prefer simple architectures

    The best system is the one the team can understand and evolve. I avoid unnecessary layers and premature abstraction.

  3. 03

    Optimize for maintainability

    Readable code, consistent patterns, and solid test coverage matter more than clever one-liners.

  4. 04

    Use AI to accelerate delivery

    I set the outcome and the boundaries, then use agents to draft, explore, and take the repetitive pass. Nothing customer-facing or irreversible goes out without my review.

  5. 05

    Measure before optimizing

    Profiling, metrics, and benchmarks come first. I fix bottlenecks backed by data, not assumptions.

  6. 06

    Focus on business outcomes

    I track the user-visible result and keep the change list in the plan. The work earns its place by moving reliability, cost, or the product.

  7. 07

    Verify the real artifact

    A green test suite is not proof the change works. I check the surface that ships: the page in a browser, the live HTTP response, or the generated file.

  8. 08

    Corrections become rules

    When a mistake shows up again, I write the rule and the reason. The next session starts from that rule, not from memory.