1. 12
  1.  

  2. 5

    In many ways this book is an advanced sequel to SICP.

    I said baby, yes, hello! SICP is the most important philosophical work of the 20th century. Looking forward to dig into this one.

    I’d been hesitating because… Lack of flexibility never has been an issue I’ve been aware of running into before. Of course, that’s because I was already fully subscribed to the Kool-Aid of Scheme and refactoring (paredit convolute ftw) and design patterns—not on the level of what’s in here, but, enough to keep my mind clear and my shirt clean.

    1. 3

      In computer science we are taught that the “correctness” of software is pa- ramount, and that correctness is to be achieved by establishing formal specifi- cation of components and systems of components and by providing proofs that the specifications of a combination of components are met by the specifications of the components and the pattern by which they are combined. We assert that this discipline makes systems more brittle. In fact, to make truly robust systems we must discard such a tight discipline.

      I love it♥

    2. 3

      Reading this at the moment - I’m very interested to see if/how the concepts might apply to other languages (Rust, Go and Python in particular.

      1. 3

        Table of contents. I believe the last chapter on propagators is similar to this.

        1. 2

          Also reading this. Was already knee-deep in propagator network literature so I’m glad it finally has a textbook like this!

          1. 1

            Sussman has previously given some excellent lectures on the ideas in this book. I particularly like this quote https://youtu.be/Rk76BurH384?t=2343 .