“How not to be wrong: The art of changing your mind” [affiliate link] is a follow-up to James O’Brien’s earlier book, “How to be right” The idea this time is that he walks through a number of areas where he has been wrong in the past and has changed his mind.

It’s such a simple concept, but, as a society, we have difficulty doing exactly that. Politicians are criticised for doing the wrong thing and then again for doing a u-turn. Tribal loyalty means that people won’t change their minds if that would mean agreeing with “the enemy.” I’m not putting myself above this¹, sadly, and neither does O’Brien.

I have a problem with this book [affiliate link]. Now that I come to write some notes on it, I find that there is so much that I want to quote that I may as well copy and paste the whole text.

I’m not going to, but here are a few.

I hate competitiveness, because I know I’m better than that.

And.

People say I’m self-deprecating, but I don’t think I’m very good at that.

I’m biased. As Mulder did, I want to believe. Except, I want to believe that being a generalist can work. And that’s what “Range” [affiliate link] by David Epstein, claims. It’s subtitle is, “How generalists triumph in a specialised world.”

It’s not a challenging read. There is a lot of anecdata, examples of people who took a broad path and still succeeded. In that sense, maybe it’s like “Quiet,” which is about introverts. It doesn’t tell you how to succeed, only that it’s possible and that you’re not alone. Maybe that’s enough?

Every year I try to complete the Advent of Code. Every year I fail to finish. I get about halfway through, and the exercises start taking longer to complete than I have time.

Every year I think about Jon Bentley’s Programming Pearls¹ [affiliate link], because the same kinds of challenges you find in Advent of Code can be found in the book. The main difference being the quality of the answers. At least in my case². In the words of the preface: “Programming pearls whose origins lie beyond solid engineering, in the realm of insight and creativity.”

I’ll be honest: I wanted to like “Facts and Fallacies of Software Engineering” [affiliate link] by Robert L. Glass more than I did. I’m not sure if it’s dated badly — it’s from 2002 — or I was in the wrong frame of mind, or something else, but it just didn’t work for me.

The book is structured as a list of facts grouped around areas such as “Management” and “Requirements.” For each fact, there is a discussion, the controversy, and then the sources and references. The writing aims to be friendly, but I found it a bit grating¹.

Before you ask, yes, it is weird that I’m reading a bunch of “management” books.

You can watch Michael Lopp’s career by following his various books. Start with “Being Geek” [affiliate link], the software developer’s career handbook. The move into management resulted in “Managing Humans” [affiliate link]. And his promotion from manager to director and executive gets you “The Art of Leadership” [affiliate link] which is the book I recently finished.

“Radical Candor” is one of those phrases that I’ve heard and wondered about. Is it another vacuous management phrase? Does it mean anything? I saw it in the library and thought I’d find out. I’m cynical about these things but it doesn’t mean I’m closed minded!

The pitch is “Be a kick-ass boss without losing your humanity” which sounds positive but I don’t manage people at work. Even if it contained genuine insight, would there be anything I could use?

A couple of years ago I did a conference talk called “On Cloud Nine: How to be happy migrating your in-memory computing platform to the cloud.” I wish I’d had “Cloud Without Compromise” back then. It covers much of the same ground but, as you’d expect in a book rather than a forty minute conference talk, in much greater depth. More importantly, it puts some concepts into context much more clearly that I did, either by explaining it better or by giving it a good name.

I failed to reach my target of reading twelve books in 2021 by quite some margin this year. I finished only ten books, and that’s including the cheat of counting two short stories as two books!

Despite my objective of reading more fiction, I also failed with that (just the one novel and the two short stories).

While the volume was down both on previous years and my target, the quality was actually pretty good. From the story of the company behind the BlackBerry to the story of the Seventies, how to build a computer and how computers were made. All were worth a read.

Empty shops, rising prices, the laughing stock of Europe, our place in the world in question, people out of work and fuel shortages. But that’s enough about late 2021, I decided that I wanted to learn more about the Seventies, the decade that brought, well, me, the Winter of Discontent, power cuts, the three day week and shocking fashion sense. There are a few books that cover the same timeline, but I decided on “Crisis? What Crisis?” [affiliate link] by Alwyn W. Turner.