Siteadmin, Check users, nsTeam1RO, nsTeam1RW, nsTeam1_talkRO, nsTeam1_talkRW, oversight, Administrators
30,650
edits
Changes
Jump to navigation
Jump to search
Line 6:
Line 6: + + + +
It is hard to write even the smallest piece of code correctly, and our whole world runs on big, complex pieces of code.
* Some [[computer programmer]]s distinguish between [[coding error]]s and [[design flaw]]s, often using the half-joking justification, "That's not a bug. It's a [[feature]]!"
* Some [[computer programmer]]s distinguish between [[coding error]]s and [[design flaw]]s, often using the half-joking justification, "That's not a bug. It's a [[feature]]!"
* Often the distinction between a coding error, a design flaw and a feature request is disregarded. Indeed, [[Sun Microsystems]] maintains a [http://bugs.sun.com/ bug parade] for their [[Java]] platform which lets everyone in the world vote for a bug fix or feature request.
* Often the distinction between a coding error, a design flaw and a feature request is disregarded. Indeed, [[Sun Microsystems]] maintains a [http://bugs.sun.com/ bug parade] for their [[Java]] platform which lets everyone in the world vote for a bug fix or feature request.
Speaking of one particularly embarrassing software bug, [[Java]] guru [[Joshua Bloch]] wrote:
* The general lesson that I take away from this bug is humility: It is hard to write even the smallest piece of code correctly, and our whole world runs on big, complex pieces of code. We programmers need all the help we can get, and we should never assume otherwise. Careful design is great. Testing is great. Formal methods are great. Code reviews are great. Static analysis is great. But none of these things alone are sufficient to eliminate bugs: They will always be with us. A bug can exist for half a century despite our best efforts to exterminate it. We must program carefully, defensively, and remain ever vigilant. [http://googleresearch.blogspot.com/2006/06/extra-extra-read-all-about-it-nearly.html]
==External links==
==External links==