News for hackers. Stuff that matters.
Re:Readme-Driven Development (2010) by wck0 on Friday June 29, 2018 @06:29PM (#17428337)
I forget where I saw this, but it struck me as very good advice: Don't document your code, code your documentation.
Re:Readme-Driven Development (2010) by cbcoutinho on Friday June 29, 2018 @06:57PM (#17428480)
Sounds like literate programming, popularized by Donald Knuth
Re:Readme-Driven Development (2010) by iamdave on Friday June 29, 2018 @06:40PM (#17428387)
I like that.

So many times I've looked at a peer's code and had a hard time reconciling what the comments and wiki articles said with what their code was attempting to do.

This mindset is probably a godsend to QA teams.

Re:Readme-Driven Development (2010) by madhadron on Friday June 29, 2018 @11:02PM (#17429270)
My father was convinced that Quark XPress was written that way: once they had the core functionality figured out, they wrote the manual, then implemented it.
Re:Readme-Driven Development (2010) by bitL on Saturday June 30, 2018 @09:15AM (#17430769)
The thing is - this is interesting because nobody is doing it anymore. Once everybody starts doing it, i.e. literally "human politics" gets directly involved on all levels of development, everybody would try to escape this style to get some development freedom for themselves to stay sane.