Comment on 100 patterns every developer should know

I always find it interesting that we think most developers are capable of following or recognizing a good design. Nick sugests that there are potential 100 essential patterns that each developer should know. I think patterns are far beyond hard for an average developer.

As my favorite software legend Juval Lowy of IDesign would say "its all plumbing". This plumbing should be left for people like Juval. So what is the solution? It depends (Juval's favorite).

If we can progress from Assembler to C/C++ to managed code, shouldn't we be able to do something similar and eliminate patterns completly?

Noteworthy Feb, 2007

Remote Desktop Connection 6.0 client update is available for download in the Microsoft Download Center
http://support.microsoft.com/kb/925876

Hawkeye - The .Net Runtime Object Editor
http://www.acorns.com.au/Projects/Hawkeye/


http://jayflowers.com/joomla/index.php?option=com_content&task=view&id=13&Itemid=38


.NET Application Extensibility
http://msdn.microsoft.com/msdnmag/issues/07/02/CLRInsideOut/default.aspx

PageAsyncTask Class (not for the novice developer)
http://msdn2.microsoft.com/en-us/library/system.web.ui.pageasynctask(VS.80).aspx

User Interface Process Application Block - Version 2.0
http://www.microsoft.com/downloads/details.aspx?familyid=98c6cc9d-88e1-4490-8bd6-78092a0f084e&displaylang=en&tm

howard gardner, multiple intelligences and education
http://www.infed.org/thinkers/gardner.htm#multiple_intelligences