It's the mark of a very bad writer, to take several sources of respectable ideas and use them to get to a conclusion worse than the original.
It would be like an engineer taking the finer points of concrete and steel and making something weaker than wood. I believe it takes talent to be that talentless.
"It would be like an engineer taking the finer points of concrete and steel and making something weaker than wood."
That's a bit antisocial to bring that metaphor up around programmers... that's uncomfortably close to what we do all the time.
Just this week I was examining a project built on Java and Struts and a couple of other rock solid Java technologies, and the end result... well, you name the problem and it had it, inconsistency, no conceptual integrity, bad performance, terrible code... 'twas horrible what they did to Java. I don't like Java, but it doesn't actually have to be this bad...
(I found myself making this metaphor: It was like the team was situated in front of a bulging dam, armed with a firehose that sprays Java code. Every time a crack appears, they shoot the hose at it and spray out a few more hundred gallons of code. Eventually you're left with nothing but a mess.)
lmao, for whatever it's worth, the guy or gal has taken his/her time to go through the studies and present the information. To compare abstract thought with concrete objects is perhaps talentless :P
