p.04 Cover Story
Close
to the Metal
Wojciech Dabrowski writes the code nobody sees — and everybody depends on. A profile of an embedded engineer who measures success in microamps, microseconds and zero field returns.
ProfileGniezno, PL8 min read
10Years in firmware
2Million devices shipped
30Boards brought up
Somewhere between the schematic and the finished product sits a layer of software that has to be perfect on the first try — because once a device is sealed, potted or shipped to a wind farm in the North Sea, there is no "quick fix". That layer is where Wojciech Dabrowski does his best work.
An Embedded Systems Developer based in Gniezno, Poland, he has spent the past decade writing firmware for microcontrollers that run industrial sensors, automotive modules and battery-powered medical wearables. His days are split between an IDE, a logic analyser and a well-worn oscilloscope.
"If it can't survive a brown-out, it isn't finished."
He is known for bringing up new hardware fast: reading the errata before the datasheet, getting a clock tree and a debug UART alive on day one, and building the drivers, RTOS tasks and test harnesses that turn a prototype into a product.
Colleagues describe him as the person you call when a bug only appears at −20 °C, once a week, on one board out of a hundred. He prefers deterministic code, honest timing budgets, static analysis over guesswork, and documentation the next engineer will actually read.
Off the clock he tinkers with open-source RISC-V boards and mentors students entering the field — insisting, every time, that they learn to read a scope trace before they learn to read a framework.