Coding best practices: Difference between revisions

Revision as of 13:33, 18 December 2008

Revision as of 15:58, 8 May 2009

Line 31:

Building the code is really just a small part of the total project effort even though it's what most people equate with the whole process since it's the most visible. Other pieces equally or even more important include what we have already gone over above namely [[requirements]], architecture, analysis, design, and [[Software testing|testing]]. A best practice for building code involves daily builds and testing.

Best coding evolves from following proper coding standards and guidelines. Appropriate Comments for each and every line of code makes code maintainability much more easier. A best code should have reusable components.

== Peer review==

It's OK, really! Look at other people's work. Learn from it. If you have a problem, chances are someone else has already had and resolved the same problem. Don't be afraid to ask questions. You can return the favor by letting others see your code and learn from it.

== Testing ==