Secure Coding mailing list archives

Bugs and flaws

From: wietse at porcupine.org (Wietse Venema)
Date: Fri, 3 Feb 2006 09:39:37 -0500 (EST)

Gary McGraw:

I'm sorry, but it is just not possible to find design flaws by
staring at code.


My experience is otherwise. Without detailed documentation I can
usually see where in the life cycle the mistake was made: analysis
(e.g., solving the wrong problem), design (e.g., using an inappropriate
solution) or coding.

        Wietse

Current thread:

Bugs and flaws, (continued)
- - - Bugs and flaws Blue Boar (Feb 02)
    - Bugs and flaws Al Eridani (Feb 03)
  - Bugs and flaws Gunnar Peterson (Feb 02)
- Bugs and flaws Gary McGraw (Feb 02)
  - Bugs and flaws Kenneth R. van Wyk (Feb 03)
- Bugs and flaws Gavin, Michael (Feb 02)
- Bugs and flaws Gary McGraw (Feb 02)
  - Bugs and flaws Jeff Williams (Feb 02)
  - Bugs and flaws John Steven (Feb 02)
  - Bugs and flaws der Mouse (Feb 02)
  - Bugs and flaws Wietse Venema (Feb 03)
    - Bugs and flaws Greg Beeley (Feb 03)
- Bugs and flaws Brian Chess (Feb 02)
- Bugs and flaws Gary McGraw (Feb 02)
  - Bugs and flaws Jeff Williams (Feb 02)
- Bugs and flaws Gary McGraw (Feb 03)
  - Bugs and flaws James Stibbards (Feb 03)
  - Bugs and flaws Crispin Cowan (Feb 03)
    - Bugs and flaws Dana Epp (Feb 03)
    - Bugs and flaws Crispin Cowan (Feb 07)
- Bugs and flaws Nick FitzGerald (Feb 03)

(Thread continues...)