3 ms·
First time I've heard of Readme Driven Development, is this a thing? I always lambast myself for continually rewriting the Readme as I go. Part of me sees it a
by CraigJPerry 13y ago
First time I've heard of Readme Driven Development, is this a thing?
I always lambast myself for continually rewriting the Readme as I go. Part of me sees it as a time drain, or at the very least an admission I've not done sufficient high level strategising upfront.
I do keep doing it though!
- nsmartt 13y agohttp://tom.preston-werner.com/2010/08/23/readme-driven-development.html http://tom.preston-werner.com/2010/08/23/readme-driven-devel... It's my understanding that this is the original article.
- jacques_chester 13y agoOne of my software engineering professors told how back in the 70s when he was promoted into management, he had his teams write a user manual before starting on coding. He said it brought up all the important fuzzy-requirement problems much earlier in the process, for much lower cost. Plus, you ensured that there was a manual written. That might not happen otherwise, or it might be done in a rush because of the next project. It was a different time, but I always found it to be an interesting anecdote.