About Me

I design and ship embedded systems where firmware, electronics, and mechanical constraints all have to agree. My work sits at the intersection of bare-metal firmware, RTOS-based products, and production-ready PCB design.

Over the years I've built controllers for industrial valves, sensor networks for agriculture, and BLE nodes for industrial monitoring. What I care about most is systems that stay reliable in the field — not just demos that work on a lab bench.

How I work

I start from the problem constraints: power budget, thermal limits, EMI, cost, and maintainability. Architecture decisions come next — MCU selection, bus topology, boot strategy, OTA path — then schematic, layout, and firmware in tight iteration loops.

Documentation is not an afterthought. Every project I ship includes design rationale, failure modes, and enough detail that another engineer can pick it up months later.

Outside the lab

When I'm not debugging a stubborn I²C bus, I write about embedded practice, contribute to open firmware experiments, and mentor engineers moving from application software into hardware-aware development.