As developers, we’re always asked to write more documentation. Some of us even do it without being asked. But look around the web and you’ll see countless gems, applications and source code examples whose documentation is either missing or makes no sense. How can we make little changes to the way we think about documentation to make things better?
YOU MAY ALSO LIKE:
You’re doing documentation wrong (and so am I)
Scott Matthewman is a senior developer at TRX, working with Rails projects dating from brand new code to repos that had their genesis in Rails 3.2 days.