Presentation on Quality by Douglas Crockford.

1. Quality Douglas Crockford Yahoo! http://www.crockford.com/codecamp/quality.ppt

2. The Software Crisis The topic dominated the computer industry trade press for about a decade.

5. Craft v Engineering

6. Computer Science has not taught us how to manage software projects

9. Programming is Difficult Software is the most complicated stuff that humans make

10. Lack of metrics Measure of quality or completeness

12. Programmers are optimists They wouldn't be able to do this work if they were not

15. Programming is a social activity Solo projects are the exception

21. Leaps

29. Software does not have enough self awareness to be afraid of bugs. That's why it works as well as it does.

31. Grace Hopper's Bug

32. Snake Oil Silver Bullets

35. Incrementalism

36. Beta Perpetually unfinished

37. Winchester House

38. Winchester House

39. Winchester House

46. The simplest thing we can do to enhance the value of our codebase is to make our programs readable.

49. Good architecture is necessary to give programs enough structure to be able to grow large without collapsing into a puddle of confusion

50. Changing a correct program into another correct program.

51. Cruft Software Scar Tissue

53. Bloat Software Obesity

54. Insecurity Marginal security

55. Good secure programming is good programming.

56. As cruft accumulates, complexity grows, progess slows. Eventually, the codebase itself becomes a huge source of friction

58. Plant and harvest your crops for six years, but let the land rest and lie fallow during the seventh year Exodus 23:10-11

59. Sometimes the best course is to start over

60. The Pain of the Crash Loss of a week's work, a day's work, an hour's work, is unbearable.

61. The illusion of completion "It's in the can."

62. An experienced team can cross that ground again very quickly. Focus must be on simplicity to avoid the second system effect.