2 ms·
I would be wary of extrapolating what the author is writing of here to general software projects. I think it makes a lot of sense on large open source projects,
by liampulles 3y ago
I would be wary of extrapolating what the author is writing of here to general software projects. I think it makes a lot of sense on large open source projects, where there are many contributors with little context- it is worth the effort to maintain such a document in this case. But all the developer committed documentation I've seen on smaller work projects have inevitably become unmaintained.
- berkes 3y agoI've done a few Architecture sessions with teams. It's always valuable. If anything, you'll learn that people in the team have very different ideas about the current and the ideal architecture. Making that explicit, alone, is worth a document. And also: "documentation become unmaintained" is a very poor argument to not make documentation. Because any documentation, even outdated or subtly wrong one, is better than "no documentation".