ْْْْْْْْْْْْْْْْْْْْْْْْْْ retweetledi

the problem with "spec driven development" is that most software can't be spec'd up front
software is a creative act, where you figure out what you're building as you build it
you need to get your hands dirty in the details, and react to incremental versions
it's telling that all the examples of spec driven development are sorting a list or porting thoroughly tested code (like a js runtime or browser engine), which are the exception, not the rule. the vast majority of software doesn't have a spec – or if it does, the spec was created *after*
English













