Systems & AI
Architecture, operations, verification, and ownership when implementation gets faster.
Systems · AI · Machines in the real world
Field notes on what engineers must understand, verify, and own when AI accelerates implementation and software begins acting in the physical world—from distributed systems to sensors, power, networks, and motion.
Architecture, operations, verification, and ownership when implementation gets faster.
Where sensors, power, networks, and actuators test every software assumption.
Failures, measurements, changed decisions, and evidence that can be reproduced.
Latest field note
A 2003 programming book predicted that coding would get easier while systems got harder. AI arrived; judgment, verification, and ownership matter more.
Read the latest entry →Start with the newest entry, or follow how the decisions and experiments evolved over time.
Finding similar ideas at ROSCon changed my next milestone: one recorded robot failure, AI-assisted investigation, and a replay test that can prove a fix.
Directional Wi-Fi throughput, a low-battery plot twist, missing logs, and the cleaner experiment that came out of a robot debugging session.
Charging downtime, vendor power guidance, the external bench-PSU solution, and the questions it raised about power paths and autonomous docking.
Why VNC is the wrong long-term abstraction and how an RTX 4090 Ubuntu workstation could become a native ROS 2 participant.
Hardware verification, ROS inventory, measured battery telemetry, SSH friction, and the strategy for a recoverable full-disk backup.
Arrival, assembly friction, wiring questions, display issues, and the realization that robotics starts below ROS.
Preparing Ubuntu, ROS 2, and an RTX 4090 workstation before depending on the robot-side Jetson as the only development machine.
The M3 Pro purchase decision, the risk I accepted, and the plan to verify, understand, back up, and eventually move beyond the vendor stack.
The requirements, tradeoffs, security concerns, and Jetson decision behind choosing a mobile manipulator as a first robotics laboratory.
The two-year adaptation goal, ten-year horizon, and why failures and beginner questions belong in the permanent engineering record.