4 ms·
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 do
by raggi 16y ago
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
- steveklabnik 16y ago- they accumulate Google juice over time, overpowering advice for newer versions of your framework.
- silentbicycle 16y agoOr even worse, when half the documentation is a screencast.
- integraleq 16y agoYou 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.