14 Dec
2006
14 Dec
'06
5:27 p.m.
On Thu, 14 Dec 2006, Kirsten Chevalier wrote: ...
If you want to learn how to "think" functionally, forget you ever heard the words "design pattern". There shouldn't be patterns in your programs. If there are, that means that either your language isn't providing you with enough abstractions or that you aren't using the abstractions that are available (or possibly both).
Well, maybe not Patterns, but wouldn't there be important skills relating to patterns in a more general sense? Like "fold", for example, seems to be a pattern, with several standard implementations and no doubt countless others to suit particular applications. Donn Cave, donn@drizzle.com