I couldn't agree more with the conclusion that NPP's (non-programming programmers) should be eradicated. Lately I've been, jokingly but with a very serious undertone been saying there should be a world wide register for these individuals so they can't ever work in that field again, for the protection of everyone who values the work they do. Lately I've been working on a project that involves an API that's clearly written by NPP types and the entire API is a complete example with 100% coverage of what *not to do* in .NET. It's a total inverse of every best-practice as if there was a contest to see how bad one could screw up an API. Needless to say, once the multitude of problems came up, try to communicate and explain the problem when the other side you're dealing with consists of NPP types. And then you provide them with profiler output that clearly identifies some very major problems, you point out exactly where, and even explain *how* to fix it with a few lines of code and you don't get anywhere with them because they just don't seem to understand *anything* at all. It certainly made me wonder how people like that got their jobs doing what they're (clearly NOT!) doing. Your post highlights, once again, one of the very serious gravitational black holes in the industry.