2010-10-29, 04:07 PM
Something you'll learn down the road is that maintainable code is worth far, far more than fast code. Eventually down the line someone else is going to look at your code. It might even end up on TDwtp (lol - the daily wt'f - just google it). Fast code is only necessary when one needs bal'ls to the walls speed, and for many applications it's simply not necessary.
The best code is "at-a-glance" code where you can just skim it and have a fairly good idea of exactly what each method or function will do.
Good coding practices state that about 15 - 20% of your code should be developer comments. More complicated parts of the code should be documented heavier. Comments should not restate the code, but state why that method of code was used instead of another, or explain the purpose of the code at hand.
The best code is "at-a-glance" code where you can just skim it and have a fairly good idea of exactly what each method or function will do.
Good coding practices state that about 15 - 20% of your code should be developer comments. More complicated parts of the code should be documented heavier. Comments should not restate the code, but state why that method of code was used instead of another, or explain the purpose of the code at hand.