This is a title I’m giving to some failings in the history of literate programming. Great software was created in a literate style only for all the literate elements to be stripped out by programmers preferring the concise efficiency of straight code. The theory eat itself.
The motivation behind this auto-canibalisation of the paradigm is clear to anyone who has coded for any time - it is very time consuming to document what you are doing. In fact it takes considerably longer to write about what you are coding that’s it does to code it. If you are a coder and not a writer, writing about your code is not simply inconvenient it is physically painful. It is a rare coder who enjoys documenting there work.
# Empathy
Given an understanding of the problem, we can see how we might step sideways and solve it - at least for specific cases. The evolution is to accept that coders won’t write, and to focus on writers. We need to make the experience motivating for writers. That way the coders can be motivated to join in - even if this is the same person.
These elements are: - Unearthing energy - Autopoetic integration - Content = Code
Or if we were to say the same thing in words, itch scratching in diverse communities is possible, but requires building feedback systems between varied incentives.