Documentation is more like a pizza baking manual, so that if a new chef takes over, they can still make the same pizza.
back
4 comments
Recording this sort of institutional knowledge is why I find it invaluable to write my code as a Literate Program:
https://literateprogramming.com/
so that specific problems are documented.
That's good but you still need documentation of available methods and how to use them. That's it's literate just makes it that much easier to connect what you read in the documentation with the code.
SSL doesn't work with Firefox or Chrome.
One could argue that no literate programming system has had more than one user. Knuth's WEB and CWEB never really caught on.
Good point on SSL, should have used: http://literateprogramming.com/
Well, I worked up:
https://github.com/WillAdams/gcodepreview/blob/main/literati...
for my current project (and will use it going forward for any new ones) and:
https://github.com/topics/literate-programming
has 443 projects...
That's one kind of documentation. Checklists and runbooks, for instance, are recipes. Other documentation describes APIs systematically (Javadoc) while other documentation describes architecture and broad concepts.
A ... recipe?
Exactly. Its knowledge transfer from the previous to the next generations. No knowledge transfer, so sustainable progress.