<?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: Rajiv </title>
    <description>The latest articles on DEV Community by Rajiv  (@rrajivnair).</description>
    <link>https://dev.to/rrajivnair</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%2F4077469%2F140b82a8-be29-49d6-8ad0-e573b891d302.png</url>
      <title>DEV Community: Rajiv </title>
      <link>https://dev.to/rrajivnair</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rrajivnair"/>
    <language>en</language>
    <item>
      <title>Bad code</title>
      <dc:creator>Rajiv </dc:creator>
      <pubDate>Fri, 14 Aug 2026 10:19:20 +0000</pubDate>
      <link>https://dev.to/rrajivnair/bad-code-34cd</link>
      <guid>https://dev.to/rrajivnair/bad-code-34cd</guid>
      <description>&lt;p&gt;&lt;strong&gt;Stop Writing Bad Comments: A Guide to Meaningful Code Documentation&lt;/strong&gt;&lt;br&gt;
Most code comments state the what instead of the why. If your comment just repeats what the code clearly shows, it is noise. Clean code should tell a story, and comments should only fill in the missing context.&lt;br&gt;
&lt;strong&gt;The Golden Rule&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Write code that is easy to read.&lt;/li&gt;
&lt;li&gt;Use comments only when code cannot explain the intent.&lt;/li&gt;
&lt;li&gt;Delete outdated comments immediately.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>code</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
