You want to turn my 300 lines of clear, readable and concise logic into 1,000 lines of English paragraphs that break up the functions of my code into yet smaller pieces of code devoid of context? Now I have to dig through that book, ignoring all the shit I've read hundreds of times because it doesn't compile into anything, just to debug an off-by-1 error in a loop buried in a paragraph explaining the original developers diatribe on why we're looping over that range? Fuck. No.

This is the sort of academic crap that sounds good but in practice is just terrible for anything other than small projects that are intended specifically to teach.

Not GP, but reading gnarly code and making definitive statements about who/what/when/where/why such that your documentation is accurate, especially in a corpo context where there are not clear boundaries of responsibility, requires quite a bit of brain power. Not to mention the ever increasing entropy in systems driven by profit means that whatever you write in terms of documentation will have a pretty short shelf-life. The code might stick around as an unholy amalgamation of copypasta after a refactor or two.