<?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: Vedant</title>
    <description>The latest articles on DEV Community by Vedant (@vedamnn).</description>
    <link>https://dev.to/vedamnn</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%2F4039355%2Fdc228009-87fb-4e46-ae6a-aed4c454da66.gif</url>
      <title>DEV Community: Vedant</title>
      <link>https://dev.to/vedamnn</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vedamnn"/>
    <language>en</language>
    <item>
      <title>How does code make hardware work ???🤐</title>
      <dc:creator>Vedant</dc:creator>
      <pubDate>Tue, 21 Jul 2026 06:35:37 +0000</pubDate>
      <link>https://dev.to/vedamnn/how-does-code-make-hardware-work-systemsprogramming-embeddedsystems-1hgm</link>
      <guid>https://dev.to/vedamnn/how-does-code-make-hardware-work-systemsprogramming-embeddedsystems-1hgm</guid>
      <description>&lt;p&gt;Have you ever wondered how a few lines of code can make your keyboard respond ⌨️, your SSD store data 💾, or your GPU render millions of pixels every second? 🎮&lt;br&gt;
At first glance, it almost feels like magic.&lt;br&gt;
We write code.&lt;br&gt;
The CPU executes it.&lt;br&gt;
The hardware somehow responds.&lt;br&gt;
But... what actually happens in between? 🤔&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F41j9rar3himf8yl5p5zj.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F41j9rar3himf8yl5p5zj.png" alt=" " width="800" height="1200"&gt;&lt;/a&gt;&lt;br&gt;
How does software communicate with physical electronics?&lt;br&gt;
More importantly...&lt;br&gt;
How does a device know that the CPU wants to talk to it and not to something else?&lt;br&gt;
These questions led me down a fascinating rabbit hole into computer architecture and operating systems.&lt;br&gt;
I realized that the CPU doesn't naturally understand concepts like a keyboard, GPU, SSD, or even a mouse. It simply executes instructions and works with addresses.&lt;br&gt;
Everything else is built on top of carefully designed mechanisms that allow software and hardware to communicate efficiently.&lt;br&gt;
And understanding those mechanisms isn't just useful for operating systems.&lt;br&gt;
It's also one of the foundations for understanding device drivers, reverse engineering, firmware, and even advanced cybersecurity concepts. 🔐&lt;br&gt;
This post is the beginning of a series where I'll document my journey into the systems that make modern computers work—from silicon to security. ⚙️&lt;/p&gt;

&lt;p&gt;Next up:&lt;br&gt;
If the CPU doesn't know what a keyboard or GPU is... how does it communicate with them?&lt;/p&gt;

</description>
      <category>assembly</category>
      <category>computerscience</category>
      <category>architecture</category>
      <category>iot</category>
    </item>
    <item>
      <title>[Boost]</title>
      <dc:creator>Vedant</dc:creator>
      <pubDate>Tue, 21 Jul 2026 06:33:48 +0000</pubDate>
      <link>https://dev.to/vedamnn/-2ncg</link>
      <guid>https://dev.to/vedamnn/-2ncg</guid>
      <description></description>
    </item>
  </channel>
</rss>
