Code: Quantity vs. Quality

Coding Horror on coding quantity vs. quality.

It seems that while the “quantity” group was busily churning out piles of work – and learning from their mistakes – the “quality” group had sat theorizing about perfection, and in the end had little more to show for their efforts than grandiose theories. […]

  • Stop theorizing.
  • Write lots of software.
  • Learn from your mistakes.

From this you can plainly see that the rise of iterative/agile development methodologies is a natural evolution; improvements only come from practice and learning from your mistakes.

It puts me in mind of something my company’s IT Director recently said: “If you got past the interview stage, you’ll never make a stupid mistake in this office. You’ll make mistakes—granted—but you’ll learn from them, and grow stronger.”



One response to “Code: Quantity vs. Quality”

  1. Interesting post. I think this principle is applicable to so many things: public speaking, sport etc.
    If you like Jeff Atwood you might be interested in his joint podcast with Joel Spolskey about their new programming forum: stackoverflow: