That approach is not without merit, however, it's still a possible dead end. I see this pattern happen consistently even with really good engineers: * Ident

That approach is not without merit, however, it's still a possible dead end. I see this pattern happen consistently even with really good engineers: * Identify a problem and design a solution for it * Apply the solution and it fixes the problem * Later a problem occurs with the solution, so * Apply a fix for that solution's problem * Later another problem happens somewhere in the "solution chain" and the same repair cycle is applied At a certain point, it's worth revisiting the original problem and its original solution and see if there's a better way to address it (especially with all the lessons ostensibly learned in the solution chain).