News for hackers. Stuff that matters.

A comment on Readme Driven Development. Parent comment

Re:Readme Driven Development by raggi on Monday August 23, 2010 @03:43PM (#1627778)
no. blogs are not a substitute for documentation.

ruby has been suffering this for too long.

blogs have several problems:

- they don't get updated - they don't get patched - they don't ship with the software - they break when the user dies / moves / leaves / changes software - they have a lower signal to noise ratio

[ Parent | on HN ]
Re:Readme Driven Development by steveklabnik on Monday August 23, 2010 @05:25PM (#1628109)
- they accumulate Google juice over time, overpowering advice for newer versions of your framework.
[ Parent | on HN ]
Re:Readme Driven Development by silentbicycle on Monday August 23, 2010 @06:57PM (#1628340)
Or even worse, when half the documentation is a screencast.
[ Parent | on HN ]
Re:Readme Driven Development by integraleq on Sunday September 12, 2010 @11:09PM (#1685352)
You are correct. So I suppose I should alter my previous post by saying that it is a good way to go iff you are also willing to be diligent in your updates to keep the documentation as current as possible.
[ Parent | on HN ]