Firmware
A barking dog tells you something. A lunging, barking dog tells you a lot more. On a battery-powered pet collar, the two most informative senses are motion and sound — but you can't run a microphone flat-out all day, and a motion sensor alone can't tell a
Hardware
Designing perceived responsiveness while respecting electrical reality Users rarely judge a product by how fast the hardware actually becomes fully ready. They judge it by how quickly the product appears alive. That difference matters. A device may need several hundred milliseconds, or even a few seconds, before every rail is
Firmware
There is a particular kind of failure that haunts always-on devices, and it almost never shows up in the lab. The firmware runs perfectly for a day, a week, a month — and then, somewhere out in the field, it quietly stops. No crash log, no stack trace, just a device
AI
How we are building a dog facial recognition system from scratch using landmark alignment, metric learning, and a custom-trained embedding model The Problem EverBowl is Hoomanely's precision healthcare deivce for dogs. The bowl monitors eating and drinking habits, ocular temperature, sounds and behavioral patterns over time, turning routine
Firmware
A pet-health monitor doesn't get to reboot when it feels like it. It sits on a kitchen floor, watches a bowl, weighs every meal, listens for chewing, runs computer-vision models on-device, and uploads insights — continuously, for months, unattended. The Linux underneath all of that is not a detail.
Hardware
Why gating and physical safeguards matter before firmware ever gets involved A feature that turns on at the wrong time is not just a firmware bug. In real embedded products, accidental activation can create electrical stress, false sensor readings, unexpected power draw, startup instability, or confusing factory-test failures. Sometimes the
Product
Hardware redesigns rarely happen in isolation. A change to one subsystem ripples outward — and what looks like a simple reduction in sensor count can cascade into new structural constraints, new joining challenges, and a fresh round of stress calculations. This is the story of moving our ring scale from three
Software
Every engineering team eventually encounters the same challenge. A product begins with a clean codebase, a small team, and a clear vision. Features are added quickly, decisions are made pragmatically, and development moves fast. Then growth happens. More developers join. More requirements arrive. More integrations appear. Suddenly, changes that once
Firmware
A dog's weight is arguably the single most predictive number in preventive care. A slow upward creep is the earliest signal of obesity; a slow decline can be the first whisper of kidney disease, dental pain, or a dozen other conditions a vet would love to catch months
Hardware
Every embedded engineer has experienced it. A prototype is running perfectly on the bench. Sensors are streaming data, processors are executing complex algorithms, peripherals are synchronized, and logs indicate everything is healthy. Then someone accidentally unplugs the power cable. The board shuts down instantly. Power is restored a few seconds