Blog

Reading 2021

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.

The low-light was undoubtedly Malcom Gladwell’s “Talking to Strangers.” A reasonable “long read” blog post but stretched very thin over an entire book.

For 2022 I have the same target as 2021. Will I do better this time? Watch this space…

Talking of which, what is the point of these posts? Are they reviews? Not really, they’re thoughts or recollections or highlights of reading the books. Some read more like reviews, others are tangents, things that reading the book made me think about or consider in a new light.

Blog

Pilot Error and Showdown

In one sense this was me trying to cheat my “twelve books in 2021” challenge. Does reading two short stories count as two books? Goodreads seems to think so…

But it wasn’t just a cheat. These are still stories that I did want to read. Dan Moren is a writer I’ve followed for a while, though entirely in his Mac-centric, technical writing at Six Colors1 and podcasting at Clockwise. The stories are both part of a bigger sci-fi-space-opera universe but work well stand-alone.

Of the two, I enjoyed “Pilot Error” the most. I didn’t see the twist coming, though looking at the remaining page-count I knew that either one was coming or that it was intended as a major cliff-hanger for the follow-up book.

As a short taster for the writing, the characters and the universe, these stories fit the bill. I’ve not managed to read a whole lot of fiction this last year or two, but I’ve added Moran’s books to my list.

If this sounds like your kind of thing, you can read them for free.

  1. As a Brit, that spelling kills me but I’ll stick with the official site name. ↩︎
Blog

Losing the Signal

I have a confession to make. I had a BlackBerry for a few months and I hated it. To be fair I was late to the party. By the time I used one, the iPhone had launched and and the BlackBerry was not the Cool Thing any more.

Nevertheless, a few years before that I remember seeing them all the time around the City and Canary Wharf. They had an impressive tactile quality, where were people continually touching them, scrolling the side-wheel or the spinning the little trackball on the later models. By the time I started using one, the hardware itself was still great but the software was incredibly dated.

Clearly there was something about the BlackBerry that was interesting. This book, “Losing the Signal,” is about the maker of the BlackBerry.

It’s a history going from the foundation of the company to roughly the resignation of the co-CEOs that had run the company for years. Since we all know how it ended, the simple chronological structure works well. The authors interviewed just about everyone on the record. They managed to get both the good and the bad out of those they talked to, making it neither a hagiography nor uncritical.

In the end, the story is one of hubris. Early on, it was a huge advantage to the company. Everyone else knew that mobile email was at best niche, at worst a waste of time. Everyone, of course, was wrong and RIM was right. But in 2007, when the iPhone launched, that hubris started to work against them.

Unlike rival handset makers, Lazaridis didn’t come to Barcelona armed with 4G prototypes, but with a physics lecture... Now he was going to explain to Verizon why they were wrong about 4G.

I’ve seen this behaviour before – from my own employer at times – the supplier telling the customer that they’re Doing It Wrong. They knew that the next generation of cellular technology wasn’t a big deal – the speed was unnecessary, the power consumption was a problem – knew that customers valued the security of the BlackBerry above the web browser of the iPhone or the App Store of Android. Only this time they were wrong.

I knew some of the story, having seen the devices and read articles, especially post-Android, post-iPhone, but it was good to read the whole history. The access the authors had to the key people is impressive and they made good use of it.

In the end, if you’re interested in the earliest successful smartphones, BlackBerry is the company to follow and this book is well worth reading.

Blog

Crisis? What Crisis?

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.

The book is in roughly chronological order, with occasional jumping around to make certain aspects make sense.

Despite being such relatively recent history, there are surprising volumes of material that are shocking, or at least uncomfortable. I know the name Enoch Powell and the phrase “rivers of blood,” of course, but even then the more detailed background is both depressing and familiar. The parallels with the modern anti-immigrant movement are obvious.

On the other hand, it made the rise of Margaret Thatcher more understandable to me. I’m not a fan of her politics but you can appreciate the desire to shake things up. Having said that, I thought her victory in the 1979 election was assured so it was fascinating to read that it wasn’t, and that had the election been called just a few months earlier things might have turned out differently.

Those looking for a change with Thatcher may not have realised what they were letting themselves in for. I guess I’ll have to read the next book about the Eighties to find out.

Looking back, the Seventies is often seen as a “lost” decade, which is why it’s nice that the book concludes with the upsides that we often don’t consider:

For most of the country, for most of the decade, times were really quite good. In retrospect, the 1970s can look like a period of comparative calm and stability. It was still possible for an average working-class family to live on a single wage, very few were required to work anti-social hours, and housing was affordable for most.

Almost by definition, I can’t say how complete the book is but I do get a much better feeling for the decade than I had before, which makes it worth the read.

