<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engineering on EnRedAndo Me - Carlos Prados</title><link>https://carlos.enredando.me/categories/engineering/</link><description>Recent content in Engineering on EnRedAndo Me - Carlos Prados</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>mail@carlosprados.com (Carlos Prados)</managingEditor><webMaster>mail@carlosprados.com (Carlos Prados)</webMaster><copyright>© 2026 Carlos Prados</copyright><lastBuildDate>Sun, 19 Apr 2026 12:00:00 +0200</lastBuildDate><atom:link href="https://carlos.enredando.me/categories/engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Build for the Field, Not the Lab: Shipping OTA Updates to NB-IoT Devices</title><link>https://carlos.enredando.me/posts/build-for-the-field/</link><pubDate>Sun, 19 Apr 2026 12:00:00 +0200</pubDate><author>mail@carlosprados.com (Carlos Prados)</author><guid>https://carlos.enredando.me/posts/build-for-the-field/</guid><description>&lt;h2 class="relative group"&gt;Fleet Health Is the Product
 &lt;div id="fleet-health-is-the-product" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#fleet-health-is-the-product" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;The industry sells IoT as if data were the point. It isn&amp;rsquo;t. Data is the receipt. &lt;strong&gt;Fleet health is the product.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;A thousand sensors in the desert, a gas meter in every flat of a rural town, a cold-chain tracker strapped to a pallet crossing a border — none of that is worth anything if the fleet degrades between my laptop and the real world. Every device that silently goes dark, every firmware bug that bakes in without a way out, every slot of flash with a bricked image — each of those is a direct cut into whatever value the product was supposed to deliver.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://carlos.enredando.me/posts/build-for-the-field/featured.jpg"/></item><item><title>Breaking the Chains: Why I Built Keystone to Replace AWS Greengrass</title><link>https://carlos.enredando.me/posts/why-keystone/</link><pubDate>Mon, 16 Feb 2026 12:00:00 +0100</pubDate><author>mail@carlosprados.com (Carlos Prados)</author><guid>https://carlos.enredando.me/posts/why-keystone/</guid><description>&lt;h2 class="relative group"&gt;The Vendor Lock-in Trap
 &lt;div id="the-vendor-lock-in-trap" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-vendor-lock-in-trap" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;For the better part of the last decade, the industry narrative around IoT has been dominated by a &amp;ldquo;Cloud-First&amp;rdquo; mentality. The premise was seductive: treat your edge devices as dumb pipes and offload the heavy lifting to the cloud&amp;rsquo;s infinite compute.&lt;/p&gt;
&lt;p&gt;However, as we moved from prototypes to production at scale, cracks began to appear in this facade. Latency mattered. Bandwidth costs exploded. But most importantly, we realized that by adopting managed edge runtimes, we were walking into a trap of architectural dependency.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://carlos.enredando.me/posts/why-keystone/featured.jpg"/></item></channel></rss>