An evolving practice 2000s—Now

Skills do not replace each other. They accumulate.

From first programs and webpages to distributed platforms, simulated worlds, and technical leadership. Scroll through the traits that stayed.

Begin evolution

01 / Lineage

Before depth,
there was movement.

The early work was direct: write the code, make the interface respond, ship the idea. The methods changed. The instinct to build did not.

Previous form

A Three.js DNA archive: scroll, bloom, raycasting, and hand-built animation. Explore the archive

Then A site was a collection of effects.
Now Motion is part of the narrative.

02 / Systems

Make it work
where failure is normal.

Applications became services. Services met unreliable networks, heterogeneous devices, high-volume data, and real operational constraints.

  • 01 Software engineering
  • 02 Distributed systems
  • 03 Data platforms
  • 04 Edge resilience

FIELD SYSTEMS / 2018+

Distributed IoT network

Multi-architecture edge nodes, durable telemetry, custom overlay networking, and reproducible deployments in hostile environments.

Read the architecture story

DATA AT SCALE

HPC data platform

Self-serve analyst software and scalable pipelines processing up to 1 TB per minute while reducing annual operating cost.

HPC · Spark · Python · Qt

03 / Simulated worlds

Systems gained
space, motion, consequence.

Engineering crossed into real-time simulation: orbital mechanics, inverse kinematics, finite element analysis, shaders, and data-driven gameplay.

Integrated simulation techniques into Unreal Engine for advanced digital twins—work that contributed to three new deals and a Phase II SBIR contract.

04 / Architecture & leadership

The unit of work
kept getting larger.

First a function. Then a service. Then a platform, a team, a budget, a roadmap, and the responsibility to keep them aligned.

  1. 01

    Developer / Engineer

    Ship under pressure. Improve codebases. Document the decisions.

  2. 02

    Architect / Manager

    Choose stacks, shape solutions, unblock people, and design for change.

  3. 03

    CTO / Director

    Balance requirements, budgets, delivery, maintenance, and teams at scale.

05 / Current form

Still
evolving.

I build across the boundary between software, data, simulation, infrastructure, and organizations—then make those parts work as one system.