<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Generics on Rusty Eddy</title><link>https://rustyeddy.com/tags/generics/</link><description>Recent content in Generics on Rusty Eddy</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 31 May 2026 08:52:27 -0700</lastBuildDate><atom:link href="https://rustyeddy.com/tags/generics/index.xml" rel="self" type="application/rss+xml"/><item><title>Building an IoT Device Abstraction Layer in Go</title><link>https://rustyeddy.com/iot/building-iot-device-manager-in-go/</link><pubDate>Sun, 02 Nov 2025 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/iot/building-iot-device-manager-in-go/</guid><description>&lt;p&gt;IoT applications get hard to maintain when hardware code and application
logic are tangled together. A prototype can read one GPIO pin or one I2C
sensor directly. A real system has sensors, actuators, timing loops, message
publishing, local storage, APIs, dashboards, and failures that happen at the
edge.&lt;/p&gt;
&lt;p&gt;The useful boundary is a device abstraction layer: hardware-specific drivers
stay below it, application logic stays above it, and the two communicate
through small interfaces.&lt;/p&gt;</description></item></channel></rss>