My learnings from the book "A Philosophy of Software Design"
Table Of Content Solid recommendations I agree with Implementation comments: what and why, not how A philosophy of software design - John Ousterhout Chapter 5 — Information Hiding (and Leakage) Define Errors Out of Existence How can social robot use cases in healthcare be pushed - with an interoperable programming interface Chapter 14 — Choosing Names Pass-through variables add complexity because they force intermediate methods tobe aware of their existence, even though the methods have no use for thevariables. Below are the notes I made on takeaways from the book and my thoughts on acouple of the ideas (minus some fun references to real code that I've workedon). I'm publishing the notes as it's a nice way for me to re-read them andretain the information. This doesn't cover all the content in the book, and it'spossible that I misrepresent the author in some of my paraphrasing. If you'reinterested in the content I definitely recommend buying a copy - it's...