The author seems to conflate several different types of documentation, like requirements, code comments, and api explanations. Additionally TDD isn’t intended t

The author seems to conflate several different types of documentation, like requirements, code comments, and api explanations. Additionally TDD isn’t intended to work in the absence of any documentation, the concept is that a test models the requirements. Maybe a paradigm to consider more is: Literate programming (LP) tools are used to obtain two representations from a source file: one understandable by a compiler or interpreter, the "tangled" code, and another for viewing as formatted documentation, which is said to be "woven" from the literate source. https://en.wikipedia.org/wiki/Literate_programming https://en.wikipedia.org/wiki/Literate_programming