A clean, if short (32 minute) version of Jim Weirich's talk on connascence is again online at Confreaks (Thanks, Coby!). See:
The Building Blocks of Modularity, aka The Grand Unified Theory of Software Development http://confreaks.com/videos/77-mwrc2009-the-building-blocks-of-modularity Just as some of Glenford Myers' work in "Composite/Structured Design" fails to match some aspects of OO development, some of Meilir Page-Jones work in "What every programmer should know about Object-Oriented Design" fails to match some aspects of Clojure, FP, etc. For example, Clojure's handling of identity and value certainly speaks to the question of "Connascence of Identity". I'm not sure how much effect immutability has on connascence. Certainly, "using the data as the API" (as Stuart Sierra recommends) differs markedly from OO best practices. However, the basic notion of identifying forms of coupling and thinking about their dangers (and benefits) is still very relevant. If you want a good introduction to the topic, this is a good video to watch. -r -- http://www.cfcl.com/rdm Rich Morin http://www.cfcl.com/rdm/resume r...@cfcl.com http://www.cfcl.com/rdm/weblog +1 650-873-7841 Software system design, development, and documentation -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
