Hacker News Reader

Serious question: What does TDD, BDD, Extreme Programming, SCRUM, Standups and all the stuff in the first paragraph have to do with writing a library or app with proper documentation?

I'm completely lost as to how doing Extreme Programming means you don't have a good Readme for your Git-Powered wiki with sweet API?

View on HN

All of those things are approaches to crafting better software. It is my observation that a lot of projects developed with these methodologies still lack proper documentation. And I see documentation, especially in the form of a good Readme, as critical to the design, usability, and longevity of a project.

Do you consider projects like http://erector.rubyforge.org/, http://pivotal.github.com/jasmine/user-guide.html, or http://github.com/pivotal/cedar to have good documentation?

Sure. The documentation for those projects looks great!

Not necessarily anything -- it's only when Agile practitioners take "your documentation is your code" a bit too literally.

Reply on news.ycombinator.com