About Clean Code
Clean Code is an approved procedure in coding, both in writing variables, methods, classes and error handling. Bad coding practices proved to impair projects and companies.
LeBlanc’s law stated that “late equals never”, which means rearranging bad code would not happen. This creates chaos in codes and hinders feature addition to system. Companies will have to spend plenty of time and money to support code maintenance and could end in bankruptcy. Early use of Clean Code allows companies to focus more on features addition and system updates for their development, rather than maintaining old codes.

Naming of Variables, Functions, and Classes
The name on a variable should reflect what the code does, why it is made, and how it works. Proper and unique naming show the intention of the programmer and help variable search, hence comprehensible to programmer that later develop the system. GDP Labs asserted that every function has to be small, and carry out one task only, either execute something or solve issue, not both things at once. Moreover, GDP Labs advised to avoid excessive parameter on functions. On object-oriented program, class is used to provide attribute and implement the object’s behavior. In Clean Code, programmer has to mind the order of declaration of class. GDP Labs also asserted that every class has to be small and responsible for one task only, and every method within contains high cohesion.