This is a poorly written article by someone clearly projecting their own individual experience (or more clearly, the lack thereof) onto a giant world of profess

This is a poorly written article by someone clearly projecting their own individual experience (or more clearly, the lack thereof) onto a giant world of professional phenomena. It is trivially easy to think of a structural counterexample to their primary point, which is how experienced senior engineers can inherit production codebases without documentation or the original team that wrote it and are able to successfully operate, understand and improve the entire codebase. Is there a gradient of pain? Yes. Is it possible to inherit a codebase that is falling apart, without the resources to get the ship back on track due to organizational issues? Absolutely. However, it doesn't change the fact that every year, significant quantities of senior engineers do something that the author does not believe to be possible. This isn't to say employee churn is particularly health for software companies; it's often not. But that really varies on a case by case basis.