Coding Efficiency - Printable Version +- QB64 Phoenix Edition (https://qb64phoenix.com/forum) +-- Forum: Chatting and Socializing (https://qb64phoenix.com/forum/forumdisplay.php?fid=11) +--- Forum: General Discussion (https://qb64phoenix.com/forum/forumdisplay.php?fid=2) +--- Thread: Coding Efficiency (/showthread.php?tid=2924) |
RE: Coding Efficiency - dano - 09-12-2024 Clarity is KING. Proper named variables are also a huge help as well as organized variable naming conventions. For example, if my variable is a local only variable, it will begin with lowercase 't' (meaning temp) - this way I know at a glance that it is local only. RE: Coding Efficiency - Jack - 09-12-2024 I agree with dano on clarity, some people are very clever but only they can understand their code RE: Coding Efficiency - Kernelpanic - 09-12-2024 Using sensible variable names is "ancient", but it was often overlooked. You could read about it already in every good programming book over 30 years ago, especially in the standard programming work: Code Complete from 1993. And there is something else that you can find/found not only there, the use of brackets in C, Java & Co. Code: (Select All)
Even back then, in 1993(!), it was pointed out that this type of bracketing have costed hundreds of thousands of man-hours in troubleshooting. But it is ineradicable! People still use brackets like this. --> Now about . . . 100 million man-hours? Or could it be a bit more? RE: Coding Efficiency - Pete - 09-13-2024 Not to mention tax brackets. Although the difference here is the higher you go, the more time money you lose. Pete - I coded with bell-bottoms in the 1970's. |