This is a good example of getting a drink from the firehose. A large piece of code required the writer to understand a whole heap of concepts to understand the code.
For another programmer to understand the code without those concepts is hard.
Code is really just a snapshot of ideas in progress at time. It’s one of the challenges I see with the open source movement. It’s great to get the source but if the concepts in the source aren’t broken down and made digestible you might as well be shipping an encrypted binary program. Programmers end up consuming code that is open source but don’t do so with understanding.
I think with teams is it better to encourage teams to get good at sharing concepts rather than dumping code on one another.