Content deleted Content added
Added context for programming examples in "Keep the Code Simple". Revised language/links. |
→top: Replacing inaccessible book link with a citation that includes an OCLC that links to a Worldcat record that lists ebooks. They may be behind a paywall, but I think this is better. Removed comment. Please do not insert comments into the Wikitext that would be better placed on the talk page. |
||
Line 4:
}}
'''Coding best practices''' or '''programming best practices''' are a set of informal rules (''[[best practice]]s'') that many [[software developer]]s in [[computer programming]] follow to improve [[software quality]].<ref name="McConnell 2004 p. ">{{cite book |
In the [[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."<ref name="Bentley1985">{{cite journal|last=Bentley|first=Jon|year=1985|title=Programming pearls: Bumper-Sticker Computer Science|journal=Communications of the ACM|volume=28|issue=9|pages=896–901|issn=0001-0782|doi=10.1145/4284.315122|s2cid=5832776|doi-access=free}}</ref> Any guidance which can redress this lack of foresight is worth considering.
| |||