
Composite/structured design
by Glenford J. Myers · first published 1978
3mentions
2recommended by
3HN commenters
2012–2023first – last mentioned
67% recommend33% neutral
Affiliate links. As an Amazon Associate I earn from qualifying purchases.


…thought of as the poor-man's Dragon book. The Practice Of Programming by Kernighan and Pike. As if the UNIX way needed any defending after almost 40 years. Reliable Software Through Composite Design and Composite/Structured Design by Glenford Myers. You have to get past the ancient languages and flowcharts. These books describe modularity and module strength and coupling and are full of good ideas that still apply. Database In…
on “Books Programmers Don't Really Read But Recommend” ↗On the subject of modules, I often recommend “Composite / Structured Design” and/or “Reliable Software Through Composite Design” by Glenford Myers. It’s old. The examples are in PL/I. But his framework for identifying “Functional Strength” and Data Coupling is something every…
on “You Want Modules, Not Microservices” ↗…This one is working: 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…
on “Rich Hickey: Simple Made Easy” ↗