Coding best practices: Difference between revisions

Revision as of 06:43, 9 October 2022

Revision as of 21:15, 12 October 2022

Line 4:

}}

'''Coding [[best practice]]spractices''' or '''programming best practices''' are a set of informal rules that(''[[best thepractice]]s'') that [[software developmentdeveloper]]s communityin employs[[computer toprogramming]] helpfollow to improve [[software quality]].<ref>{{cite book

| title = Code Complete

| url = https://archive.org/details/codecomplete0000mcco

Line 14:

| publisher = Microsoft Press

| isbn = 0-7356-1967-0}}</ref>

Many computer programs remain in use for long periods of time,<ref>{{cite book

| title = Software Engineering

Line 23 ⟶ 22:

| publisher = Pearson

| isbn = 0-321-21026-3

| page = 38}}</ref> so any rules need to facilitate both initial development and subsequent maintenance and enhancement of [[source code]] by people other than the original authors.

In the [[Ninety–ninety rule|ninety-ninety rule]], Tom Cargill is credited with an explanation as to why programming projects often run late: <!-- these do add to 180%, and are meant to (=late project). See linked Ninety-ninety rule --> "The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time." Any guidance which can redress this lack of foresight is worth considering.