DoesIntelliSenseImpareXP

This page extracted from WhyIsXpInDotNetDifficult

The expectations of Microsoft programmers are vastly different - IME wizards and ease of coding come higher in priority to quality. Programming by intellisense. Its often easy to knock-up something that works, but difficult to improve it.

This is down to discipline. It's just as easy to create bad code in other languages too. I tend to avoid all the evil wizards in VS and rely on trusted OO techniques to get the job done. -JoeW

-- Anthony: I do agree wizards don't always produce decent code, but don't really see the harm in intellisense.

Maybe its just that wizards discourage the act of refactoring and looking for bad smells. Intellisense in itself is not an issue, and perhaps this page is now poorly named and needs refactoring itself. The point is that wizards make code easy to produce, but do nothing to improve code quality and testability.

--

On the contrary, intellisense makes XP (in particular testing and refactoring) easier. Intellisense can vastly save the amount of time needed to figure out how to navigate around lots of finer grain objects and methods, encouraging the practise of tiny teeny small things.

Since using refactoring tools, I've found myself writing much better code because refactoring is just SO DAMN EASY.

Wizards on the other hand, are just pure evil...

-JoeW³host³³date³September 27, 2002³agent³Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)³DoesIntelliSenseImpareXP