Part of the problem with documentation is is decoupling from code. Therefore, when code changes, the documentation might tell a different story. Documentation

Part of the problem with documentation is is decoupling from code. Therefore, when code changes, the documentation might tell a different story. Documentation-as-code (i.e. doctests in Rust or Go) alleviates some of the shortcomings by showing how to use an API correctly. The beauty of Docs-as-Code is that parts of it can even be generated. I'm thinking Diagrams-as-Code where the system under test can be i.e. queried for capabilities.