From 9812d92c09050966bae38dd49027ae46e1444e58 Mon Sep 17 00:00:00 2001 From: Tom Preston-Werner Date: Mon, 23 Aug 2010 09:52:20 -0700 Subject: [PATCH] Add HN link. --- _posts/2010-08-23-readme-driven-development.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/_posts/2010-08-23-readme-driven-development.md b/_posts/2010-08-23-readme-driven-development.md index 1b7eddc3..70219253 100644 --- a/_posts/2010-08-23-readme-driven-development.md +++ b/_posts/2010-08-23-readme-driven-development.md @@ -30,4 +30,8 @@ By writing your Readme first you give yourself some pretty significant advantage * It's a lot simpler to have a discussion based on something written down. It's easy to talk endlessly and in circles about a problem if nothing is ever put to text. The simple act of writing down a proposed solution means everyone has a concrete idea that can be argued about and iterated upon. -Consider the process of writing the Readme for your project as the true act of creation. This is where all your brilliant ideas should be expressed. This document should stand on its own as a testament to your creativity and expressiveness. The Readme should be the single most important document in your codebase; writing it first is the proper thing to do. \ No newline at end of file +Consider the process of writing the Readme for your project as the true act of creation. This is where all your brilliant ideas should be expressed. This document should stand on its own as a testament to your creativity and expressiveness. The Readme should be the single most important document in your codebase; writing it first is the proper thing to do. + +-- + +[Discuss this post on Hacker News](http://news.ycombinator.com/item?id=1627246) \ No newline at end of file