<?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 Arjav Garg on Medium]]></title>
        <description><![CDATA[Stories by Arjav Garg on Medium]]></description>
        <link>https://medium.com/@arjavgarg?source=rss-dcc72478466a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*2CAqCnsp909a5Qs_</url>
            <title>Stories by Arjav Garg on Medium</title>
            <link>https://medium.com/@arjavgarg?source=rss-dcc72478466a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:55:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arjavgarg/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[Naming Stuff in Software Engineering]]></title>
            <link>https://medium.com/@arjavgarg/naming-stuff-in-software-engineering-efb17c8470bf?source=rss-dcc72478466a------2</link>
            <guid isPermaLink="false">https://medium.com/p/efb17c8470bf</guid>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Arjav Garg]]></dc:creator>
            <pubDate>Fri, 05 Dec 2025 17:24:09 GMT</pubDate>
            <atom:updated>2025-12-05T17:25:31.339Z</atom:updated>
            <content:encoded><![CDATA[<p><em>“There are only two hard things in Computer Science: cache invalidation and </em><strong><em>naming things</em></strong><em>”</em></p><p>It might sound like an exaggeration but naming things in your code or database schema really does matter.</p><ul><li>It reads easier so you can focus on the actual problem at hand.</li><li>Misconceptions are dispelled which not only leads to better understanding, but fewer bugs as well.</li><li>AI will make lesser mistakes if your code tells its story to it in a succinct way.</li></ul><p>Writing software isn’t really about knowing how to talk to the machine on which your code runs — we have known that for decades. It takes only a precise language as its input and does everything to the letter.</p><p>No, writing software is about communication. Communication with other humans (or AIs) who happen to read your code. Hence, improving your naming skills will improve your (technical) communication skills as well, the benefits of which I’m sure I don’t need to list.</p><p>So, to improve our naming skills, we need to think of it as a communication exercise. When you write a variable, database field or function’s name, think about how it would read to someone who has not worked on this codebase in the last week or so. That <em>someone</em> can be you as well, just a month or two weeks later!</p><h3>Variables &amp; Fields</h3><ul><li>When naming your variables, think about what makes them different from other similar variables. For example, if you have two lists, don’t name them items1 and closedItems because this doesn’t give any clarity about whether items1 contains all items, or just open, non-closed items. “But if you just read the code…” stop. If I have to go through the control flow to get a basic understanding of what your variables are storing, you are not naming them properly.</li><li>Do not name your variables or database fields after the noun form of a verb, like validation. The only time you should do this is when your variable is holding a Promise or a Task so that you can write your code like await dataValidation which reads perfectly well.</li><li>Finally, obviously, do not name your variables or database fields gibberish like a or b. This could be done for extremely short-lived variables (not more than 3 lines), but still, please avoid this.</li></ul><p>PS: <em>This is a work in progress.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efb17c8470bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>