I found a list of books someone had read and liked the idea, so I wanted to start a list of my own. The list is in reverse chronological order, but only goes back as far as I could remember when I started the list, which was sometime in 2017.
Under each book I've put a short summary of what I ended up getting from the book as well as my general sentiment about the book.
Listened to the audiobook. I enjoyed the book, but I can't say there was a big takeaway from it for me. I thought the world in the book was interesting and the motivations and mechanisms of the party were interesting, but I don't think there was anything in it that changed my worldview on real-life issues of government. I think the world described in 1984 is quite unrealistic.
Slightly positive sentiment. Would recommend it as interesting but not an essential read by any means.
Only read about half of it. It was much more academic than I expected and I have no experience reading academic literature in that area of study, so it was quite difficult to read.
One interesting point was that people hate being forced to wait in western culture because time is valuable. When one's time is wasted, it can be interpreted as them not being valuable, which is why people hate having to wait.
Neutral sentiment, but probably wouldn't recommend to anyone because of its difficulty.
I stopped reading this book on page 254/440. I felt that I was getting very little out of the book for the time I was putting into reading it.
The biggest takeaway I got from it was a kind of meta-takeaway, which was that many of the programming languages we have today were created for very different reasons. Some were meant to be very practical and an improvement on an existing language, like C++ and Objective-C. Some were based on academic theory like Haskell and ML. Some were created for specific domains, like awk and APL. Forth stood out to me as the most unique out of the languages I got through.
Slightly negative sentiment
Running a business should heavily use the scientific method to test your assumptions, understand your customers and the market, and learn what is important to work on and what isn't. The faster you learn, the faster you'll move towards a sustainable business. You need feedback as early and often as possible, forever. If you're not setting up a hypothesis and running an experiment to either confirm or disprove it, then you have no way of measuring what you've learned. In the book the author often mentions that businesses who just makes changes and "see what happens" will achieve just that: they'll see what happened. However, without hypotheses and careful experiments, they have no way of knowing what caused any change in the metrics they're using. Lean is all about learning as fast as possible and applying what you learn. If you can't apply what you learned, you didn't learn anything useful.
Here are the notes I took while reading the book:
The Five Whys is a method you use when there's a problem. You ask Why did the problem occur? Then ask that question again for the answer, and repeat until you've gone through five levels of understanding why the problem occurred. An important part of the Five Whys is that you fix each of the five problems at the five levels, not just one of them.
I think the biggest takeaway I got from this book was how to recognize a bad design. If you can recognize exactly what it is that makes something bad, you have a great starting point for how it can be improved. I also learned some new words related to design in this book, namely "affordances" and "signifiers". I really liked the chapter on design thinking and would recommend reading just that chapter to anyone.
The way to God is not through ritual, practice, or works. There is no intermediary between us and God. The law (old testament) is a means to an end (God), not not the end in and of itself.
I really enjoyed the message of the book and it's widely applicable to all parts of living a Christian life.
I also liked that it includes a chapter or two on some of the terrible things that have happened in church history.
The single biggest takeaway I got from it was the importance of naming variables and functions. You can communicate so much by using great names in your code. I think names are vastly underappreciated in their power to make the code read like prose. There were a lot of more subtle takeaways too that I won't list here. Another big one though was that code has two steps: Get it working, and make it beautiful. A lot of people stop after it works and don't refactor and rethink the code to make it as simple and readable as possible. It also definitely convinced me of the importance of unit tests.
Suggested by a good friend of mine. His recently-married brother read it and his parents are well-read and a big fan of this author.
This book was well-written and the content was good too, but it jumped around between many different topics which I feel took away from its impact. For example, I'm writing this in early July 2018, roughly a month after I finished reading it and it's hard for me to think of a strong takeaway, but I remember having lots of good converstations with my wife about points brought up in the book while I was reading it.
Slightly positive sentiment
My wife and I read this on the beach on our honeymoon. Read within a few days.
Given to my wife and I as a wedding gift from our friends who had recently gotten married and liked this book. I liked the message and the points made, but I don't think it was as well-written as other books I've read. This was admitted in the book by one of the authors though (Francis), which was nice because I could focus on the message instead of getting distracted by the medium.
Main takeaway: Christian life has an end goal in mind: spending eternity with God in heaven. Obviously I knew that technically, but I had never heard that perspective discussed in any depth, and I'm glad that I can't say that anymore thanks to this book. It's an important perspective to be able to look from. Really emphasized what it means to live for God first and foremost, and how important that is in a marriage context.
This is a really great book. It's a lot of almost-primary information coming from someone who's done a lot of the research himself. He writes in a very neutral tone, and the book is exceptionally well organized.
Main takeaway(s): There are two systems: System 1, which is unconscious, pattern-oriented, fast, and takes no energy to use, and System 2, which is conscious, is able to synthesize new ideas from existing onees, is slow, and requires effort. There is also Econs vs Humans, and the Remembering Self vs the Experiencing Self.
This book has a lot of really great information that is easily applicable to your life in so many ways. I definitely feel like I understand my own thoughts and actions as well as those of others after reading this.
I have mixed feelings about this book. I think the author has wisdom to offer, but I also think he makes a lot of dubious claims as well. This is a book that you could tear apart if you take things at face value, but for me to do so accomplishes nothing. Rather, I'm trying to look past the questionable parts of the book and take away only the valuable parts.
The main valuable point that I took away from this book is that masculenity is real (whether or not you accept how the author defines it). Masculenity is something that is never talked about in my own experience, but it is something vital to every boy and man. The book made me realize that there is something necessary in having other men in your life, a "band of brothers" as the author puts it. Young men need to know they're a man and that they have what it takes.
The book inspires bravery and a willingness to take on the unknown and conquer it. The unknown is pursuing your passion in your career. Pursuing a woman you want to date, or pursuing the woman you are already with. Standing up for what is right and not backing down. I think that a key aspect of being a man is that you take responsibility when no one else will. That's a man. A man takes responsibility for calling someone out. A man takes the responsibility of fixing things, planning things, doing things. A man takes the responsibility for asking out a beautiful girl and treating her right. A man doesn't do what's safest, try to protect himself from pain at all costs. A man instead pursues what is noble and right. He pursues his dreams. He pursues his woman. He fights to protect his loved ones and puts their safety ahead of himself. He takes responsibility. He fights for something.
This book is essentially a list of 99 cognitive biases. The author adds a few examples in each chapter to illustrate each bias. Funny enough, these examples clearly show the author's biases. He's clearly a big fan of Charlie Munger, Warren Buffet, Nassim Taleb, and Daniel Kahneman. Taleb's Antifragile and to a lesser extent Kahneman's Thinking, fast and slow are cited several times throughout the book. This isn't a criticism though. It's just a note that this book is secondary knowledge, and it might be worth reading those two books for "more primary" knowledge.
The author also has a very obvious bias against religion and often uses it in examples to illustrate irrational thinking. I don't expect him to know everything though, so he can be forgiven for being clueless about Christianity.
This book changed the way I think in small but positive ways. For example, it has made me much more comfortable with the randomness of life. When you read all of these flaws in our thinking that we fall into constantly, you realize that we have much less control over things than we like to think we do, and by the end of the book I had internalized that thought even though it is something I've considered myself to have "always known". I'm also more comfortable ignoring books or ideas about patterns in things that supposedly lead to success, because such things reek of Survivorship Bias, Clustering Illusion, and the Illusion of Control. Same goes for people who have started small businesses and run them successfully. I used to hold such people in high regard, feeling like I might never have what it takes to start my own business one day. Now I don't hold them so highly, and think rather that it takes a combination of modest smarts, hard work when it's needed, and plenty of luck.
Starting a small side business is plausible, especially if you're a knowledge worker. Neutral sentiment.
No one - not even the most orthodox religious groups - follow the Bible exactly literally. Therefore everyone picks and chooses the rules they wish to follow. Positive sentiment.
Outsource or ignore tasks that you are able to. Slightly positive sentiment.
There is a difference between "shallow" and "deep" work. Deep work takes significant time and focus, and requires large, continuous, uninterrupted blocks of time to accomplish. Focus is a finite resource. Slightly positive sentiment.
Even those with a lifetime of leadership and experience in the church can have doubts, and it's ok to have them. Neutral sentiment.
Hofstadter argues that consciousness is an emergent property of complex formal systems that have the property of self-reference (I think). Neutral sentiment.
Name something after someone you want something from. Slightly negative sentiment.