Well.. it's not like your comment bursts with cleverness either. But yeah, I clearly overdid it... I just got triggered by that presumptuous comment. I'm really sorry, but I have to work with code written by these "pragmatic, quick 'n dirty"-people everyday. Yeah, the kind of guy who is liked by the management because "they get things done"... IMHO people like that can go and write a poc.. or something that can be thrown to the garbage, but not something that has to be maintained over many years by a lot of different people. Please keep them away from anything serious. Their short-term pragmatic and profitable solution doesn't come for free - it is based on the debt left for others to pay in the future... I am not saying there isn't such thing as overengineering. There is a lot of that too, rest assured that I've seen it more than enough. But overall, I've seen 10x more code that is hard to maintain because it was written by a "cutting-the-crap" guy compared to a something that is problematic because it was overengineered... anyway, that's just my opinion.