<?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 Hendrik Beck on Medium]]></title>
        <description><![CDATA[Stories by Hendrik Beck on Medium]]></description>
        <link>https://medium.com/@hendrikbeck?source=rss-ab0c1941ad9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*AS4HseT8SGLMzV_O.gif</url>
            <title>Stories by Hendrik Beck on Medium</title>
            <link>https://medium.com/@hendrikbeck?source=rss-ab0c1941ad9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:14:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hendrikbeck/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[My 5 reasons not to use short variable names anymore]]></title>
            <link>https://medium.com/@hendrikbeck/my-5-reasons-not-to-use-short-variable-names-anymore-89a7b32aad34?source=rss-ab0c1941ad9------2</link>
            <guid isPermaLink="false">https://medium.com/p/89a7b32aad34</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Hendrik Beck]]></dc:creator>
            <pubDate>Thu, 18 Jun 2015 20:25:09 GMT</pubDate>
            <atom:updated>2015-06-18T20:25:09.771Z</atom:updated>
            <content:encoded><![CDATA[<p>An appeal to better variable naming from many years ago, re-interpreted as a metaphor for quality work.</p><p><em>I originally wrote this </em><a href="http://blog.hendrikbeck.com/2010/08/03/my-5-reasons-not-to-use-short-variable-names-anymore/"><em>back in 2010 on my blog over here</em></a><em>, after having been frustrated over this just too many times in one day. Now that I wanted to give Medium a shot I thought this would be a nice one to pick up and re-publish it here. I modified it a bit. I was surprised though how true it still is. Not because people are still using bad variable names (I think they do, don’t they?) but because it feels more like a metaphor by now. For almost every aspect in software engineering. Sense and quality and thoroughness and attention to detail do pay off. Over time but probably sooner than expected.</em></p><p>Every other day I stumble upon lines of code like this:</p><blockquote>sysMgrH = vFgrMan</blockquote><p>or this:</p><blockquote>parse1(l, e, arr);<br>parse2(l2, e2, arr);</blockquote><p>Please don’t do that anymore! Choose long and clear variable names, nothing else! Why?</p><ol><li>It’s actually allowed to have variable names longer than 1, even longer than 10 characters, if you need that.</li><li>Your job is not about saving a couple of keystrokes or 30 seconds of time, it’s about producing something of high quality. And something maintainable. And sustainable.</li><li>Actually writing down the code in your editor is only a tiny fraction of your time compared to the rest, like, uhm, thinking about what code you should write. You can as well spend a few seconds more on the writing part.</li><li>If you worry about having to write the same 12-characters variable name over and over again: make friends with Ctrl+Space.</li><li>But the actual reason, my personal #1 reason, is the following: you don’t write that piece of code for yourself and for right now. It will be existing for the next 5 or 10 years and if you’re lucky dozens of developers will see it. And some of them have to understand it. In 2 months, in a year, in 5 years. For them it won’t be a matter of 30 seconds (that’s the time you saved 5 years ago, remember?), for them it can easily become a matter of hours and days. On average more than 50% of software development costs are spent after the initial version is finished.</li></ol><p>So here is my appeal: be nice and write your code as if you’d write a novel. Choose nice words, choose long words, and format everything nicely. Think of your fellow developer in the future who will thank you for that. And who might just be <a href="https://groups.google.com/forum/#!msg/comp.lang.c++/rYCO5yn4lXw/oITtSkZOtoUJ">“a violent psychopath who knows where you live”</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89a7b32aad34" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>