>>That's engineering considering the long-term effects of your code. Both direct and indirect. No that is over engineering, and in violation of YAGNI (you ain

>>That's engineering considering the long-term effects of your code. Both direct and indirect. No that is over engineering, and in violation of YAGNI (you ain't going to need it) an KISS (keep it simple stupid) principles. A lot of code my teams develops gets thrown away over time, as it is either no longer needed or replaced with an off the shelf tool. It is really hard to predict what code will survive AND becomes a performance bottleneck. There is no point optimising prematurely. It is often best to tackle the problem when it occurs.