Software fundamentals
by David Lorge Parnas, Daniel M. Hoffman, David M. Weiss · first published 2001
80% recommend20% neutral
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
Mentions per year
What Hacker News says
Related books
Collected papers
Slevin, Joseph Richard
Recommended by 2 · mentioned by 42 recommend · 4 mention2 recommend · 42 recommend
2020–2026Software Engineering at Google
Titus Winters, Tom Manshreck, Hyrum Wright
Recommended by 21 · mentioned by 2921 recommend · 29 mention21 recommend · 2921 recommend
2012–2024Making Software
Andy Oram
Recommended by 12 · mentioned by 2512 recommend · 25 mention12 recommend · 2512 recommend
2010–2024The Design of Design
Frederick P. Brooks
Recommended by 23 · mentioned by 3423 recommend · 34 mention23 recommend · 3423 recommend
2014–2025Grokking Algorithms
Aditya Y. Bhargava
Recommended by 42 · mentioned by 5942 recommend · 59 mention42 recommend · 5942 recommend
2008–2026Working effectively with legacy code
Michael C. Feathers
Recommended by 186 · mentioned by 234186 recommend · 234 mention186 recommend · 234186 recommend
2018–2026A Philosophy of Software Design
John K. Ousterhout
Recommended by 163 · mentioned by 232163 recommend · 232 mention163 recommend · 232163 recommend
2007–2026The Pragmatic Programmer
Andy Hunt, Dave Thomas
Recommended by 353 · mentioned by 589353 recommend · 589 mention353 recommend · 589353 recommend
…Peopleware 2007. Software engineering: Barry Boehm's lifetime contributions to software development, management and research. Ed. by Richard Selby. Hoffman, Daniel M.; Weiss David M. (Eds.): Software Fundamentals – Collected Papers by David L. Parnas, 2001, Addison-Wesley, ISBN 0-201-70369-6. You might also like my later book on technical design in general: The Design of Design. Start with Part…
on “Fred Brooks has died” ↗…https://en.wikipedia.org/wiki/Systems_thinking and https://thesystemsthinker.com/systems-thinking-what-why-when... ] For Software specific issues i highly recommend David Parnas' collected papers in the book Software Fundamentals. He and his colleagues defined much of what is mainstream in today's Software Architecture/Organization practice. Finally, the case studies given here are a great source of insights: https://aosabook.org/en/index.html
on “Ask HN: Best books on managing software complexity?” ↗Mentioned before, but I'll +1 these: - The Impostor’s Handbook: Rob Conery - Foundations of CS: http://blough.ece.gatech.edu/3020/focs.pdf Also be sure to check out - Software Fundamentals, essays by David Parnas Here's one of the essays from the book: https://www.win.tue.nl/~wstomv/edu/2ip30/references/criteria... Parnas promoted the idea of encapsulation before the word had even been…
on “Ask HN: What book to read to get a footing in CS theory?” ↗…Lister Peopleware - 2007. Software engineering: Barry Boehm's lifetime contributions to software development, management and research. Ed. by Richard Selby. - Hoffman, Daniel M.; Weiss David M. (Eds.): Software Fundamentals – Collected Papers by David L. Parnas, 2001, Addison-Wesley, ISBN 0-201-70369-6. - And his: The Design of Design. Start with Part II.
on “No Silver Bullet (1986) [pdf]” ↗'Elements of Programming' by Stepanov and McJones 'Software Fundamentals' by Hoffman and Weiss, 'Writing Solid Code' by Maguire, 'Code Complete' by McConnell
on “Ask HN: Top 10 Timeless Software Books That ChangedLife as Software Engineer?” ↗A good and concise (albeit old) SE book is "Fundamentals of Software Engineering by Ghezzi, Jazayeri and Mandrioli". For more background; "Software Fundamentals: Collected papers by David L. Parnas" is a great resource. For a tour of the CS aspects; see "Specifying Software: A Hands-On Introduction by R.D.Tennent"
on “Ask HN: Best book to gift someone for getting into software engineering?” ↗Thank you. Every Software Engineer should read Software Fundamentals: Collected Papers by David L.Parnas. People are nitpicking things and just parroting what is written in other books without really understanding the idea behind it all. For example what is a Interface/Class/Library/Framework/Module(logical…
on “Pretending OOP Never Happened” ↗A Classic. Folks interested in studying more of Parnas' foundational papers should checkout the book Software Fundamentals: Collected Papers by David L.Parnas. A good antidote to "cargo culting".
on “On the Criteria to Be Used in Decomposing Systems into Modules (1971) [pdf]” ↗Software Fundamentals: Collected Papers by David L. Parnas is an excellent compendium of Parnas' papers. You will find more wisdom here than most books on "Software Engineering" being published today.
on “On the criteria to be used in decomposing systems into modules (1972)” ↗>object oriented concepts like information hiding Having read "Software Fundamentals" [1], I think David Parnas [2] would beg to differ on that bit. Not the least because he actually invented the concept. Parnas wrote extensively on information hiding as the basis for modular program…
on “Pretending OOP Never Happened” ↗