Opinion

Ops is undervalued

I made the mistake of suggesting that there was a blog to be made from this tweet. This is that post.

People still underestimate the value in (Developer|Operator) Experience when building platforms and honestly it’s kinda shocking to me.

If you want to win mindshare you need to make your tools actually usable. If you don’t want to lose it you need the same.

First: I agree with the sentiment. Maybe not to the same extent as Danielle, but I fight the same battles in my day job. I wanted to say this now because, on reading the rest, you may think the opposite. What follows is an explanation of why this is a common situation. I don’t mean it as a justification.

In summary, making software work for ops teams is not a focus either for software companies or internal development teams because of at least three reasons:

  • It’s not a business driver
  • Ops are not the buyer
  • Engineering is run by developers

Naturally there are exceptions to these rules. Every company is different. These are observations, not rules.

Working at the “coal face” it’s easy to forget, but people don’t buy software. They buy a solution to a business problem1. These days, that solution is often software but you don’t buy a new product because it’s cool2.

A driver might be to get a report generated more quickly, or to provide a new service to paying customers, or to reduce the costs of some infrastructure3.

But, you argue, the ops team are the people who keep the system up and running. How can this new system generate reports or deliver a service if it’s not running reliably or has not been provisioned correctly?

You’d be right. Sadly, organisations are often not structured to recognise that fact. The IT teams tasked with making everything run smoothly are frequently in a completely different reporting hierarchy from “the business.” I put “the business” in quotes as I hear it described that way all the time, but it’s this us-versus-them philosophy that brings many issues, including how ops get sidelined4.

With “the business” and “ops” being in separate reporting structures, one or the other has to sign off on the purchase of new software (unless it goes way up the organisation) and that’s always going to be “the business.”

The buyers normally consult the ops team, but ultimately they’re going to put their own needs first. Objections that the ops team have will end up in the business case, but likely in an appendix that no one will ever read.

This makes no sense because, as we all know, most of the expense of a system occurs after go-live. But monitoring, management and deployment are not things at the top of mind of developers and business users.

But even in the IT organisation, the ops team frequently don’t get the attention they deserve either. Anecdotally, this is because IT leadership come from the development team. Their outlook on IT is therefore skewed towards making things rather than keeping them running. I see the same challenges for testing teams. Or, indeed, the lack of testing teams.

This lack of buy-in from the ops team is endemic. I see it in companies buying and using software. I see it in companies that make and sell software5.

At this point, what I would like to be able to do is say, “And the solution to this terrible problem is…” Sadly there is no easy answer. Saying “You should listen to your ops team” is both obvious and unhelpful. Making tools useful for the ops team to get mindshare is a good way to get your software on a shortlist but maybe not enough to clinch that sale.

  1. I’m talking here about software used in a business of course, but the difference between this and personal use isn’t as great as you might initially imagine. You buy a game to solve the “problem” of boredom. Very few people buy software because it’s software. ↩︎
  2. You might buy it because this, specific solution is cooler than the other options. ↩︎
  3. That is, even in the case where it’s the infrastructure that is being improved, the business case is not “make the ops team more efficient” but “make the cost of operations lower.” ↩︎
  4. There’s another blog in how toxic “the business” as a concept is. This isn’t that blog. ↩︎
  5. This is a chicken and egg problem. Do software companies fall into this trap because they’re run by developers? Or is it because they’re selling to companies who have already fallen into the trap? ↩︎
Blog

Little Book of Humanism

While there is nothing wrong with “The Little Book of Humanism,” it wasn’t for me. Some people need to see aphorisms or testimony about their chosen faith. If that’s you, if you’re a humanist, then this book fits the bill. Similarly, if you’re Humanism-curious, then this book might fill in some gaps in your knowledge.

None of the sections span more than a few pages and it’s filled with quotes and stories by people who were publicly Humanist or at least espoused the same values. The vignettes cover life from birth to death and everything in between. Some I’d heard of before, others were new to me. It’s longer than I was expecting, though it’s easy to dip in and out; there’s no need to read the whole thing beginning to end.

I don’t think I need these stories or quotes. This says more about me than the book. I was never religious, meaning I have no need to replace a sacred text. And I have never found other people’s testimony persuasive1. But if hearing about other people with a similar outlook gives you the warm fuzzies, or if you’re curious about what Humanism means, then this book might be what you’re looking for.

  1. I always found it odd that many believers go straight to testimony as a way to convince you that their particular brand of faith is the right one. Is it that the approach works or is it that people enjoy talking about themselves? ↩︎

Photography, opinions and other random ramblings by Stephen Darlington