I agree with this premise entirely....however, in the .Net world, at least in my experiences, the smartest (in terms of raw mental capabilities and depth of knowledge) are also the people that write the most verbose, complicated code to do the simplest things...generally I suppose under the guise that it will be "more flexible" I suppose. Often times after enough frustration I've rewritten some of the code in question in one fifth the size, which handles more scenarios, runs faster, and usually even a junior programmer could figure it out.
I often read people making fun of the grossly overarchitected solutions in the java world, but I personally feel the same way about the .Net world, at least when it comes to code written by people who are in most ways genuinely the smartest, most capable developers I have worked with.
Any other .Net people feel this way or am I missing something?
I've noticed a corresponding tendency, but amongst the most experienced (But not most capable).
The longer someone's been a '.Net Programmer' (rather then a programmer who does .Net) the more likely they are to over-architect, over design and use frameworks and tools that are just...wrong.
I often read people making fun of the grossly overarchitected solutions in the java world, but I personally feel the same way about the .Net world, at least when it comes to code written by people who are in most ways genuinely the smartest, most capable developers I have worked with.
Any other .Net people feel this way or am I missing something?