Thanks. This one is working: http://confreaks.com/videos/77-mwrc2009-the-building-blocks-of-modularity http://confreaks.com/videos/77-mwrc2009-the-building-bloc

Thanks. This one is working: http://confreaks.com/videos/77-mwrc2009-the-building-blocks-of-modularity http://confreaks.com/videos/77-mwrc2009-the-building-blocks-... He mentions that back in the 70s he was writing Fortran for NASA and his mentor recommended he read a book called Composite/Structured Design. "Structured Design" was the big thing back then and the controversy was using if-else and while loops instead of Gotos. Nobody was worried about strongly vs weakly typed langauges (perl!).. Key chapter in that book is on Coupling and Cohesion. Junp to the late 90s for his second book recommendation: "What Every Programmer Should Know About Object-Oriented Design", really just the third part of the book which introduces "connascence". Two pieces of software share connascence when a change in one requires a corresponding change in the other. I love the historical angles on this stuff.