Technology is easy to admire when everything works. What interests me is why it succeeds, why it fails, and what happens between an idea and a product that people actually use. This site is where I write about that gap.
For more than a decade I have worked across embedded software, connected products, industrial IoT, and systems architecture. I helped build a hardware startup from its first day and spent eleven years growing it before watching it close. Since then I have worked across different industries—from electric vehicle charging and virtual reality to intelligent buildings—seeing how the same engineering challenges reappear in very different forms. My work now focuses on connected products, cybersecurity, software architecture, and digital innovation. Everything I write comes from building products, making mistakes, and living with the consequences—not from theory.
Most of what I write sits somewhere between four recurring themes: embedded systems and firmware, intelligent buildings and connected products, engineering organisations and technical leadership, and the parts of strategy and product thinking that rarely make it into a document.
Engineering doesn't happen in isolation. Every technical decision is shaped by people, products, organisations, and business realities. That's where I think the most interesting lessons are found.
I don't write tutorials for the sake of tutorials. I'm more interested in why certain engineering decisions survive contact with reality while others don't. Whenever possible, personal experience becomes evidence rather than the story itself.
Engineering isn't about writing software. It's about understanding systems well enough to make good decisions.
Whether you work with embedded systems, software architecture, intelligent buildings, or engineering more broadly, I hope you find something useful here.
And if one article changes how you approach a problem, this site has done its job.
