Where should the type information be 342

Thats the good thing, but then call them ''lore''. There have been important and interesting books about programming lore.

Or worse, see below :-)

The ''pattern'' movement, sometime explicitly, more often implicitly, seems based instead on the core premise-promise of most commercially successful ''methodology'' propaganda, that they enable the near-complete deskilling of the vast majority of programmers.

Basically the kicker is that ''patterns'' are programs for programmers, and that astute managers can run a software shop as a plantantion: a few ''creative geniuses'' (I have heard this expression used entirely seriously in more than one case) as analyst gangmasters, emanating sequences of ''patterns'' to be mechanically coded by the yard by illeteterate :-) coder peons chained to their cubicles, probably while singing nerd blues off key (with a strong hinglish accent) :-)

The same premise, the ability to get dumb programmers to execute ''programmer programs'' was the lure behind most other ''methodologies'', from the ancient JSP (Jackson's) to UML (the diagrams being the ''programmer programs'').

Or worse, see below :-)

Ah yes, I like that book. Some people love it too much...

mobile phone OS company some teams competed at antipattern bingo (how many antipatterns can we find in our project) and even at at how many antipatterns could be added to their projects.

Allegedly one team was aiming to achieve all of them (easier than it seems as relatively few were not

Note: I hope I am not giving any coder peons any perverse ideas here. :-)