4 ms·
I feel that every codebase built by one person is understand by that person really well and nobody else gets to the same level of understanding, unless the code
by samsquire 3y ago
I feel that every codebase built by one person is understand by that person really well and nobody else gets to the same level of understanding, unless the codebase is embedded, it shall only exist as long as the original person is around.
- baby 3y agoI want to see a whole discussion based on that comment. This is a real and big issue, and the big reason why it’s hard to scale the team.
- samsquire 3y agoI don't believe code _is_ the documentation. I've thought of information systems for code, I once used OpenGrok to parse a large codebase and try work out how it works. But it's undirected learning. I think question answering would be useful: "Where should I change the code to insert behaviour that changes X, Y, Z behaviours"
- chii 3y ago> This is a real and big issue, and the big reason why it’s hard to scale the team. it's also why java as a language is good, not because the language is good, but that it's easy to have someone not originally involved in adding/maintaining the code base - you can't get too clever with java.
- baby 3y agoI would have said the same with Golang, Java though… not sure I understand considering all the crazy patterns that exist there and the huge mess codebases are due to how namespacing work and other reasons.
- kaba0 3y agoSee Naur’s Programming as Theory Building.