I build hardware and document the tradeoffs.
Actuation, sensor fusion, control systems, mechanical design — specific domains, not a generalist list. Here's the background behind the work.
Methodical by necessity, not preference.
My engineering work started with mechanical design and expanded into control systems when I realized that hardware constraints almost always dictate the software architecture — not the other way around.
I debug from first principles. When something fails on hardware, I don't assume the model is wrong — I go back to the physics, the datasheets, and the timing diagrams.
The blog exists because explaining a decision forces you to know whether it was actually the right one. Projects ship; the reasoning gets written up.
Specific areas, not a keyword list.
Actuation & Drive Systems
Sensor Fusion & Perception
Control Systems & Mechanical Design
Motor selection, drive topology, torque budgets, and closed-loop velocity control — from brushless DC to stepper-driven precision stages.
IMU integration, encoder-based odometry, Kalman filtering, and camera-lidar alignment — building state estimates that survive real hardware noise.
PID and state-space controllers tuned on physical hardware, paired with structural design — brackets, linkages, and tolerances that hold under load.
See the full engineering record.
Projects, domains, and timeline — the résumé carries the specifics. The contact page is the next step if anything warrants a conversation.