Structured design
by Edward Yourdon · first published 1975
30% recommend70% neutral
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
Mentions per year
What Hacker News says
Related books
2007–2024Death March
Edward Yourdon
Recommended by 13 · mentioned by 2713 recommend · 27 mention13 recommend · 2713 recommend
2010–2026Nonviolent Communication
Marshall B. Rosenberg, Deepak Chopra, Magiarí Díaz Díaz, Alan Rafael Seid Llamas
Recommended by 99 · mentioned by 14099 recommend · 140 mention99 recommend · 14099 recommend
2007–2026Code Complete
Steve McConnell
Recommended by 393 · mentioned by 669393 recommend · 669 mention393 recommend · 669393 recommend
2007–2026The Little Schemer
Daniel P. Friedman, Matthias Felleisen
Recommended by 288 · mentioned by 438288 recommend · 438 mention288 recommend · 438288 recommend
2007–2026Peopleware
Tom DeMarco, Timothy Lister
Recommended by 276 · mentioned by 415276 recommend · 415 mention276 recommend · 415276 recommend
2014–2026Designing Data-Intensive Applications
Martin Kleppmann
Recommended by 457 · mentioned by 659457 recommend · 659 mention457 recommend · 659457 recommend
2007–2026Structure and Interpretation of Computer Programs
Harold Abelson, Gerald Jay Sussman, Julie Sussman
Recommended by 347 · mentioned by 602347 recommend · 602 mention347 recommend · 602347 recommend
2007–2026The Mythical Man-Month
Frederick P. Brooks
Recommended by 383 · mentioned by 760383 recommend · 760 mention383 recommend · 760383 recommend
…was a library book that should never have been taken out of circulation. It discusses an important aspect of software design that gets little love in the mainstream. I also got a copy of Yourdon's "Structured Design," which was originally released just as OOP was getting big. But... it still contains numerous pearls of wisdom suitable for both OOP and Functional programmers.
on “Ask HN: Are older programming books useful?” ↗Mythical Man Month by Fred Brooks is pretty good. There is also the Design of Everyday Things (TDoET) by Don Norman. Structured Design from 1975 by Larry L. Constantine and Ed Yourdon is another excellent book that I am currently reading now.
on “Ask HN: Reading material on how to be a better software engineer?” ↗…recommendations, I suggested that Ed add it to his own list of "cool books." He replied promptly and agreed. Although I didn't read it from cover to cover, the chapters I read from a borrowed copy of Structured Design on coupling and cohesion had a big impact on me.
on “In memory of Ed Yourdon” ↗…Cleary), but would kill for this Yourdon-Constantine one, as well as the story behind it. I actually worked for a CASE vendor that started by building tools to apply Yourdon et al.'s Structured Analysis and Structured Design to important systems, in mil/aerospace/datacom. (I was lucky to be the teen mascot on our full-lifecycle evolution of those tools, in the Portland division, and then on an R&D team at HQ for next-gen…
on “How I came to write “Tidy First?” tl;dr it took 18 years” ↗…OOP still relevant? I haven't read either, personally, though I have Yourdon's book en route. We use the term "structural design" quite a bit, so I'm curious to see Yourdon's take on what they call "structured design". From everything I've read about it, it sounds very similar to a lot of how we think about things as it seems to be the basis for much of the coupling and cohesion thought in our industry. I'd also…
on “Subject-First Commit Messages” ↗…generous response! Yeah, I'm agreed on most of the AI stuff - becoming a more architect-shaped engineer is now more important than ever. I've been flicking through a copy of https://www.amazon.co.uk/Structured-Design-Fundamentals-Disc... lately to get my brain into gear on this subject. Thanks for all the web dev advice and tech callouts. Some real neat examples there which I knew nothing about. Regarding niches,…
on “Ask HN: What Are You Learning?” ↗…experience and skills, not just a good memory and algorithm for spewing out code. And I know businesses will need people who can solve business problems rather than just write code. [1] https://www.amazon.com/Structured-Design-Fundamentals-Discip... (for example) [2] https://www.amazon.com/Reliable-software-through-composite-d... (for example) [3] https://en.wikipedia.org/wiki/The_Mythical_Man-Month [4] http://doc.cat-v.org/bell_labs/utah2000/…
on “Ask HN: What skills are worth learning long-term against AI?” ↗I found the Structured Design book on there (http://vtda.org/books/Computing/Programming/) that was referenced by https://news.ycombinator.com/item?id=35246995.
on “The Vintage Technology Digital Archive” ↗…that originate from antiquated "best practices" from the dark ages that don't actually improve safety. We have it today by way of IEC 61508, which gets it from a book on structured programming called Structured Design. That book didn't recommend banning multiple exit points, but it recommended minimizing them to simplify the control flow graph and said code should minimize the distance between black boxes (bits of…
on “Show HN: I built an embeddable Unicode library with MISRA C conformance” ↗…https://en.wikipedia.org/wiki/Prolog%2B%2B to allow one to do large-scale OO programming with Prolog. Earlier, Prolog was used in AI/Expert Systems domains. Interestingly it was also used to model Requirements/Structured Analysis/Structured Design and in Prototyping. These usages seems interesting to me since there might be a way to use these techniques today with LLMs to have them generate "correct" code/answers. For Prolog and LLMs see - https://news.ycombinator.com/item?id=45712934…
on “Learn Prolog Now (2006)” ↗