A Philosophy of Software program Design by John Ousterhout


I just lately completed studying A Philosophy of Software program Design by John Ousterhout and I assumed that it will be helpful to share my opinion about it with the group.

My motivation for selecting up this ebook was that I noticed that it is among the greatest sellers in Amazon and it had a variety of good critiques.

Concerning the creator #

The creator of the ebook is John Ousterhout. He’s a professor of pc science at Stanford College. He was a professor of pc science on the College of California, Berkeley the place he created the Tcl scripting language and the Tk platform-independent widget toolkit and proposed the concept of co-scheduling. John Ousterhout has achieved some vital contributions to the sphere of pc science and has been awarded a Grace Murray Hopper Award and an ACM Software program System Award.

Concerning the contents #

This ebook was written by John Ousterhout for use as the primary studying materials of one of many topics within the pc science program at Stanford College. Regardless of the highly-academic background of the creator and being a part of the content material of the pc science program at Stanford College, the ebook is written in a really colloquial type that may be adopted with straightforward by non-academics and newbie pc science college students.

I’m an skilled developer and I’ve heard about most of the concepts within the ebook earlier than. Nonetheless, I nonetheless loved this ebook as a result of I feel the creator has achieved an excellent job extracting the essence of some ideas and placing it down in phrases. I significantly loved the sections about complexity, interfaces, and abstractions.

I additionally loved that the creator dares to problem some frequent greatest practices akin to “capabilities ought to be small” or “courses ought to solely do one factor” as a result of it encourages experimentation and being open-minded.

The ebook is split into the next 21 chapters:

  1. Introduction
  2. The character of complexity
  3. Working code isn’t sufficient
  4. Modules ought to be deep
  5. Data hiding (and Leakage)
  6. Normal-purpose modules are deeper
  7. Totally different layers, totally different abstractions
  8. Pull complexity downwards
  9. Higher collectively or higher aside?
    10 Outline errors out of existence
  10. Design it twice
  11. Why write feedback? The 4 excuses
  12. Feedback ought to describe issues that aren’t apparent from the code
  13. Selecting names
  14. Write feedback first
  15. Modifying present code
  16. Consistency
  17. Code ought to be apparent
  18. Software program tendencies
  19. Designing for efficiency
  20. Conclusion

I actually loved the primary half of the ebook. The primary chapters talk about the character and the primary causes of complexity in software program. The next chapters discover some frequent design issues in modules, interfaces, abstractions, coupling, and error dealing with. The ebook highlights the primary issues as an inventory of pink flags that we must always keep away from. I disliked that a few of the concepts felt one way or the other opinionated and not likely goal. Nonetheless, I didn’t have a giant drawback with it as a result of I truly agree with a lot of the factors of view of the creator. Additionally, he wouldn’t be capable to problem some frequent greatest practices with out being opinionated.

After chapter 11 the content material was much less interesting to me as a result of I felt that I wasn’t studying as a lot as I used to be studying in the course of the first half of the ebook. Nonetheless, that is in all probability my case as a result of I’ve learn different books (e.g. Clear Code) on related subjects.

I’d advocate the ebook for each senior and junior builders as a result of I actually loved the primary half of the ebook and I assume that some much less skilled builders will discover the second half of the ebook extra attention-grabbing than I did.

I’d additionally like to say that this ebook within reason low-cost. Many tech books have a value mark of 40 to 60 USD and this books obtainable for 17.27 USD in its paperback version. Sadly, the ebook will not be obtainable in digital codecs.

Should you assume that you’d take pleasure in this ebook, it is possible for you to to buy it on-line at Amazon UK or Amazon US.

I hope you may have discovered this evaluation helpful. I’ve plans to attempt to evaluation all of the tech books that I learn from now personal. So please comply with me if you wish to learn extra ebook critiques sooner or later.







Leave a Comment