Part of the Twenty Books in Twenty Days series.

I lent “Peopleware” [affiliate link] to a friend at some point but never got it back. I supposed they valued it as much as I do. I should probably buy the newer edition at some point.

I’m not sure if this book was the epiphany or it just happened around the same time, but at worst it was a major influence. The epiphany was that the really hard challenges in computer science were not the technical ones but the ones around people. It doesn’t mean that it’s not valuable to work on technical problems or solve them. But the challenges organising and getting people to communicate and work together effectively and build the right thing (rather than the interesting thing that we want to build) are also important, possibly more important.

Part of the Twenty Books in Twenty Days series.

At some point I realised I would never be a great programmer. It’s possible that point came when I read this book, where Bentley [affiliate link[ iterates on a number of problems, gradually improving them. Maybe I couldn’t do what the author does, but it’s a fascinating, well written journey.

Part of the Twenty Books in Twenty Days series.

I was given the first edition of Code Complete [affiliate link] in a training course in my first job, post-university. My Computer Science degree covered a number of sophisticated but impractical techniques for software engineering, the most memorable being testing. By comparison, Code Compete was incredibly refreshing. Its advice is practical and pragmatic, yet based on solid research and experience. It also rarely says “this is the way” to do something. Instead, it will list the advantages and disadvantages of various approaches. I treat with suspicion anyone who advocates for One True Way to do something.

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¹, 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” 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,” the software developer’s career handbook. The move into management resulted in “Managing Humans.” And his promotion from manager to director and executive gets you “The Art of Leadership,” which is the book I recently finished.

My career has not followed the same trajectory. I continue to be an “individual contributor,” so why would I read this book?

While I have more than enough books on my “to read” list, I am always up for suggestions. “Code” came up in a Twitter conversations about computer hardware. I noted that one of my favourite courses from my Computer Science degree (in hindsight if not at the time) was where we went from “What is electricity?” right up to a pretty much fully working CPU. “Code” was recommended as it covers the same ground.

This is probably the geekiest book I’ve read in a long time. It’s basically one step up from reading the source code for your favourite operating system. Or perhaps having a favourite operating system.

What I would say is that Unix has been pretty much the only constant throughout my career. I started with Solaris and HP-UX at university. I installed an early version of Linux on my personal machine to avoid the thirty-minute walk from home to the university labs. I’ve done consulting, I’ve developed both vertical and horizontal applications¹, C and C++, Swift and Java, banking and telecoms. Pretty much the only thing they’ve all had in common was some sort of Unix underpinning.

• Android Orphans: Visualizing a Sad History of Support – I think this is one of Androids biggest failings.
• John McCarthy — Father of AI and Lisp — Dies at 84 – Really not a good month for IT or Computer Science.
• The original iPod, 10 years later: a re-review – The original iPod is ten years old and, actually, stands up pretty well.

• News Corp to Offer Plaid Stamps! – “Giving Murdoch the benefit of the doubt, then, I’m guessing he simply doesn’t mean what he said. Perhaps he just wanted to sow a little confusion, get some publicity and maybe a concession or two from Google.”
• The night the Berlin Wall fell – “For me it was that rare occasion when a story was unqualified good news. After years watching the way communism was practised, I felt no need to mourn its collapse. Whatever came next had to be better.” Twenty years since the fall of the Berlin wall.
• OMG Ponies!!! (Aka Humanity: Epic Fail) – “The real world has failed us. It has concentrated on local simplicity, leading to global complexity. It’s easy to organise a meeting if everyone is in the same time zone – but once you get different continents involved, invariably people get confused. It’s easy to get writing to work uniformly left to right or uniformly right to left – but if you’ve got a mixture, it becomes really hard to keep track of. The diversity which makes humanity such an interesting species is the curse of computing.”