OK - that whole talk about making software more understandable instead of churning new features - sounds good. But his rejection of reliance on trust looks like

OK - that whole talk about making software more understandable instead of churning new features - sounds good. But his rejection of reliance on trust looks like a pipe dream. What is he proposing in concrete terms? How one should decide that his code is understandable enough? What to do with the recursiveness of libraries that use other libs that use libs ...? The only concrete advice he proposes is the two weeks idea: """ is it possible for a new (but experienced) developer to understand 80% of the part of the codebase they’ll be responsible for within their first 2 weeks (80 hours)? If not, this person is overworked from day 1, """ But is this practical? All code should be understandable in two weeks?