When one thinks of coding standards, the usual reaction is annoyance. However, for computer science students, coding standards should be viewed as a way to write better code. Coding standards not only improve the quality of your code for yourself, but for others that may be reading your code. According to the website geeksforgeeks.org,
- A coding standard gives a uniform appearance to the codes written by different engineers.
- It improves readability, and maintainability of the code and it reduces complexity also.
- It helps in code reuse and helps to detect error easily.
It promotes sound programming practices and increases efficiency of the programmers.
(geekforgeeks.org)
And this could not be more true. It makes just as much sense as to follow the syntax/grammatical structures of speaking languages. If they are not followed, they can not be understood and thus the sentence is not effectively communicated. Coding standards allow for us to do so for languages in the world of programming, and eventually you learn to code in compliance with the coding standards.
I don’t know about other students, but I love coding with ESLint and intelliJ. I tend to overlook a lot of small errors that would have taken me hours to find without something to look for it. ESLint not only shows the errors right where they are and right away, but if they are simple enough, you can have it be automatically corrected by the click of a few buttons. Gone are the days of searching through code for hours and hours on end, not knowing what you did wrong or what semicolon or curly bracket you’ve missed. For me, the green checkmarks that signify that my code follows the coding standards provides me a level of satisfaction that makes me think I at least did something right.