<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nithin Satheesan on Medium]]></title>
        <description><![CDATA[Stories by Nithin Satheesan on Medium]]></description>
        <link>https://medium.com/@nithinsatheesan?source=rss-a2dffd1c8c60------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*kp7uBxFsK06FAs1c.</url>
            <title>Stories by Nithin Satheesan on Medium</title>
            <link>https://medium.com/@nithinsatheesan?source=rss-a2dffd1c8c60------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 17:48:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nithinsatheesan/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Write better programs by proper naming]]></title>
            <link>https://medium.com/@nithinsatheesan/write-better-programs-by-proper-naming-a43d6c0a30f7?source=rss-a2dffd1c8c60------2</link>
            <guid isPermaLink="false">https://medium.com/p/a43d6c0a30f7</guid>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Nithin Satheesan]]></dc:creator>
            <pubDate>Fri, 15 Feb 2019 13:38:26 GMT</pubDate>
            <atom:updated>2019-02-15T13:38:26.497Z</atom:updated>
            <content:encoded><![CDATA[<p>What’s the big deal about naming? And why should we even care about it? It’s just a name.</p><p>Naming variables, methods, classes, packages etc are often given less care than it deserves. It’s very often that we encounter names like i,j,k or meaningless names like customerServicingProfileObjectUtil. We don’t feel like it is important to take a few minutes to come up with better names for our program components. Afterall it’s just a name. If we don’t understand what it does, we can always just read the code and figure it out.</p><p>Naming can mean more than we think it does. If we are not able to come up with a good name for a component that could mean any of the following</p><ul><li>We don’t understand the responsibilities of that component</li><li>It has more than one responsibility</li></ul><p>So by coming up with a good name, we can see the problems clearly and refactor the code to better clean code. It also helps the readability of our code. If we see a method with an intent revealing name, we don’t need to dig through that method trying to figure out what it does, hence making understanding the code faster. After all, we are writing the code so as to make other humans understand it.</p><p>Another smell of bad code is when we have to use comments to describe a component instead of using its name. Instead, we can simply rename the component with a meaningful name so as to avoid the need for that comment.</p><p>Example from Robert C Marting in his Clean code book:</p><p>Instead of int d; // elapsed time in days use int elapsedTimeInDays</p><p>When we name components properly, we understand them better, we realize they may belong in different places. Basically, we refactor the code better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a43d6c0a30f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>