Uladzislau Bayouski

In July 1997, the computer on NASA's Pathfinder — fresh from humanity's first successful Mars rover landing — kept rebooting itself. Not radiation. Not a cracked solder joint. A scheduling bug. A low-priority weather task held a shared resource; a high-priority task blocked waiting for it; a medium-priority task hogged the CPU in between. Deadlines were missed, a watchdog panicked, and a spacecraft rebooted — until JPL, from 190 million kilometres away, flipped one setting: priority inheritance, on. That bug has a name — priority inversion — and the machinery that caused and cured it now lives in your thermostat, your smart lock, and a few billion other small computers. It's called a real-time operating system, and the one you'll actually meet is FreeRTOS. ⏱️ The Short Version "Real-time" doesn't mean fast — it means deadlines are part of correctness . The right answer delivered late is a wrong answer. The mental model that actually works: an RTOS doesn...

You've shipped 50,000 smart locks across three continents. A security researcher emails on Tuesday afternoon. There's a buffer overflow in your firmware — exploitable, real, and present on every single lock. Without OTA, your options are recall, truck roll, or hope. Any of those costs millions and takes months. With OTA, you push a signed patch Tuesday evening. By Wednesday morning, 94% of your fleet is fixed. The remaining 6% update themselves when they next connect. That's why OTA isn't a feature. It's a survival mechanism. 🔒 The Short Version OTA (Over-the-Air) updates let you deliver new firmware to deployed IoT devices wirelessly — no physical access, no recall, no technician. The four components every OTA system needs: Update server — hosts firmware images, controls which devices get which version and when Device client — polls the server, downloads, verifies, and applies updates Transport layer — MQTT, HTTPS, or CoAP carrying the image secur...