<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: sunny</title>
    <description>The latest articles on DEV Community by sunny (@electelem).</description>
    <link>https://dev.to/electelem</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4253934%2F0dce493c-1a66-4622-8472-62446b599684.png</url>
      <title>DEV Community: sunny</title>
      <link>https://dev.to/electelem</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/electelem"/>
    <language>en</language>
    <item>
      <title>Writing Firmware for Hardware You Can Change</title>
      <dc:creator>sunny</dc:creator>
      <pubDate>Thu, 19 Nov 2026 13:35:34 +0000</pubDate>
      <link>https://dev.to/electelem/writing-firmware-for-hardware-you-can-change-5fba</link>
      <guid>https://dev.to/electelem/writing-firmware-for-hardware-you-can-change-5fba</guid>
      <description>&lt;p&gt;There is a luxury in embedded work that most software engineers never get: if the hardware is being designed at the same time as the firmware, you can change the hardware. Need a different pin, an extra test point, a bus moved off a noisy trace? If the board is not locked yet, you ask for it.&lt;br&gt;
That only works when the firmware and hardware teams are the same team, or at least in constant contact. Real-time &lt;a href="https://elementalelec.com.au/software-development-services" rel="noopener noreferrer"&gt;firmware development&lt;/a&gt; benefits enormously from influencing the schematic before it is frozen, rather than coding around decisions made months earlier.&lt;br&gt;
It changes how you architect things. You design the firmware and the board as one system, and you end up with cleaner drivers, fewer workarounds, and a product that is easier to test.&lt;br&gt;
Elemental Electronics works this way, developing firmware next to the hardware.&lt;/p&gt;

</description>
      <category>hardware</category>
      <category>softwareengineering</category>
      <category>systems</category>
    </item>
  </channel>
</rss>
