On Tue, 2002-12-03 at 13:05, Ben Collins-Sussman wrote:
> I understand that many people want to work alone -- or don't want to
> be drowning in feedback before they even have working code.

My main concern is having to stop and write detailed log messages every
time I want to change the infrastructure code a little bit. You don't
know what you want your low-level routines to do until you've written a
bunch of higher-level routines, so there were a lot of such moments in
ra_svn.

And I'm just not sure how much value there is in seeing all the
intermediate steps before a new module of moderate size is implemented.
Commits tend to be unreviewable due to the amount of refactoring
involved, and even when review is possible, the feedback is usually of
limited value. Collaboration isn't generally possible because of the
level of churn and unwritten design details. It's true that people
might have noticed the non-apr sockets code earlier, but that only took
two hours to fix after the power plant.

(I did plan to present a design document for fs_fs before writing any
code and take feedback, because there is a lot more important design
involved there. ra_svn did involve designing a protocol, but most of
the decisions were arbitrary or were previously aired on the list.)