On and off, I've tended to read quite a bit. So, I thought I'd put up some reviews of books as I read them. I am fully aware that they're really more about me than the books, so caveat lector. This page contains the most recent reads - if you want more, I recommend you go to the full index.
This was a birthday present to me, a book on the subject of video games design. Previously, I'd read A Theory of Fun for Game Design by Raph Koster, which was definitely a lot more theory than fun. This book is... the opposite.
It's a really concrete and practical book on game design. There are chapters on level design and characters and cutscenes etc. - all very practical and down-to-earth. Some of the things are pretty obvious patterns if you play a bunch of games and think about how they work, but the presentation is fun (and highly illustrated :) and thorough.
I don't intend to make video games (beyond the occasional foray into Pico-8 with my children), but sometimes it's interesting to read up on how to do things you don't intend to do. And, to be fair, my son loves it when he gets the chance to read it. I expect to find it dog-eared under his bed in a couple of weeks.
Grand summary - is it worth reading? I'd say so. Lot's of fun, not particularly hard work, and enjoyable and interesting.
Apparently I bought this at least 7 years ago, as I bought it along with The Prize (a doorstep about the history of the oil industry) and Lolita. These were all at the recommendation of a colleague, and I think it says something that I managed to get through the doorstep quite quickly, but took until now to finish this. I never got through Lolita.
Ignore the first half of the book, with run-of-the-mill logic/paradox puzzles. The second half is a fantastic introduction to combinatory logic, under the guise of puzzles about birds!
I'd stalled in a couple of previous attempts, when the trickier puzzles and subtleties unaddressed by the text started to pile up. This time around, I just wrote myself a solver to bypass the more tedious pencil-work, and pushed through the theoretical questions - which were often answered later in the book!
My workings are on github, along with some more in-depth thoughts on the book. The summary, though, is that this book is worth it if you're a fan of theoretical computer science, but not a hardcore expert.
Keith Devlin wrote one of my favourite maths books, so I was interested to see how he approached this subject. The Millennium problems are seven problems with a million dollar prize offered by the Clay Foundation. The level of difficulty in explaining them... varies significantly.
The early chapters deal with e.g. The Riemann hypothesis and P = NP, and it ends up with the Hodge conjecture. It's the usual kind of pop maths start-at-GCSE-level explanation. So, you'll be reintroduced to complex numbers yet again. By the time you get to the Hodge conjecture, which is genuinely difficult to explain, they've basically given up.
So, I'm at a bit of a loss with the book. It was effective at explaining easy things I understood, and not effective at explaining the things I didn't. After "Mathematics: The New Golden Age", it was a bit of a disappointment. Ah well.
I read "Why Buildings Fall Down" by the same author a decade ago. This is actually the better book!
It's the engineering of buildings, as described by an architect. The architect in question is actually pretty snooty about structural engineers, perhaps to counter for the fact that they're spending so much time talking about structural engineering questions. The book describes engineering principles, illustrated by famous buildings (such as the Eiffel tower and Brooklyn Bridge). Quite frankly, I found that fascinating.
It's also a book of its time. Written in 1980, it's surprising to see quite how much things have changed. You can see what the trendy things of the day were. Apparently the future of architecture was going to be plastic. And maybe inflated domes.
So between the retro-ness and the architect's need to be an insightful polymath (there's a chapter on the semiotics of structure!), there's a lot of amusement. Combined with learning all about construction materials, and how buildings carry static and dynamic loads... it's actually something of an awesome book. Better than the sequel. :)
I want to get better at public speaking. I'm taking a couple of approaches. One is to join Toastmasters, which is a freakily American public speaking club, to get the practice in (there's a branch at work). The other is to read up and get some theory.
My boss at the time recommended a video of a talk by Cara Hale Alter, I watched it, and I bought the book. The book's all about how to present in such a way that you achieve, well, credibility. So, it covers standard "how to present" skills, but with an emphasis on those things that make you clear and authoritative. Quite a lot of "stand up straight and speak clearly", to be honest. It's a short book, and not terribly dense.
On the other hand, it does the job - the advice provides nicely concrete things to work on. Videoing yourself is the core to the book's way of improving yourself, and I've been doing that. Learning how I look when presenting is both painfully unpleasant and very useful for learning with!
A younger version of me would be very wary of faking-'til-you-make-it authoritativeness in this way. Current me is happy enough that I'm not much worse at making it up as I go along compared to everyone else, and that my audience deserves to get my ideas explained clearly and in a non-distracting way. I'd happily send my younger self a copy of this book.
Another book from work's book club.
This book is a letter from black American journalist Ta-Nehisi Coates to his son. It talks about his life and the injustice of America to black people. It does so viscerally - makes it clear that in the end, it's about violence, about permanent fear that the police will kill you with impunity.
It's a journey through Coates's life, powerfully told. It covers the events of his life, and his struggle to come up with a coherent philosophy. It made me think about things from a different angle. He highlights how strange it is that America builds up MLK as a hero so much, sets up as role models people who are beaten and killed rather than fight back against violence with violence. How convenient this kind of message is to those in positions of privilege!
It's not a terribly hopeful book. It doesn't give up, it wants to fight on, but victory is not near.
Another pocket book on birds, and a Christmas present to boot. Compared to the Dorling Kindersley book I bought previously, it's smaller and thicker, and does a bird-a-page approach, roughly organised by some grouping of birds I don't really understand. It's pretty comprehensive, or at least I know there are a bunch of birds I'm never going to see in here. Is it any good? What do I know? I'm no expert. :) I like it, though.
This book was featured in my workplace's bias-busting book group, and deals with talking about race. It (unsurprisingly) is American-centric, but interesting nonetheless in how to talk about a difficult subject.
The main idea is that race is the elephant in the room that many white Americans fear to discuss. The primary approach is "color-blindness" - by trying hard to ignore race, the problem goes away. Unfortunately, the problem hasn't gone away, and claims that you can't see race make those problems impossible to discuss.
Part of this is that being white is a race, is a culture. If you're white, it doesn't mean you have no race, it means you are in the socially-dominanting race, and are seeing the world through a lens that is sufficiently predominant you don't know it's there. Acknowledging that you are white is fine as long as you can build up a racial identity that contains understanding of history and privelege, is not ignorant of other races, and actively helps people in disadvantaged minorities - as there are so many structural disasdvantages (let alone overt racists!), doing nothing (or being neutral/"color blind") is insufficient.
Unsurprisingly for a book on "race talk", it also discusses how to talk about race. The key point I'm taking away is that experience of race is subjective - as you can't live in someone else's skin, you should believe their experiences and acknowledge their emotions, and by approaching it that way you can learn to understand the world through others' eyes.
This is all, of course, a dramatic over-simplification of a whole book. There's plenty of subtlety and detail.
Indeed, the book's got a fairly academic tone, and is hard work, consisting of pretty dry, slow material. And the human interest examples are generally of people having a bad time due to their race, or having bad and dispiriting discussions about race. Furthermore, the title of the book makes it sound like it's either neo-fascism or incredibly right-on, which means I didn't dare to read it in public for fear of worrying people and/or drawing out the loonies. All of which meant I read this book incredibly slowly, and I think this has really slowed down my overall reading rate, with a big queue of books building up after it.
I learnt less from the book than I had hoped (especially considering the material's US-centricism), but it was interesting nonetheless. Would I recommend it? Not really, unless you're a masochist, or have particularly strong needs or interests in the area.
A pocket-sized Dorling Kindersley book in association with the RSPB, it's subtitled "The simplest ID guide ever", which gives you an idea of the level we're talking about. Lots of nice, colourful pictures.
Whyyyyy? Birds are these things I've never understood. I see birds fly around, but they're just birds, like trees are trees, and rocks are rocks. Caroline knows all about birds, and would occasionally say "That's an X", and I'd nod and know nothing. I thought I'd change that, and learn a little, and this is my starting point.
For that purpose, as a really basic introduction, it's great. It still leaves me wanting to know more, and it's not a huge amount more than nice, big, bright pictures (unlike the actual birds which are small and far away and generally difficult to identify - bah!), but that's still a great introduction. Did I mention the book was on special offer and really cheap?
Also, it's a convenient size. I carry it in my work bag, just in case I see something unusual on my commute (for me, almost anything is unusual, and seeing a jay was really cool).
So, I like it.
I visited Boston with work, and while I was there I took a look around MIT and Harvard. I picked this up at the MIT Museum (which is well worth visiting!). It is a book about MIT "hacks", which are generally clever re-decorations of part of the campus. The hacks are a combination of demonstrating engineering aptitude, subversion, and effectively student ownership of the campus environment. They're unofficial creativity, and I find it fascinating how books like this show the university is well in control of its own mythos. Oh, and the hacks are quite fun! A nice souvenir.
Oh my, it's been far too long since I put up a book review. And so few books I've read. Work is... keeping me busy. And I'm slowly plodding through a book that I'm not finding terribly engaging, which has slowed me down somewhat.
While reading that book, I've read this book. It's a couple of short stories, both the book versions of films. They're perfectly fine to read, I guess. The film of The Third Man is, er, extremely well regarded. The book is... fine.
It's a nice, quick read. I enjoy Greene, and they're pleasant enough, not much more.
I haven't read any Austen in ages, so when my wife re-read Emma it seemed a good opportunity for me to read it at the same time. It's good. It's long. It's annoyingly long, because it's also good, so you can't properly begrudge the excessive length.
Emma herself is a great heroine, because she's basically silly and annoying, but not excessively so, and works out her flaws over the course of the book. Embarassingly, having watched Clueless before reading Emma gave me a much better understanding of Miss Woodhouse's character - the parallels are excellent.
As I said, it's good. I can't really judge it much better than that, as right now I have a sore throat and am really irritable. Some of the sentences test the limits of my comprehension in this fuzz, but it's still an enjoyable read.
I've been meaning to read this book for some time now, and having got sufficiently nostalgic about Haskell, I finally did. "Real World Haskell" is apparently one of those oxymorons, like "ML for the Working Programmer", but I don't care. I still like Haskell.
This is not a short book. There's about 600 pages of proper content. It took a decent number of commutes for me to read (don't worry, I take public transport :p ).
I was intrigued as to how much theory they'd use, and how they would introduce the more algebraic structures. I feel the start of the book is pretty darn good, building up slowly, so that when you hit monads, around page 300, you've already seen the pattern a few time, and then you get the general version of it.
The code examples didn't convince me in a few cases - I was suspicious of some of the corner cases, and the barcode recognition code just seemed messy to me. Still, they helped move things along.
Once monads are introduced, a few extra topics like monad transformers and error handling are presented. I'd never really played with "ap" before, or studied MonadPlus, so I got to learn some new tricks, as well as seeing various style points written down that I'd only previously inferred. This was pretty much the high point of the book.
Then, from around page 450, the "real world" kicks in. Various programs introducing real-world interaction are given, and sadly this is pretty dull. Databases, web clients, GUIs, meh. Why do all books with network programming examples always have to re-explain TCP vs. UDP? There are some cool bits mixed in. "Concurrent and Multicore Programming" is pretty interesting, as is "Profiling and Optimisation". The book ends on a reasonably fun note with "Software Transactional Memory".
A few of my pet favourite subjects were missing - for example, no untied data types. Mutable arrays are hidden carefully in the Bloom Filter example chapter, without a sensible index entry. Indeed, many of the chapters feel ordered arbitrarily, sometimes using functions which are only described chapters later. There's no category theory, which I think is a good thing for a book like this.
Then there's the errata. I felt the start of the book was pretty good. By about halfway, I think everyone was tired out. I started spotting sufficiently many bugs that I started reading the book with the errata web page open. "Yep, thought that was a mistake."
A six-hundred-plus page book is a massive undertaking, especially if you're trying to produce nice code examples and cover a bunch of platforms, and write things to only use the features you've described so far. I'm still a bit disappointed. I must admit, there's a good book on Haskell in there somewhere, covered in a layer of errors and flab. Is it good? I don't begrudge the time I spent reading it, but I wish it had a little more confidence and didn't have to spend quite so much time and space justifying its "real world" nature.
I'm finally working through a few books by "famous authors who are influences on William Gibson". William Burroughs was a bit of a disaster. Ballard looked potentially tricky, so I went for one of his more conventional novels.
This book is not surreal, unlike much of his other work. In fact, it's rather more hyperreal than surreal. It's a ray-traced pile of chrome balls on a checkerboard versus the complexity of reality. A simplified model of the world to try an idea.
Cocaine Nights is ostensibly a whodunnit, set in the ex-pat community on the Costa del Sol. In reality, it's a musing on the nature of crime, and the environments of retirement communities. It makes me think of a generation-earlier version of Chuck Palahniuk - indeed there are thematic similarities to Fight Club.
For all that, it's a rather staid, repetitive novel. Perhaps this is a commentary on those timeless retirement communities where nothing changes. The crime involved has an airless quality, colour drained by the sun. Much of the repetition can be laid at the feet of the protagonist, who is fascinated by the underworld. It seems that it's this character's voice, rather than the author, who is bludgeoning the message home rather artlessly.
It's a funny book. Not quite the whodunnit it suggests, unsubtle in its motives and message but restrained in its detail. The writing is enjoyable and brings in a good sense of place. I feel I now need to read a bit more Ballard to separate out the novel from the author.
I've been holding off on reviewing this for a while. I thought What Got You Here Won't Get You There was a bit annoying. This is a whole different ball game.
Ricardo Semler is the owner of a reasonably large company (Semco). He inherited a reasonably successful company from his father, changed it massively and grew it. This book is about his management style.
His management style is, in his words, "democratic", and in the view of someone like me "anarchic". Well, it is a democracy, but rather more a direct democracy of everyone involved. Power is delegated, but there's also no centralisation of a wider strategic direction. There are good parts to this, in that people on the front line have control to make things work and do things right. There are bad things, such as when a firm that does environmental assessments got clobbered for breaking environmental laws - laws they knew they were breaking, but couldn't actually prioritise fixing.
This is perhaps the strength and weakness of the company's approach: It centres around managing by not managing - on any tricky issue which divides the company, the default action is to do nothing. I'll admit this is an often-effective and underused technique in most companies - most places feel they must make some action, and try to do too many things, and are ineffective at "wait and see". However, I think "do nothing" should be an active decision, rather than an incidental side-effect of a political log-jams.
It seems that the Semco empire is highly siloed. If every decision has to be made across the entire group affected, those groups can't grow too large. Everyone runs their own infrastructure. The global inefficiencies are weighed against local agility. It seems the business models they've chosen work like this, although I don't think this model can scale for everything. Having worked at both a siloed company and a company with large and effective horizontal projects, I now appreciate what effective strategic steering can do.
And at the top of it all is Ricardo Semler. He does rather go on a bit about how his job is very nice, and largely involves taking himself out of the loop and going off having a nice time around the world. I'm not quite sure what the message is, here. Being the capital owner of a large stake of a successful business is nice, perhaps?
I don't disagree with everything in the book. However, it takes things to extremes for reasons that are unfathomable to me. It's like a annoying, hyperbolic person arguing for something you believe in a way that makes you feel less convinced afterwards.
As for the book itself, it's quite tedious. Perhaps the book is a model of Semco? It's pointlessly long, rambling, doesn't particularly make any conclusions and for all that is apparently very successful in the marketplace.
More accurately, "What Didn't Stop You Getting Here Will Stop You Getting There". The core thesis of the book is that people limit their success by holding onto various destructive behaviours. As they've been successful in the past, they don't realise that these behaviours are a blocker on further progress, and may think they're part of their success.
There are 20-odd specific behaviours listed in the book, but they can be boiled down to "Don't be self-centred and arrogant". As people get more successful and rise up an organisation, they both need to get other people doing the work and learning new skills themselves. If they keep taking on the work themselves and shooting everyone else down, this doesn't happen. Leadership needs teamwork.
The other part of the book is about how to change. It's about gathering feedback and using it. This is where I really start to disagree with it, although the disagreement extends to the behaviours, too. Basically, the suggestion is "When someone says something to you, nod and smile and thank them and don't say anything". I disagree with this. Sure, when you have a senior role people take your opinion seriously, but gentle, positive and constructive feedback helps others grow, and if someone has some constructive feedback for you - well, you should engage with it. Not deny it, certainly, but at least dig in and truly understand what they're saying.
The higher you go, the more gently you need to steer and provide feedback, and perhaps this is really my main problem with the book. It's for executives - pretty much people trying to break through to being CEO of a large company, and being held back by their bad habits. Perhaps it's just a bit lost on me. Indeed, given it's a bestseller, I suspect more people have bought it than are actually in its true target market.
Burroughs is one of those authors that other authors keep refering to, so I thought I should go read some, and, well, this is his most famous book.
The issue I have is that Naked Lunch is uninteresting, unintelligible and unpleasant. If it weren't for all of those, I could probably cope. A not-nice subject is discussed in not-nice terms. However, those terms are also tied into the slang and culture of a distant decade. I'm sure I'd find modern junkie culture pretty much unintelligible too, but this is... rather worse.
And, at the end of it all, I don't really care. There are very few books I've given up on (I read all of Gravity's Rainbow, and I still have no idea why), but this is one.
This is an extremely deliberate book on management and leadership. As in, it's clearly been constructed to fit squarely in the genre. From the foreword by Stephen "7 Habits" Covey through to the end of chapter points to think about and suggested exercises for your next off-site, the author clearly knows the genre.
The book is about how the author, as the captain of a nuclear-powered submarine, empowered his crew and managed to bring it from being one of the worst-performing boats to one of the best. While it's largely narrative-driven, the leadership techniques are literally WRITTEN OUT IN CAPS so that you can't miss them!
Part of what makes this book so great is that it's clearly not about a heroic and intuitive leader changing things around through native charisma. Throughout the book, the author namedrops all the management books he's read, giving the reader a chance to find out more, but also demonstrating that this kind of leadership can be achieved through study and thought, not just making inspiring speeches.
Moreover, by using concrete examples of what happened, not only is a dry subject given human interest, but the techniques of leadership are illustrated with practical examples. This is why the book can freely reference other books, because it adds something more - insight into the practical applications.
The target audience seems to be managers of managers, with the aim of creating an organisation where everyone is working towards the next level. However, the context of a nuclear submarine is interesting to me as an SRE. Admittedly, if I get my day job wrong I'm unlikely to die in a horrible way, stuck inside an enclosed metal tube filled with nuclear material and explosives far below the sea surface. On the other hand, we deal with incidents under pressure and have to deal with complex systems. We train and practice and optimise our responses. It makes an interesting comparison.
I really rather enjoyed this. Recommended.
A rather less interesting but perhaps more accurate title for this book would be "Qualitative analysis of simple differential equations with practical examples". Put bluntly, this is a boring book.
Examples are things like thermostats, and fish stocks, and capital growth, and epidemics. Things you can model as differential equations. However, this book is about the qualitative analysis of such equations - the modes the system can fall into. It never actually says it, but it's aiming to be approximately right, rather than precisely wrong.
It is, basically, quite boring. Perhaps reasonably worthy. I don't know why it's so boring - it's not a long book, but maybe it's pretty slow despite that. It does have some good insights, but it makes them seem... boring.
For example, in many dynamic systems, we directly attack one variable, rather than try to adjust the system to produce the result we want. To give a topical example, Donald Trump is not actually the problem, he is the result of a system that enabled him to get where he is, and the problem needs to be attacked at a lower level, ideally at a place with higher leverage.
By taking such a structured, academic approach to Systems, you really do end up with a primer on the subject of systems. However, it's neither as amusing, nor as fundamentally insightful as the insanity that is Systemantics (aka The Systems Bible).
A lovely, vitriolic Christmas present from my wife. :)
Right now, Charlie Brooker is probably best-known for Black Mirror, which I still haven't watched. However, he's had a long history of writing for the Guardian, reviewing the week's TV and complaining about the idiocy of the world (these two things going fairly close in hand. His writing is, unsurprisingly, angry and world-weary. There's a lot of reviewing Big Brother.
The writing in question was circa 2007, so it's interesting to see how things have changed. He was complaining about the general state of the world, and in particular regularly complaining about the Bush presidency - if only he could have seen where we are now. He'd have been horrified and not terribly surprised. Indeed, the version of Charlie Brooker who didn't time travel and took the long route from 2007 to now seems to be horrified and not terribly surprised.
Seeing all those extended similes of hatred together is a little wearing, but you also see the patterns of his personality, and occasional surprises. He's a fan of Doctor Who, but generally disappointed by sci-fi which doesn't challenge - cue Black Mirror, I guess. And he went to Glastonbury with an ex-Big Brother contestant who became his friend. Strange world.
Debugging Teams is a guide to team management and leadership for those software engineer types who don't really want to do that stuff. I quite like doing that stuff, so I guess this isn't really intended for me, but it's a fun, short (150 page) read. It's not even 150 real pages - it's got a bunch of cartoony illustrations in there that don't really add anything, perhaps because reading words is hard, or you like to be treated like a baby, or they wanted to pad out a really short book.
On the other hand, the text itself has no filler. Unlike many management books, as well as having a main thesis, it's packed with specific advice, examples and suggestions, so that it's actually relatively dense. The main idea is that even if you don't want to do leadership stuff, you're still better off doing it than leaving it to chance and dealing with the fall out; a stitch in time saves nine. The core of their advice is to encourage a positive team culture, specifically one centred around Humility, Respect and Trust - which allows people to be open and honest and learn things and contribute without feeling under fire.
The authors have management experience from both open source (specifically Subversion) and Google. Indeed, a subtitle of this book could have been "How engineering management works (or is supposed to) at Google". Reading this book as a manager at Google, this part was slightly preaching to the choir, but good to refresh. The OSS side was... interesting. Now that we have a large number of significant, long-running OSS projects, culture in open source projects is being recognised as a big thing. In the short term, a few bright people can make a project, but over the long run, with contributor turnover, it's all about having a culture that encourages people to join and develop. This book is a great resource for people trying to work out how to run such a project.
To change tack for a moment, recently I went to see "The Book of Mormon" with my wife, on her birthday. In effect, the message is that a positive and helpful culture can more than make up for a lack of... rigorous rationality. This seems to mirror the message of the book - rather than try to have a perfect crystal of software, go for a positive community of practical people delivering something people want to use, and maybe you'll actually get some success.
Recommended if you want to know how Google engineering management is supposed to work, or if you want to make a piece of OSS people want to work on.
The third in the Ancillary Blah series, and the culmination of the trilogy. Also, in my opinion, a bit disappointing. Things kinda get sorted out to a degree, with an appropriately don't-fix-the-entire-universe ending. The disappointment comes from just not exploring the possibilities available. The Presger are involved, relatively boringly. A bunch of spare AIs turn up and nothing's really done with them. That Dyson sphere from the previous book just isn't mentioned. Instead, there's a lot of counselling for young and emotionally distressed officers. Er, yay? The previous books didn't exactly avoid this, but I wasn't desperately hoping for more.
The other Dirk Gently book!
This one wanders quite firmly over to more of a fantasy genre, although the previous book lurked on the edge of that space. I didn't enjoy it quite as much. The connectedness runs through this book as a stronger thread than in the last book. It's enjoyable for the most part, but I felt it made for a let-down ending: Dirk fails to (intentionally) do anything helpful, and then connectedness sorts it out at the end anyway. I like the fridge, though.
Now that I'm back in management, I thought I should catch up on a few more management books. Google's management philosophy is (or was) allegedly based on this book, so I thought it was worth a read.
This book is the missing manual for being a manager.
It's not about Leadership or abstract stuff. It's about the nitty-gritty of what management's about, and how to do it. Grove's model is that the output of a manager is the work their team does, which sounds simple but does force clarity around a fairly hand-wavy area. It's about results.
From there, it covers lots of useful stuff, especially around meetings, one-to-ones, feedback and appraisals. Grove is clearly a workaholic and makes no bones about it - but it's really worked for him. :p
This is a book from the early '80s. It's based around the experiences of physically manufacturing stuff. E-mail is not a given. So, there are things that do not translate to the modern environment. They're kinda interesting historically, but they're not entirely useless since all the suggestions are grounded in principles, so that they can be extrapolated to the modern high-tech workplace.
Is it good? Yes. It's pretty short, but very solid and practical, and makes a nice contrast to most other hand-wavy management books. I don't want to take everything in it verbatim, but it's flexible enough to work. I wish I'd had it when I started managing.
It's been soooo long since I last read this. It really does deserve a re-read.
In my teens, I preferred the (early) Hitch-hiker books. Now, I think these are my preference. They're not quite as acidic as the H2G2 books (which passed me by a bit at the time), and the structure is just more fun. The setting's familiar (I think the last time I read this was before I went to Cambridge), and it's very weird to think of the protagonists now being younger than me (definitely not the case last time!).
It captures the feel of '80s tech wonderfully, with Richard's piles of tech, Silicon Fen entrepreneurs, chaos theory and all the rest. It could be a late Infocom or Magnetic Scrolls text adventure.
So, for me, it's both warmly nostalgic and just an enjoyably structured Adams story. We lost him far too early.