Better code practices, readability.

One feature of a good code practice is its readability.

Two men coding.
Two men coding.
Photo by Alvaro Reyes on Unsplash.
  • Keep a consistent naming scheme.
  • Make comments but don’t overuse them.
  1. Camel case: The first letter of the first word in the identifier is lower case, while the first letter of every subsequent word is uppercase. ‘lentghOfTable’.
  2. Underscores: That is the use of underscore between each word. ‘length_of_table’.
Naming scheme of a programmer.
Naming scheme of a programmer.
Photo by Christopher Robin Ebbinghaus on Unsplash

When you see commented-out code, delete it! — Robert. C. Martini.

There are many more(Part will come). So the bottom line is comment codes which will not be obvious to another programmer also comments can also indicate why you chose a certain approach over the normal one. Also one mistake sometimes we all make is commenting out the unused code, Robert. C. Martini wrote in his book Clean Code: A Handbook of Agile Software Craftsmanship “when you see commented-out code, delete it!”, this helps in making our code clarified and uncluttered. Code commenting is good, it gives us a clear understanding of the code we write but we must not go overboard.

18yrs old self-taught game developer — Highly interested in tech and software engineering I blog about these here on Medium — YouTube channel —

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store