
The Amp Hour (my podcast) has always been a great life hack: I can convince folks to talk to me for an hour at a time every, single week. I have met some amazing people that way. As it so happens, I also met my future boss about 10 shows back.
When I announced I was leaving my job at ABB to run Contextual Electronics, Supplyframe took note and offered me a part time gig that I loved and it turned into a full time thing. When I wrote Redirecting Beams back when I joined Hologram, I was making the jump from pure hardware consulting and training into the world of cellular connectivity. When I later wrote Moving up the stack, from hardware to IoT on my way to Golioth, it was because I saw how much firmware and device management was holding back great hardware products.
I’m excited to share what’s next for me: I joined Hubble Network as Developer Relations Lead.
Looking Back at Golioth and Canonical
Leaving Golioth (and more recently, Canonical) is bittersweet. I was the 4th hire there and loved helping people build IoT products with our tech. Over the past five years, I got to work alongside an incredible team. We focused on building open-source as much as possible. I learned more about firmware engineering, more than I ever expected, and built out some really interesting projects. I am super appreciative of all my coworkers who made me into a better engineer.
Golioth got acquired by Canonical earlier this year and I think it’s a really great home for the technology we built. If you haven’t seen, there is a Zephyr LTS 26.04 that will make microcontroller-based products more secure far into the future.
Wait… Bluetooth to Space?
A few months ago, I had Alex Haro on The Amp Hour (Episode #728). He’s the co-founder and CEO of Hubble Network. When you first hear the pitch for Hubble your engineer brain will rightfully react with skepticism. I know mine did. Connecting standard, off-the-shelf Bluetooth Low Energy (BLE) chips directly to satellites in Low Earth Orbit (LEO) sounds bananas. I can barely get it to connect across the room some days.
Alex does a great job explaining it, including the business use cases. Combined with their expanding terrestrial network (100M nodes!), Hubble is making it possible to pull low-bandwidth location and sensor data from sparsely populated areas without adding expensive, power-hungry cellular or traditional satellite modems to the BOM. It was delightfully easy to get a device to talk to a satellite from my home lab last week.
Why This, Why Now?
As I got a taste for small Bluetooth devices at Golioth, I really enjoyed all of the low power, small size challenges. I was making smaller devices than I had in the past because you can only make cell modems so small. I attempted (and succeeded!) making my first board with 0201 components on my home bench, something that I had never tried before.
Contrast this to the other ways that devices connected to the cloud reliably: large battery packs, complex RF environments, ongoing data plans, and specialized modems. The idea that a developer can take an existing BLE microcontroller, flash a lightweight SDK, and suddenly have a global terrestrial and satellite backhaul changes the calculus for how we design products.
Developer Relations again?
This is now the third job I have had as Developer Relations. If you’ve never heard of it, I basically play the part of the engineer experiencing the platform for the first time. I try out the platform with a “beginners mind”, I communicate with other companies, I write blog posts, I make videos, and I build things.
As I alluded to in my last post about firmware, the arena of programming microcontrollers has changed. At Hubble, I’m going to be building reference designs, writing firmware, testing out real-world deployments, and helping developers understand how to integrate Hubble into their own products. Using the Clanker to make helper tools to help visualize what’s happening and understand the difficult world of RF and transmitting to space will be crucial. Leaning on tools like WebSerial to build helper tools with firmware based devices is a particular favorite of mine.
As always, I’ll still be recording The Amp Hour most weeks, talking to people in and around the industry. Lots of Bluetooth and Space ideas are flowing through my head. I am also tinkering on side projects and posting updates on Bluesky and YouTube.
If you’re building devices with BLE and wishing they worked outside the range of a smartphone or local gateway, I’d love to hear from you. I’m just getting ramped up, and I can’t wait to show you what we’re building.
Alternative titles I considered: - Reaching Orbit: Moving from the Cloud to the Constellation - Moving even further up the stack (literally)