SYSTEMS ARCHITECT · WEB · AIR · SEA · GROUND
Web, air, sea and ground, by the same hand.
Ten years of shipped systems: web products sold to strangers, a drone release pipeline, marine docking control designed in a simulated sea first, and autonomy software I co-lead for ground robots.
THE STACK, EXPLODED
Ten years, seven layers
Seven chapters, ten years, and machines that went from browsers to boats, drones and patrol robots. Every chapter ran on a different stack and lit different layers of it. Pick a chapter to read it.
Talk to me about
- 01Architecture reviews.A target architecture your platforms can share: ports and adapters, ADRs, and configuration that swaps stacks instead of forking them, from the web tier to the ROS 2 graph.
- 02Simulation strategy and digital twins.A simulator-to-stack contract in Isaac Sim, Omniverse, CARLA or Webots: sensor rigs matched to the real machine, and software-in-the-loop runs your team can repeat.
- 03Operator tooling.What the person at the console sees, and how late it may arrive: web dashboards on a custom streaming server, camera streams held to a latency target, mission control on a QGroundControl fork speaking MAVLink to PX4.
- 04Safety and handover.An autonomy safety layer drawn into the architecture: mission management, a hierarchical state machine that escalates, a timed handover to a teleoperator, and requirements traced to ISO 26262, SOTIF and UL 4600.
- 05Release engineering.The build decides what the field runs: CMake and Conan builds lean enough to package, .deb packages cut in GitHub Actions, and Docker and Terraform for the cloud around the machines.
- 06Shipping with coding agents.Harnesses that check every change against decision records and golden tests, with the final review left to your engineers.
Bring the boundary your team trusts least; that is where a review starts. Start the conversation →