A summary of all posts that conclude my review of the book a Philosophy of Software Design by prof. John Ousterhout.
71 – Review: A Philosophy of Software Design, Conclusion
#begin So that’s it everyone! We have discussed the entire book called A philosophy of software design. This was such an awesome book. I believe this book will go into history as one of the great books written about software design, like the GOF design patterns book...
70 – Review: A Philosophy of Software Design, Chapter 20
#begin The last chapter of this book is about designing for performance. You might have heard before that, really performant code if often obscure and unreadable. But in this next chapter Prof. Ousterhout will shed some light on how to design for performance. Up until...
69 – Review: A Philosophy of Software Design, Chapter 19
#begin Next is a short little chapter about Prof. Ousterhout’s view on popular software trends and how they relate to the principles of a Philosophy of Software Design. I remember reading this chapter a long while back thinking Prof. Ousterhout does not understand...
68 – Review: A Philosophy of Software Design, Chapter 18
#begin So next up is chapter 18 and it’s titled Code Should be obvious. Interestingly, this chapter comes after all the information about comments. This shows the importance of comments and summaries in the eyes of Prof. Ousterhout I think. He puts so much emphasis on...
67 – Review: A Philosophy of Software Design, Chapter 17
#begin Today we will discuss a really important topic in software design and development: Consistency. Yeah let's go! Consistency So chapter 17 is called Consistency. Prof Ousterhout says it’s a powerful tool for reducing the complexity of a system and making...
66 – Review: A Philosophy of Software Design, Chapter 16
#begin Next-up is a chapter about modifying existing code. And from what I can remember, this is very focused on, well... comments, again. John puts in a real effort to make it abundantly clear that comments are really important for good software design. I remember...
65 – Review: A Philosophy of Software Design, Chapter 15
#begin In todays blog we will take a look at chapter 15 of A Philosophy of Software Design. This chapter is going to be about a practice where you write your comments/summaries before you write any code. Sounds weird right? Write the comments first When I read...
64 – Review: A Philosophy of Software Design, Chapter 14
#begin Today we will take a look at a chapter where I think Prof. Ousterhout and Uncle Bob are somewhat on the same line again. Both of them want you to choose good names for concepts in your code. Uncle Bob has lot's of practical advise and Prof. Ousterhout shares...
63 – Review: A Philosophy of Software Design, Chapter 13
#begin We will continue our discussion about comments with another chapter about comments. This time Prof. Ousterhout will give some advise on how to properly write them. Let's see. And, well prepare for a rant. Comments should describe things that aren’t...
62 – Review: A Philosophy of Software Design, Chapter 12
#begin Hey, welcome back! Today we will dive into a really interesting topic of the book A Philosphy of Software Design. It's about comments and why we should write them. This highly contractics the practices presented in Uncle Bob's Clean Code which is why it's such...
61 – Review: A Philosophy of Software Design, Chapter 11
#begin On today's menu we got chapter 11 from a book called A Philosophy of Software Design. We'll be looking into a chapter that covers a really simple yet very effective practice which is design your solution twice (or more). Let's check out what Prof....
60 – Review: A Philosophy of Software Design, Chapter 10
#begin Today we will be checking out chapter 10 of the book A Philosophy of Software Design by John R. Ousterhout. Todays chapter is one of the chapters where this book gets its popularity from I think. When people talk about this book they will often mention the...
59– Review: A Philosophy of Software Design, Chapter 9
#begin In todays blog we will be diving into chapter 9 of A Philosophy of Software Design. In this blog we will discuss one of the most fundamental questions of software: Better together or better apart? Better Together Or Better Apart? What ever that means....
58 – Review: A Philosophy of Software Design, Chapter 8
#begin Heya there again and welcome back for another blog about A Philosophy of Software Design. Today we will be looking into chapter 8. Let's dive straight in. Pull complexity Downwards Chapter 8 is about pulling complexity downwards. This chapter provides...
57 – Review: A Philosophy of Software Design, Chapter 7
#begin How nice of you to join me on another blog about A philosophy of software design. Today's topic is chapter 7 Different Layer, Different Abstraction. A fundamental aspect of software is layered design, there is simply no escaping it. Let's find ou what Prof....
56 – Review: A Philosophy of Software Design, Chapter 6
#begin Hey and welcome back for another blog about A philosophy of software design. Today we are diving into chapter 6 General-purpose modules are deeper. Let's have a look! General-purpose modules are deeper In software design you often need to make a choice...
55 – Review: A Philosophy of Software Design, Chapter 5
#begin Today we will continue with A Philosophy of Software Design chapter 5. There are some really interesting concepts in here about information hiding, and leakage. I also particularly like how Prof. OusterHout describes there are formal and informal elements to an...
54 – Review: A Philosophy of Software Design, Chapter 4
#begin Hi there again! Today we are going to continue with a blog about another chapters in the book called A Philosophy of Software Design by John R. Ousterhout. We are going to dive into my favorite chapter of this book so without further ado, let's check it out....
53 – Review: A Philosophy of Software Design, Chapter 3
#begin Hi there again! Today we are going to continue with a short blog about the chapters in a book called A Philosophy of Software Design by John R. Ousterhout. On today's menu we have chapter three, working code is not enough. Let's take a look. Working code...
52 – Review: A Philosophy of Software Design, Chapter 1 & 2
#begin Alrighty! In the previous blog we got up to chapter 13 of the clean code book. Chapter 13 is the last chapter of the book I can meaningfully cover in a blog format. The remaining chapters are all case studies with a lot of code and examples. Uncle bob shows you...