Design & Engineering

Naming is an essential but grossly underrated skill. Every programmer faces the problem of finding good names on a daily basis. Yet, few programming textbooks and university courses discuss the topic beyond a few syntactic do’s and don’ts. Vague rules such as “identifiers should be self-describing” are not explained and are hard to follow, especially for novices. Ironically, studies show that beginners are especially reliant on good names, as more experienced developers are better at reading contextual cues. While developers agree that naming matters, they adhere to different conventions and disagree on critical aspects such as acceptable names lengths. Very few use written guidelines or consult empirical evidence.

In this article you’ll find theory behind finding good names for programming purposes and a set of practical guidelines that will help you improve your craft. Dive in to discover what the name of your next variable, class or method should be.

You probably keep your personal message centre by your side most of the time. Being the first to know about new offers, best deals and order status is at your fingertips. News floods you via SMS, emails and notifications – you don’t need to hunt them anymore. However, you have a specific stock of attention at your disposal, and sadly – limited power over this resource.

The responsibility for taking a comprehensive, sustainable approach towards technology and placing the good of humanity in the centre of interest lies upon each of us. 

Creating websites requires a great amount of organisation in order to simplify any further changes while maintaining consistency. Even though this task seems daunting at first sight, it can be supported by a methodology like Atomic Design – which compares created components to atoms, molecules and organisms.