Reliable software through composite design
by Glenford J. Myers · first published 1975
3mentions
3recommended by
3HN commenters
2012–2023first – last mentioned
100% recommend
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
…Software Tools by Kernighan and Plauger. Can be 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…
on “Books Programmers Don't Really Read But Recommend” ↗…COBOL, PL/1 and a bunch of other non-OOP languages, and those who think procedural programming is better have probably never done it. The starting point for OOP, at least for me, was the splendid book "Reliable Software through Composite Design" by Glenford Myers, which was the first to study coupling, cohesion and other techniques that lead directly to OOP. This book still maintains a position of honor on my shelf, and I strongly recommend…
on “Object-Oriented Programming – The Trillion Dollar Disaster” ↗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 developer should have. Keep in mind this is before…
on “You Want Modules, Not Microservices” ↗