Interesting. We find the situation to be quite the opposite. The older and larger the system, the more expensive figuring out is. You mention a 3-6 months. Tha

Interesting. We find the situation to be quite the opposite. The older and larger the system, the more expensive figuring out is. You mention a 3-6 months. That's quite a high price. Would it be inconceivable to optimize this significantly? Stability can also be misleading. It's especially the small changes that can be problematic because when the code is large enough, people simply do not know what of what they already know (what's already in their memory) is no longer true. This is the challenge. Instead, the proposition is that we should not have to rely on our memory of things that can change. We can just check it. Only to do it in a reasonable timeframe, we need custom automation. In any case, the article does not propose a tool. It proposes a way of working. The tool is important to show how it can work in practice.