Ever felt the more you programmed, the crappier a programmer you were becoming? It could just be your editor of choice. I read this thought provoking and mostly amusing article from a guy who is bagging out Microsoft's MS Visual Studio.
Some good quotes from the article.
On Intellisense: "Human beings have never been inclined to refrain from pursuing certain technologies because they may have unfortunate repercussions."
On interactive design tools: Eventually, the interactive design stuff found its way into development with C++ and the Microsoft Foundation Classes, and there, I truly believe, code generation was used to hide a lot of really hairy MFC support that nobody wanted to talk about.
On visual studio: Almost twenty years after the first Dialog Editor, Visual Studio is now the culprit that generates ugly code and warns you not to mess with it.
and
But Visual Studio is not interested in having you write good code. It wants you to write code fast.
Whilst the majority of the article is MS specific, it applies to every IDE. So don't you snicker at the evils of MS all your open-sourced Eclipse fanboys because it still applies here.
Overall a good read.
2 comments:
Correct me if I'm wrong but where Mr. Charles Petzold writes "But Visual Studio is not interested in having you write good code. It wants you to write code fast", isn't that the whole reason your using the IDE for? You want code, put together as quickly as possible.
True, using an IDE, just like most WYSIWYG programs, do 'blunt' your coding ability, but when your busy pulling together this applications isn't it more of a case of the outcome is more important than the means to it? Sure it would be nice if everything was put together in nice clean code and ran as efficently as possible, but can you justify that extra say 5-10% performance for all that extra time it will take?
Don't get me wrong, I agree with what he says in most parts, but lets be honest, nothings going to change not from the end we are at.
vi/vim/gvim 7.x FTW.
Post a Comment