[paulddraper]

This conversation is simply the English-equivalent of TDD conversations.

* Conventional development = writing, then editing

* Test-driven development = writing and editing simultaneously

The preferences are endless and neither removes the most difficult part which is the conceptual architecture.

Personally, I like to splatter a whole bunch of ideas down first and then later go back and commit.

[whlr]

There are some parallels, but I don't know if the writing:editing::programming:testing analogy is very strong. I think editing is more like refactoring than anything else, but I hesitate to make parallels between code and prose in general.