Timeline for How to reduce the number of bugs when coding?
Current License: CC BY-SA 2.5
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 21, 2013 at 2:27 | comment | added | Vector | @MetalMikester: Unit tests are good. But with high level languages and good libraries, most of the hard bugs require integration and regression testing to nail. | |
| Apr 2, 2013 at 3:15 | history | made wiki | Post Made Community Wiki by DonJoe | ||
| Sep 28, 2010 at 18:08 | comment | added | Frank Shearar | And if you're so sure that condition X will never happen... use an assert to make sure that when condition X happens, you'll know about it (through an exception, or logging, or whatever). | |
| Sep 28, 2010 at 17:20 | history | answered | MetalMikester | CC BY-SA 2.5 |