About the engineer

Curiosity, made testable.

I am a software developer with interests spanning full-stack systems, AI and data, cybersecurity, DevOps, cloud computing, accessible web engineering, and game technology. The common thread is turning uncertain behavior into something explicit, measurable, and recoverable.

How I work

I prefer small, explicit contracts over invisible assumptions. That means validating external data, documenting tradeoffs, bounding retries and resources, separating domain logic from infrastructure, and treating failure paths as part of the product.

The projects in this portfolio use synthetic data and public-safe scenarios. They are designed to make engineering judgment visible without publishing employer code, customer data, credentials, or unsupported production claims.

Working principles

  1. 01
    Model the failure first.

    Retries, recovery, invalid input, and partial work shape the design.

  2. 02
    Make claims reproducible.

    Tests, benchmarks, and generated reports travel with the source.

  3. 03
    Preserve the reader's time.

    Shallow structure, clear names, fast starts, and explicit limitations.

Role alignment

Broad range, connected by engineering discipline.

Software & full stack

Reliable APIs, stateful workflows, integration boundaries, and accessible interfaces.

AI, ML & data

Reproducible evaluation, deployment gates, monitoring, SQL transformations, and honest model limits.

Systems & cloud

C++, Rust, firmware recovery, protocols, orchestration, containers, Kubernetes, and infrastructure as code.

Games & engines

Deterministic simulation, ECS design, pathfinding, tactical AI, telemetry, and replay verification.

Cybersecurity & DevOps

Defensive detection, identity boundaries, supply-chain verification, GitOps, incident evidence, and measured recovery labs.