You know how teachers used to say, “You can’t cheat your way through life, so don’t cheat on this test.” They may have been right about the test...but not life.
Researchers at Microsoft and University of Cambridge have developed an Artificial Intelligence that’ll write code all by itself.
Many developers many coding styles so it is important to set a naming convention on each project where you work in a team. There isn't wrong convention but there are many ways you can approach so agree on a pattern in order to make the code intuitive.
Here is an example to take away and modify by your preferences.
Always stick to theses essentials:
Understand the problem before you fix it .
Check for common defects.
Refine the test cases that produce the error.
Narrow the suspicious region of the code. / Expand the suspicious region of the code.
Be suspicious of classes and routines that have had defects before.
Check code that’s changed recently.
Set a maximum time for quick and dirty debugging => rewrite the code .
Change the code only for good reason AND Make one change at a time.
Never debug standing up :)