Modern device systems do not usually fail because one request is too large. They fail because many reasonable requests arrive at the wrong time, under the wrong retry behavior, with no shared contract between client and server. That pattern shows up most clearly during reconnects. Devices go offline for minutes
AI
A collar microphone cannot tell whose bark it heard. It picks up every sound within range — the dog wearing it, the beagle three doors down, the TV in the background. An audio classifier running on the firmware can label a sound as "bark," but it has no way
Hardware
Why Clock Gating and Controlled Pull Strategies Matter More Than You Think One of the most frustrating problems during embedded hardware bring-up is a system that behaves perfectly after initialisation but randomly fails during power-up. The firmware loads correctly, communication works, and every subsystem appears healthy—until one cold boot
Firmware
How do you count a dog's steps when the dog might be a four-kilogram terrier or a sixty-kilogram mastiff, walking, trotting, or flat-out galloping? You can't hard-code a step frequency, because there isn't one — a small dog's legs cycle nearly twice as
Software
A pet parent opens EverWiz chat and asks, “Is Milo overdue for his rabies booster?” A generic LLM can write a thoughtful essay about rabies vaccination schedules. What it cannot do out of the box is look at this pet's actual vaccination card and give a real answer.
Firmware
A pet wearable has one job above all others: be awake when something happens. A dog doesn't schedule its zoomies, and a collar that has quietly wedged itself into an infinite loop is, for all practical purposes, dead — it just hasn't fallen off the dog yet.
Every successful hardware product begins as a prototype. But a prototype and a product solve fundamentally different problems. A prototype answers the question: "Can this work?" A product must answer a much harder question: "Can this be built repeatedly, assembled efficiently, shipped reliably, and trusted by users
Hardware
In the early stages of hardware development, it is incredibly common for engineers to imagine assembly as a perfectly linear, flawless process. In this idealised world, components arrive exactly on time, boards get populated in a strict sequence, firmware is flashed immediately after assembly, cables are connected correctly, and every
Firmware
A collar-worn pet tracker lives in about the most hostile environment a storage engineer could design on purpose. The battery is tiny, the dog is unpredictable, and the wireless link to the hub drops every time the dog wanders behind the couch. Now picture the worst possible moment: the battery
Technology, Insights and Ideas.
AI
Presence detection sounds solved—motion sensors have shipped for decades. But a real living-space sensor must spot a person sitting dead still, ignore furniture, work in the dark, and not confuse the dog for a human. Our first trigger, a single-channel time-of-flight lidar, failed nearly all of these. Here'
Modern device systems do not usually fail because one request is too large. They fail because many reasonable requests arrive at the wrong time, under the wrong retry behavior, with no shared contract between client and server. That pattern shows up most clearly during reconnects. Devices go offline for minutes
AI
A collar microphone cannot tell whose bark it heard. It picks up every sound within range — the dog wearing it, the beagle three doors down, the TV in the background. An audio classifier running on the firmware can label a sound as "bark," but it has no way
Hardware
Why Clock Gating and Controlled Pull Strategies Matter More Than You Think One of the most frustrating problems during embedded hardware bring-up is a system that behaves perfectly after initialisation but randomly fails during power-up. The firmware loads correctly, communication works, and every subsystem appears healthy—until one cold boot
Firmware
How do you count a dog's steps when the dog might be a four-kilogram terrier or a sixty-kilogram mastiff, walking, trotting, or flat-out galloping? You can't hard-code a step frequency, because there isn't one — a small dog's legs cycle nearly twice as
Software
A pet parent opens EverWiz chat and asks, “Is Milo overdue for his rabies booster?” A generic LLM can write a thoughtful essay about rabies vaccination schedules. What it cannot do out of the box is look at this pet's actual vaccination card and give a real answer.
Firmware
A pet wearable has one job above all others: be awake when something happens. A dog doesn't schedule its zoomies, and a collar that has quietly wedged itself into an infinite loop is, for all practical purposes, dead — it just hasn't fallen off the dog yet.
Every successful hardware product begins as a prototype. But a prototype and a product solve fundamentally different problems. A prototype answers the question: "Can this work?" A product must answer a much harder question: "Can this be built repeatedly, assembled efficiently, shipped reliably, and trusted by users
Hardware
In the early stages of hardware development, it is incredibly common for engineers to imagine assembly as a perfectly linear, flawless process. In this idealised world, components arrive exactly on time, boards get populated in a strict sequence, firmware is flashed immediately after assembly, cables are connected correctly, and every
Firmware
A collar-worn pet tracker lives in about the most hostile environment a storage engineer could design on purpose. The battery is tiny, the dog is unpredictable, and the wireless link to the hub drops every time the dog wanders behind the couch. Now picture the worst possible moment: the battery