Today, I finished Algorithms to Live By – The Computer Science of Human Decisions. I found out about this book at a meetup about software craftsmanship. At the meetup, we discussed the first chapter of the book and it looked very promising. Hence, I decided to read it. Here’s what it did to me.
Last week I read The Five Dysfunctions of a Team: A Leadership Fable. It’s a non-fiction book about teamwork and what makes teams fail, but told via a fable. It’s a fun read and Patrick Lencioni adds cool characters for his story.
So, what did I think about the book?
I have been a fan of xkcd for quite some time. A lot of Randall Munroe’s comics concern IT and technology jokes, and I’m always in for that! On his website, he also has a “what if” inbox. Here, he allows people to ask absurd hypothetical questions which he will answer as seriously as possible. And then he went and made a book of those questions and answers!
Wow. I have never read a non-fiction IT book before. The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win helps you understand what the value of IT is in modern organisations. While I have some doubts about the stories, I do like that as an IT guy I can relate to much of the problems presented.
Let’s have a look at The Phoenix Project.
I’ve been catching up to a lot of things lately concerning my work environment. Not only do I work for a great company, I also like what I do there. Why is that? Why do I like to go to work while I know other people who are having difficulties getting to theirs? A colleague suggested I would read the Drive book. And so I did. Here’s what I think of it.
I like feedback. It’s great. Totally awesome. Sorry, let me untrumpify that: I enjoy feedback a lot. I think it is a great tool to learn things and to adjust your course. And it helps you improve. At my job, we try to continuously improve ourselves and our projects. One means of getting feedback, is through retrospectives. And to improve those, I decided to read this book.
Every day, I work, eat and read. In between, I work as a software engineer. I’ve had the luxury to start my career working on a scrum team. I’ve been in the industry for some time now, but wanted to know more why that first team was doing so good. What is behind this process? I thought I’d read it best from mister Scrum himself.