"Code is the documentation" has to have boundaries though, or else you'd have to understand the entire system down to the instruction set in order to print hell

"Code is the documentation" has to have boundaries though, or else you'd have to understand the entire system down to the instruction set in order to print hello world. Within a small/medium codebase, code is documentation is mostly okay, but for libraries and abstractions you really ought to have solid API docs.