These are the best 7 tips to write clean code in 2018

4 min readMay 16, 2018

Let’s spend some time in learning how to become a better programmer by keeping your code clean, easily readable and well worth. Here are 7 tips to write clean code in 2018

Conventions

Naming convention basically means that you are going to call your variables by name that adhere to a certain set of rules. There are preset rules that people could go into but it can get hairy and most of the people don’t agree on which is the best

Related Reads:
Let’s Learn ANDROID
Some basic tips for JavaScript Beginners

360 No Scope

There aren’t any rules defined and every coder can have his own way of doing it as long as these are consistent throughout the code. It will make it simple for what can be used from where.

Say What You Mean

The most frustrating thing that a developer faces looking at your code, is seeing a variable with a misleading name, or worse, named with a single letter.

Let’s take a look at how we can clean it up:

More Reads:
Multitasking increases Productivity, you say? Think Again!
More work doesn’t equal more success
10 Mantras For A Successful E-commerce Store

Whitespace Is a Nice Space

The whitespace can add a few extra kilobytes. But there are tools that can minify your files at the time of deployment. If you are writing many things together in a single block, then try grouping the lines of code into some logical pieces.

Commenting Saves Lives — or At Least Headaches

Comments can be used to explain why certain things are required to happen in a certain order. However, too much commenting can have negative effects and can also result in sloppy code.

Automating After 3 Times

The lines of duplicate codes are not only harder to read than a concise and elegant solution, but also helps in increasing the chance for an error.

And here’s an approach that cleans everything up:

The Power of i

When you have a code block with multiple loops one after the other; you would need different iterator variables. Declaring your iterator outside of the loop and reuse it would be the best choice.

The longer function definitions are quite an easy way of cluttering your code. Generally, it’s always best for taking a look at what actually is being done. If in any case, the function is doing more than what its name suggests; probably the excessive functionality is likely to split out into its own functions.