 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
Coding best practices or programming best practices are a set of informal, sometimes personal, rules (best practices) that many software developers, in computer programming follow to improve software quality.[1] Many computer programs require being robust and reliable for long periods of time,[2] so any rules need to facilitate both initial development and subsequent maintenance of source code by people other than the original authors.
In the ninety–ninety rule, Tom Cargill explains why programming projects often run late: "The first 90% of the code takes the first 90% of the development time. The last 10% takes another 90% of the time."[3] Any guidance which can redress this lack of foresight is worth considering.
The size of a project or program has a significant effect on error rates, programmer productivity, and the amount of management needed.[4]
- ^ McConnell, Steve (2004). Code Complete. Redmond, Wash.: Microsoft Press. p. [page needed]. ISBN 978-0-7356-9125-4. OCLC 61315783.
- ^ Sommerville, Ian (2004). Software Engineering (Seventh ed.). Pearson. p. 38. ISBN 0-321-21026-3.
- ^ Bentley, Jon (1985). "Programming pearls: Bumper-Sticker Computer Science". Communications of the ACM. 28 (9): 896–901. doi:10.1145/4284.315122. ISSN 0001-0782. S2CID 5832776.
- ^ McConnell, Steve (2004). Code Complete (Second ed.). Microsoft Press. pp. 649–659. ISBN 0-7356-1967-0.