> How can having a comprehensive understanding of your infrastructure/stack be a weakness exactly? Weakness in the inverse: not being ready to change to new co

> How can having a comprehensive understanding of your infrastructure/stack be a weakness exactly? Weakness in the inverse: not being ready to change to new code, because you have a clear and distinct understanding of the old, and an uncertain take on the new. In that case, even if the new were better objectively, it would be discounted for you by uncertainty. Conversely, if you understand something complex deeply and newbies don't, to them something that's easy to understand (but defers problems your stack solves) is preferable, and you end up with culture and governance issues. Managers who are relatively ignorant then set up competitions to surface issues, validate claims, and develop alternatives to mitigate their reliance risks on employees. So: move fast and forget things, and expect a fight :)