1. 30
  1.  

  2. 5

    SICP brings wonders. The rest I don’t know.

    SICP: https://github.com/sarabander/sicp

    1. 6

      SICP is vastly overrated.

      1. 6

        Ok, I’ll bite. Why do you say that?

        1. 1

          I understand it doesn’t resonate with everybody, which is why I included it in the section of books good for specific interests.

      2. 4

        C’mon, these are great books even for the entry level grunt.

        And I struggle with “An Elegant Puzzle,” it is not a book I would recommend.

        1. 1

          That’s fair. Wasn’t sure if the “staff engineering” label made sense, but I went with it because

          • These books generally aren’t about actually coding
          • When I was getting started, the most useful books I found were the specifics of writing code (for Rails, HTML, CSS, etc)

          But agreed that these are probably great choices for anybody. Updated some wording in the article to account for this.

        2. 2

          For a “Staff” software engineer, this book should be on their reading list: https://www.amazon.com/Developer-Hegemony-Erik-Dietrich/dp/0692866809

          Not a book about programming, but about the corporate system they are part of.

          1. 2

            My take away is that you don’t need to read any book in particular to reach the ‘staff’ level. There’s nothing on this list that isn’t accessible to a junior with a year of experience.

            1. 2

              Definitely. Guess what I meant (and poorly explained) was that many people don’t think a lot about non-technical aspects of engineering until they get to senior levels. Or at least I didn’t 😬.

              Will update the article to reflect that. Thanks for the feedback!

              1. 1

                You’re welcome! I might pick up “The Pyramid Principle” based on this and JulianWgs’ comment

            2. 2

              Ok. With the risk of sounding stupid, What is a staff engineer?

              1. 1

                That’s not a stupid question, and I should’ve just titled this “my software engineering reading list”.

                Staff engineer is a level in many engineering career ladders, above senior engineer. I titled the reading list with “staff engineer” because I tended to read a different set of books than these earlier in my career, but now these seem to be the most impactful.

                But others in this thread rightfully pointed out that these books are useful for all experience levels.

                I would rename the post, but then that would change the url to the article 🤔

              2. 2

                I haven’t read it yet, but the author of An Elegant Puzzle also has a new book called Staff Engineer: Leadership Beyond the Management Track. Unfortunately, it’s self published, so it’s probably wise to wait for reviews.

                1. 1

                  I can really recommend „The Pyramid Principle“. It will change the way you structure your thoughts (and write better e-mails, if you are into that)

                  1. 1

                    Without a doubt! I’ve been using it a lot for proposals and presentations, as well.

                  2. 1

                    Thanks for putting this together! We went over Structure and Interpretation of Computer Programs in my programming languages course, but I’ll definitely add some of these others to my list of “eventually” books.

                    Also wanted to note that the ISBN for the first book is off. It looks like it may have been copied from the second in the list.

                    1. 1

                      Thanks for catching the ISBN error! Fixed.