Yeah, I should elaborate. Well-written documentation can be great for collaboration. But well-written documentation can be really hard to do, even when the incentives are perfectly aligned (very rare even in open source; the world is complex). So lately I try to at least talk about the thing right in front of the thing rather than on some other page all by itself. That way at least if I screw up how I describe the thing, at least the reader has a chance at trying to cross-triangulate what I mean by looking at and running the thing itself. But you're a Smalltalk guy. I suspect I'm preaching to the choir 🙂

Interesting. Are there other ways than documentation that foster collaboration? Something less tiresome to maintain.