Spolsky on Writing Specs

The Pragmatic Craftsman :: Simplicity from complexity ::

August 18th, 2005 | In Quotes | Comments Off

The reason you write a spec is not to solve every possible problem in advance: the reason you write a spec is to solve as many problems as you possibly can in advance so that you minimize the number of surprises that come up during development.

–Joel Spolsky
- talking about Copilot.com spec

Reference:Blog entry about The Project Aardvark Spec by Joel Spolsky

Related:The original spec (pdf) by Joel Spolsky

Comments are closed.

Currently Reading

@PragCraftsman on Twitter

New on my blog: @PragCraftsman Twitter Weekly Updates for 2010-03-14 http://bit.ly/8ZfjXd -Pragmatic Craftsman - 16 hours agoSOLID principles come in handy here. Especially, "Open of Extension, Closed for Modification." One of the best principles I've learned. - 1 day agoI actually try to follow @unclebobmartin's rule all the time. Sort of. I try not to make it worse. But to make it better? Great challenge! - 1 day agoAlways check a module in cleaner than when you checked it out (via @unclebobmartin in 97 Things Every Progr.). I love the idea! - 1 day agoI put Code Complete #1 over Martin's book because it has "awaken" me as a programmer. But other than that, Martin's book is the best! - 2 days ago

The Pragmatic Craftsman :: Simplicity from complexity ::