<?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: Manoj</title>
    <description>The latest articles on DEV Community by Manoj (@manojge).</description>
    <link>https://dev.to/manojge</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3606576%2F09dfa08c-e03a-41fd-88da-807133d5512e.png</url>
      <title>DEV Community: Manoj</title>
      <link>https://dev.to/manojge</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/manojge"/>
    <language>en</language>
    <item>
      <title>Understanding the C Compilation Process</title>
      <dc:creator>Manoj</dc:creator>
      <pubDate>Sun, 23 Nov 2025 18:20:42 +0000</pubDate>
      <link>https://dev.to/manojge/understanding-the-c-compilation-process-5b91</link>
      <guid>https://dev.to/manojge/understanding-the-c-compilation-process-5b91</guid>
      <description>&lt;p&gt;This article grew out of my journey to revisit C from a systems perspective. Most of my career has been in Notes/Domino, Java, and Drupal, and although I learned C during my university years, I never used it extensively in practice. Lately, my curiosity has pushed me to return to the fundamentals and understand what really happens beneath the surface. This article is for anyone who shares that same curiosity—those who want to peek under the hood and see what truly happens when we hit &lt;em&gt;compile&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;This article is the first entry in a learning packet I’m putting together called &lt;em&gt;What Happens to Your C Program When It’s Compiled&lt;/em&gt;. We begin with the preprocessing stage—the starting point of the compilation process.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Hosted on GitHub:&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
&lt;a href="https://github.com/manojge/bitsofbeing/blob/main/packets/understanding-c-compilation-preprocessing.md" rel="noopener noreferrer"&gt;Understanding the C Compilation Process — Part I: Preprocessing&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Understanding Complement Arithmetic: Why Computers Subtract by Adding.</title>
      <dc:creator>Manoj</dc:creator>
      <pubDate>Tue, 11 Nov 2025 22:02:23 +0000</pubDate>
      <link>https://dev.to/manojge/understanding-complement-arithmetic-why-computers-subtract-by-adding-2kff</link>
      <guid>https://dev.to/manojge/understanding-complement-arithmetic-why-computers-subtract-by-adding-2kff</guid>
      <description>&lt;p&gt;Thirty years after first learning 2’s complement, I revisited it — not just to remember how it works, but to understand why it works. What I found was a surprisingly elegant bridge between 17th-century mechanical calculators and modern binary arithmetic.&lt;/p&gt;

&lt;p&gt;If you’ve ever wondered why flipping bits and adding one turns subtraction into addition, this deep dive might surprise you.&lt;/p&gt;

&lt;p&gt;🔗 Read the full packet: “Subtraction Through Addition: The Power of Complements&lt;/p&gt;

&lt;p&gt;Hosted on GitHub:&lt;br&gt;
&lt;a href="https://github.com/manojge/bitsofbeing/blob/main/packets/understanding-complement-arithmetic.md" rel="noopener noreferrer"&gt;Understanding Complement Arithmetic&lt;/a&gt;&lt;/p&gt;

</description>
      <category>c</category>
      <category>beginners</category>
      <category>computerscience</category>
      <category>history</category>
    </item>
  </channel>
</rss>
