Content deleted Content added
Mjchonoles (talk | contribs) m disambiguated UML |
m contractor dab |
||
Line 4:
There are standards that originated from the intensive study of industry experts who analyzed how bugs were generated when code was written and correlated these bugs to specific coding practices. They took these correlations between bugs and coding practices and came up with a set of rules that when used prevented coding errors from occurring. These standard practices offer incredible value to software development organizations because they are pre-packaged automated error prevention practices; they close the feedback loop between a bug and what must be done to prevent that bug from reoccurring. There is no need to write your own rules to get the benefit of these practices - the experts have already done it for you.
In a team environment or group collaboration, best coding practices ensure the use of standards and uniform coding, reducing oversight errors and the time spent in code review. When work is outsourced to a third-party [[independent contractor|contractor]], having a set of these best practices in place gives you the knowledge that the code produced by the contractor meets all the guidelines mandated by the client company.
It should be understood that these practices are not just a way to enforce naming conventions in your code.
| |||