Software
One message stopped testing cold: "my bowl is not getting connected to wifi." We have an FAQ that answers exactly this. The bot escalated anyway — no answer sent, just a ticket sitting in Slack for someone to pick up six hours later. Nothing was broken, technically. Retrieval ran,
AI
In our previous post we hit around 92% identification accuracy on detected frames. That result came with a catch we had quietly set aside: the gallery was built from bowl camera images, evaluated against bowl camera images. What happens when that changes? The Problem With the Current Setup A quick
When I first started working with Grafana, I treated it like a collection of graphs. I could see request counts, latency, error rates, and dozens of other metrics, but I didn't really understand what they were telling me. Every panel looked useful on its own, yet I found
Hardware
Filter placement, return-path proximity, connector-side filtering, trace length control, and shield-boundary discipline EMI problems are often discovered late. The schematic looks correct. The filter components are selected from the datasheet recommendations. The simulation shows attenuation. The PCB passes functional testing. Then the product enters certification testing, and suddenly a few
AI
Our smart bowl fires its camera whenever anything comes within 40 centimetres — a dog's nose, a human's ankle, a broom. That is by design: in the data-collection phase, every visitor is a labeled training sample. But the product question is sharper than the trigger: the bowl
Product
An engineering investigation into how sensor geometry, optics, and software together determine the true field of view of an integrated camera system. Introduction When you build a vision system out of off-the-shelf parts, it's tempting to assume that if the sensor and lens are mechanically compatible, they'
Firmware
Late at night, a smart pet bowl in a customer's kitchen quietly downloads a new operating system, installs it, reboots into it, checks that everything still works — and, finding a problem, silently reverts to the version that was working an hour ago. The owner never notices: no support
Software
Deeplinks Are Distributed Systems in Disguise Why application navigation behaves more like distributed messaging than request routing. For years, I thought of deeplinks as a routing problem. A URL came in, it was parsed, and the application navigated to a screen. It felt deterministic—almost boring. That assumption lasted until
Firmware
Most engineers learn backpressure the moment a fast producer overwhelms a slow consumer: you slow the producer down. But there's a mirror-image problem that gets far less attention. When a device has been offline — a home router rebooted, the ISP hiccuped, the WiFi dropped for an hour — it
Technology, Insights and Ideas.
Most SEO conversations start and end with content - better keywords, longer articles, more backlinks. That's a real part of the picture, but it quietly assumes something worth actually verifying: that search engines, and increasingly AI answer engines, can find your pages, read them correctly, and trust what
Software
One message stopped testing cold: "my bowl is not getting connected to wifi." We have an FAQ that answers exactly this. The bot escalated anyway — no answer sent, just a ticket sitting in Slack for someone to pick up six hours later. Nothing was broken, technically. Retrieval ran,
AI
In our previous post we hit around 92% identification accuracy on detected frames. That result came with a catch we had quietly set aside: the gallery was built from bowl camera images, evaluated against bowl camera images. What happens when that changes? The Problem With the Current Setup A quick
When I first started working with Grafana, I treated it like a collection of graphs. I could see request counts, latency, error rates, and dozens of other metrics, but I didn't really understand what they were telling me. Every panel looked useful on its own, yet I found
Hardware
Filter placement, return-path proximity, connector-side filtering, trace length control, and shield-boundary discipline EMI problems are often discovered late. The schematic looks correct. The filter components are selected from the datasheet recommendations. The simulation shows attenuation. The PCB passes functional testing. Then the product enters certification testing, and suddenly a few
AI
Our smart bowl fires its camera whenever anything comes within 40 centimetres — a dog's nose, a human's ankle, a broom. That is by design: in the data-collection phase, every visitor is a labeled training sample. But the product question is sharper than the trigger: the bowl
Product
An engineering investigation into how sensor geometry, optics, and software together determine the true field of view of an integrated camera system. Introduction When you build a vision system out of off-the-shelf parts, it's tempting to assume that if the sensor and lens are mechanically compatible, they'
Firmware
Late at night, a smart pet bowl in a customer's kitchen quietly downloads a new operating system, installs it, reboots into it, checks that everything still works — and, finding a problem, silently reverts to the version that was working an hour ago. The owner never notices: no support
Software
Deeplinks Are Distributed Systems in Disguise Why application navigation behaves more like distributed messaging than request routing. For years, I thought of deeplinks as a routing problem. A URL came in, it was parsed, and the application navigated to a screen. It felt deterministic—almost boring. That assumption lasted until
Firmware
Most engineers learn backpressure the moment a fast producer overwhelms a slow consumer: you slow the producer down. But there's a mirror-image problem that gets far less attention. When a device has been offline — a home router rebooted, the ISP hiccuped, the WiFi dropped for an hour — it