Auto Ads by Adsense

Booking.com

Monday, December 13, 2021

Review: Principles

 I was assigned Principles as part of an onboarding reading. I'd never heard of Ray Dalio or Bridgewater Associates before, and I was dubious about yet another business book. But I gave it a shot anyway.

The first 2/3rds of the book were irritating. I generally agreed with Dalio that the most important thing in the world was to face reality, and that you need to iterate constantly towards your understanding of reality and to challenge your view. But I got very annoyed by his choice of words. For instance, he used "evolve" when he meant "improvement." This is a pet peeve of mine, since evolution doesn't actually have any direction or aim. I was also very annoyed by various statements about how the system he found himself in was a good one. I certainly don't think that viruses or mosquitoes do any good. We just have to live with them. I suppose if you become mega rich like Ray Dalio did, you can't help but believe that the universe you live in must be the best of all possible worlds, even if objective reality of the majority of people living around you says otherwise.

The last 3rd of the book ("Work Principles") were however a treasure trove of great ideas and deep insight. For instance, here's a brilliant section on why you need to talk to your skip-level reports, a major mistake many directors (new and experienced) make:

Probe to the level below the people who report to you. You can’t understand how the person who reports to you manages others unless you know their direct reports and can observe how they behave. f. Have the people who report to the people who report to you feel free to escalate their problems to you. This is a great and useful form of upward accountability. g. Don’t assume that people’s answers are correct. People’s answers could be erroneous theories or spin, so you need to occasionally double-check them, especially when they sound questionable. Some managers are reluctant to do this, feeling it is the equivalent of saying they don’t trust their people. These managers need to understand that this process is how trust is earned or lost. Your people will learn to be much more accurate in what they tell you if they understand this (page 459)

Here's another one about how to properly run a post-mortem:

 Avoid the anonymous “we” and “they,” because they mask personal responsibility. Things don’t just happen by themselves—they happen because specific people did or didn’t do specific things. Don’t undermine personal accountability with vagueness. Instead of the passive generalization or the royal “we,” attribute specific actions to specific people: “Harry didn’t handle this well.” Also avoid “We should . . .” or “We are . . .” and so on. Since individuals are the most important building blocks of any organization and since individuals are responsible for the ways things are done, mistakes must be connected to those individuals by name. Someone created the procedure that went wrong or made the faulty decision. Glossing over that can only slow progress toward improvement. (Page 479)

 Use “public hangings” to deter bad behavior. No matter how carefully you design your controls and how rigorously you enforce them, malicious and grossly negligent people will sometimes find a way around them. So when you catch someone violating your rules and controls, make sure that everybody sees the consequences. (Page 514)

The book has a ton of common sense, and ultimately, if I'd summarize the theme of the book, it's that the management team need to approach an organization the way an engineer approaches code:

 Great managers are not philosophers, entertainers, doers, or artists. They are engineers. They see their organizations as machines and work assiduously to maintain and improve them. They create process-flow diagrams to show how the machine works and to evaluate its design. They build metrics to light up how well each of the individual parts of the machine (most importantly, the people) and the machine as a whole are working. And they tinker constantly with its designs and its people to make both better. They don’t do this randomly. They do it systematically, always keeping the cause-and-effect relationships in mind. (Page 451)

You will note that many management books aspire to inculcate this sort of thinking. One good one, for instance, is the Fifth Discipline. I loved the Beer Game as described in that book, because it made a big deal out of how long feedback cycles derail non-systematic thinking. But the rest of the book didn't cover the practical details of how to build a learning organization, whereas Dalio's book does.

Dalio claims that one key approach that makes Bridgewater different, is that it makes its potential employees take a personality test. The resultant attributes are placed together with your track record to create a personnel summary (I imagine this to be something like a D&D character sheet). Then, when you need a team to do X, instead of randomly grabbing people who happen to be available, you can search through your employee database to find the best matches in terms of personality and track record, much like a team of D&D players might say, "We need a cleric, a bard, 2 fighters, and a wizard."

There's also an emphasis on "believability weighted decisions." The idea is that when making a decision, you want the people with the highest believability about that domain. Dalio claims that the believability is based on 2 principles: (1) having done the task (or similar tasks) at least 3 times before, and (2) being able to explain how and why the decision should be made. This is a nice balance between the dummy "democratic voting approach" or the even more dummy "I'm your boss so I'm going to call this shot for you" approach.

I tried the personality test, and got some results. Unfortunately, it still reads a little bit like a horoscope to me --- too generic and not generally all that interesting.

Nevertheless, I really thought the last 3rd of this book more than paid for itself in time spent reading it. It's in a far better class than books like Beyond Entrepreneurship or The Making of a Manager. Your time will be much better spent reading this book instead of any of those.

Highly recommended.


Friday, December 10, 2021

November 23rd: Carlisle Bay to Green Island

 I woke up at 6am, the latest I would wake up for the rest of the trip. We made coffee and breakfast, and weighed anchor, and started heading over to English Harbor via motor into a headwind. Arriving there, we identified the Pillars of Hercules, marked in many locations for good snorkeling, pulled in around the point, and anchor'd as close to the reefs as I dared, letting out about 20 meters of chain in 2.5 meters of sand. The snorkeling was much better than at Carlisle Bay, with lots to look at.

Boen's snorkeling equipment had been fixed, and he was now very good at snorkeling. The difference in just a couple of sessions was nothing short of astonishing. 



When we were all done, we knew we had to visit tank bay to reprovision the boat, as our provisioning had been incomplete two days ago, and we knew now what we needed. Deli meat, fruits, more bread, more eggs, and most important of all, chocolate! But first, we visited English habor (by accident), and found the bakery that Niniane had talked about (she'd stayed in English Habor before joining us at Jolly Habor), which was open and ate meat pies and other delicacies before we found our way to tank bay.
Tank Bay's supermarket was conveniently situated right on the water with a convenient dinghy dock. We purchased everything we needed, and then headed back to the boat for a quick lunch before driving the dinghy back to English Harbor to visit the old fort.

Doing the hike in the afternoon proved to be a mistake. It was hot, though we brought cold water in insulated containers, and the one mile hike was fortunately short enough that it wasn't a problem.

The view of the bay and water was great, though, and on the way back we saw not one, but two goats!
After the hike was over, we dingh'd back to the Chinook, and there realized that at 2pm, we could keep going and get a head start on Barbuda one day early. We hoisted anchor, headed back out, and headed East. motoring under full power, we realized that the outboard motor from the tender would hit the water and bounce back up, which was not good. A reduction of speed to 5 knots solved the problem, but we knew we would have to solve that sooner or later. Rounding the South East corner of Antigua at St James Bay, we raised the sails and that took care of the tender's problem.

A flotilla of 3 boats passed us, motor sailing. The wind was light, giving us no more than 3-4 knots, but anything was better than listening to an internal combustion diesel engine, so we were more than happy to sail into Green Bay, where we pulled pulled into a Bay of what looked like a flotilla of 20 sail boats and a couple of power yachts. Taking advantage of our shallow draft, we pulled deep into the Bay, well ahead of other boats, dropped anchor, and snugged it up, taking only one final swim to check on the anchor before settling in for the evening.

We were going to sail to Barbuda the next day, and I was excited about it!

Thursday, December 09, 2021

Review: How Magicians Think

 I'm admitted a snob for the written work, but How Magicians Think managed to get me to watch a few youtube videos, which is an amazing accomplishment. The book is about stage and close up magic, and reveals to me several things about magicians that I'd never known or thought about before.

The book is structured as a series of short chapters, each of which is only a few pages long and focuses on one item. Yet there are themes that span the entire book. One big theme is how much time a magician spends practicing his shows. At one point he quotes another magician saying, "In the time I spent learning to do this trick I could have been a doctor." That develops into several other themes, such as how while other professions might be openly bragging about how hard they work to achieve their effects, no magician can ever do so. The entire point of the practice is to make the motions effortless and invisible, so you cannot draw attention to that effort. But Joshua Jay describes grueling hours in front of a magician's mirror, as well as time spent practicing in the dark.

Another interesting theme is that of presentation. The perfect presentation is actually boring. The important piece that he emphasizes is that you have to have a narrative that fits the trick you're trying to present, and that technical perfection is actually not as important as the narrative. This got me to watch his stint on "Fool Us", which was great.

Jay's admiration of other magicians is also awesome. Through this, he got me to watch more videos, such as Pierric's 2015 FISM performance, as well as Penn and Teller's Cup and Ball. Even with the tricks in full view, the latter showed me how smooth and how practiced a magician has to be. Then I finally got around to watching Shin Lim and that guy was amazing too!

There's a series of articles about visits to other magicians' homes, as well as to the magic castle. Every article was worth reading, and I thoroughly enjoyed following up on the names he mentioned in the book. This book got me to watch way more magic videos than I ever thought I would. Highly recommended.

Wednesday, December 08, 2021

November 22nd: Jolly Harbor to Carlisle Bay

 We woke up at 7:00am, made coffee, and got everything ready to go. To my surprise, Mario showed up precisely at 8:00am to do a chart briefing. He started by asking us what we wanted, and we told him our constraints about having to do a PCR test on Friday but still wanting to go to Barbuda. Mario proposed we did a loop around Antigua counter-clockwise, heading south to English Habour to pick up final provisions, and then doing a 5am sail to Barbuda under favorable conditions. Our past trips to the Caribbean have featured consistent wind, so I didn't even think to ask for a wind check, which might have made me change my plans.

After that, we got a technical briefing, covering the ship systems. The ship had a water-maker, and even better, one that didn't require constant monitoring. The boat was in very good shape, though the main door wouldn't close. That would have been a problem if we were doing an ocean crossing, but for Caribbean cruising, they just tied the door open. I finished off the paperwork and reminded Ashley that I'd ordered a paddleboard the night before. Niniane and Bowen both borrowed fins from the charter company. The maintenance chief took me to their workshop, where I was shown a selection of very beaten up paddleboards, one of which looked actively dangerous. While walking there he said to me, "Are you Chinese? I've seen Chinese in Antigua, but you'd be our first Chinese boat Captain!" I told him that I was Singaporean, and that satisfied him. After more scavenging, we picked out a paddleboard that was in the least bad shape, and I took a picture and showed it to Ashley in the office when finalizing the checkout. She looked at it in horror and declared that the paddleboard rental was free!

To my surprise, by 11:00am everything was ready to go, including the laundry that I had dropped off at 8:30am. Unlike many charter companies who would drive off the slip for you before handing you the wheel, Dream Yacht Charters chose to give me the wheel, and some minor instructions and then just untied all the lines and bade us on the way. 

Motoring out of Jolly Harbor, as soon as we were clear we put up the sails, we were so eager. Arturo and I gave Niniane some instruction about raising the main halyard and unfurling the jib and soon we were off. It didn't take more than half an hour, however, before we reached Johnson point, and in light winds the boat started coming about by itself and in our jet-lagged state we couldn't quite come about fast enough to regain forward momentum, so we furled and lowered the sails, turned on the engine, and anchor'd for our first snorkel.

Johnson point was unremarkable and not really worth a stop except that everyone was hungry and we wanted lunch. But any snorkel in the Caribbean is a good one, and gave us a chance to shake out our gear. The warm water made me realize how much I missed sailing here, though by the time we were all done it was 3:00pm and our chances of making another stop before heading over to Carlisle Bay was gone.

We motor'd all the way to Carlisle Bay into a headwind, foregoing sails as advised by Mario, and once there went deep into the bay to anchor, as was my wont, for that offered the best shelter. This would turn out to be a mistake later, as we discovered that the resort there had an ultra-loud concert every night, going well past the 11pm curfew. That explained why many boats were parked much further out in the bay --- wise captains will take note if they value their sleep!

We quickly started our next snorkel, given that sunset was at 5:30pm. This was Boen's first sailing trip after he'd learned how to swim, so we had to work out what was wrong with his snorkel: turned out that the mouthpiece had been broken by chewing too hard on it! Fortunately, I'd brought other snorkels that he could use, and swapping out one for another with a good mouthpiece did the trick.


Niniane got lost for a bit in the water, surfacing near another Catamaran that looked just like ours. Fortunately, she made it back to our boat before sundown, and we all got to enjoy the glorious Antigua sunset, after which we had a pizza dinner.


The boat had a watermaker, but we discovered at this point that it was very slow, producing about 3% of the boat's tank capacity every hour. We'd left port with only 80% of the tanks full, and this was a very expensive way of getting water, by translating diesel into freshwater. It did mean we wouldn't have to spend time tying up to fuel docks in order to get fresh water, which we would have had to do at least a couple of times on this trip, assuming that there were even service stations available. We all went to bed early, hoping the sun exposure would have freed us from jet-lag.


Tuesday, December 07, 2021

November 20-21: Prologue: San Francisco, California to Jolly Habor, Antigua

 We'd originally planned the trip to Antigua for Spring break of 2020, but with COVID19 outbreak at that time, everything got cancelled. There was a ton of miscommunication between our yacht charter company, our yacht broker, and AirCanada. First of all, Dream Yacht Charter thought we were rescheduling for Thanksgiving 2020 instead of 2021, then after (with some expense) we got it straightened out, AirCanada rescheduled our flights (we were intended to arrive on Saturday, but we got rescheduled to Sunday). Fortunately, our sleepaboard had been scheduled on Sunday anyway, so all this meant was that we had to spend an extra night in Toronto in each direction while at the same time not having to spend any nights in hotels in Antigua.

Joining us this time was Arturo (who was flying to Antigua via Miami) and Niniane, who was going on her first sailing trip and was already situated in Puerto Rico and had to scramble at the last minute to find flights to Antigua when Mark Brody discovered he suddenly couldn't make the trip.

We got up at 4:45am, got into our Lyft ride, and made it to the airport and through security without major hassle, and an uneventful flight which got us into Toronto at 2:45pm. Since we were staying overnight, we had to exit, use Switch Health for another round of PCR tests, and then piled into a rental car (which was cheaper than a round trip Lyft ride to dinner) and drove to the hotel, where the receptionist was very surprised to see vaccine cards even for our kids (they were only partially vaccinated, so did not qualify for the PCR test exemption).


Bea was at Niantic but left earlier in the year before we had a chance to work together. Since she was in Toronto and was a foodie (her food pictures were amazing), we asked her to pick a restaurant and after we left our lugguage at the hotel, we drove to Zukkushi. I've heard a lot of people complain about Bay Area traffic, but Toronto's traffic was if anything even worse. It took us a good hour to get to downtown, and once there we had several minutes to walk around the neighborhood before meeting Bea for a scrumptious meal, where she was surprisingly not terrified by Bowen and Boen, who put on quite a show for her.


The next day we got onto the flight to Antigua, which was on a small plane that didn't have screens but had wifi which you could use to access onboard content. We managed to watch several movies we'd missed including Black Widow, Luca, and Thor Ragnarok. Arriving at Antigua, our PCR certificates got checked and then we were at Jolly Habor in an hour. It didn't take long to find the dock, where someone told me I was clearly there for the Chinook.

The Chinook was a Fontaine Pajot Astrea 42 sailing Catamaran in an owner's configuration, which is a complete waste of space with the starboard side of the boat filled with an owner's suite with an extra large bathroom. There was fortunately a V-berth in front for crew, so no one would have to sleep in the saloon. Cleaning was still happening and the cleaning crew was upset that we'd showed up early, but we were allowed to leave baggage on the boat and walk over to the curry house for dinner, just as Niniane showed up. Arturo showed up while we were having dinner, so now we had a complete crew!

When we were finally allowed onboard, the provisioning had been done, and we could now take a look at what was missing. They'd bought us bread and cheese but no ham, I'd way over-provisioned on water, and I'd forgotten to ask for a paddleboard. There was no gear for diving to be rented for love or  money on the island (the rental places had been hit hard by the pandemic and closed, and the shops that were still open were no longer renting for a week at a time). I met the base manager and her staff, and they were very friendly, assuring us that we'd get a chart and technical briefing the next day and the paddleboard and fins would be no problem.

We went to bed thus reassured and ready to sail the next day.


Monday, December 06, 2021

Review: Cyberpunk 2077 (PS5)

 I actually pre-ordered Cyberpunk 2077, but the reviews ahead of the actual release were so bad that I cancelled my preorder and elected to wait, hoping that by the time I got around to it the experience wouldn't be the disaster many web-sites had claimed it was.

First, I managed to get my hands on the PS5. Then, Best Buy had a sale on it for $10. At that price, I bit and started playing it, keeping it mostly on my PS5 the entire time.

The most important part of The Witcher 3 was how good the characters were. As I played Cyberpunk 2077, I discovered that the characters were nowhere as well realized. A lot of it was that the Witcher came with baggage --- lots of books, and two previous games, and I had read enough of the books that I had a good understanding of the characters even prior to the game, and had predilections about which way Geralt would decide, but Cyberpunk had no such priors and I don't remember any novels from the setting, even though I actually might have read the RPG manuals ages ago.

The story is actually reasonable, once you take all that into account. You're playing a mercenary in Night City, and in a heist gone wrong end up with cyberware taking over your mind. From there events play out and you have a choice of how to deal with the main story, side jobs, and other ancillaries, with consequences playing out in the story.

The game play is easy: I went for a gun toting reflex driven combat-oriented build, and just chose to go in guns blazing all the time eschewing stealth. It worked for most of the game, though a few (optional) side quests would be locked out because I didn't have tech levels set high enough. The game actually has surprisingly little combat, and what there is wasn't painful as long as you levelled up enough on side jobs.

The game crashed about 5-6 times during my playthrough. Annoying, but with sufficient checkpoints that I never lost a lot of progress. Load times were long, but not as annoying as in The Witcher 3 where you'd pause for minutes when you died.

The graphics were decent. Definitely on par with any PS4 games, but didn't feel good after masterpieces like The Last of Us 2.

All in all, I thought the game was reasonably good (there aren't that many games I play till the end), so I enjoyed it. I thought Ghost of Tsushima or Miles Morales were better games, but neither of those games are RPGs, and this was the first RPG I liked enough to finish since The Witcher 3, so I'll still label it recommended.


Thursday, December 02, 2021

Review: Hello World - Being Human in the Age of Algorithms

 Hello World is Hannah Fry's book about algorithms for a lay audience. I expected to breeze through it since I already knew most of it, but what I loved was her explanation, including why every programming tutorial starts with Hello World, which I stole for an explanation to Bowen.

I enjoyed how she described both machine-learning applications and regular programs as algorithms, and walked through the implementations and implications of both for a lay audience. She does a great job explaining that the non-computerized implementations of algorithms have problems as well, in terms of noise.

our reluctance to question the power of an algorithm has opened the door to people who wish to exploit us. Despite the weight of scientific evidence to the contrary, there are people selling algorithms to police forces and governments that claim to ‘predict’ whether someone is a terrorist or a paedophile based on the characteristics of their face alone. Others insist their algorithm can suggest changes to a single line in a screenplay that will make a movie more profitable at the box office. Others boldly state – without even a hint of sarcasm – that their algorithm is capable of finding your one true love.* (Kindle loc 2952)

She points out that all algorithms  have issues:

 I’ve thought long and hard and I’ve struggled to find a single example of a perfectly fair algorithm. Even the ones that look good on the surface – like autopilot in planes or neural networks that diagnose cancer – have problems deep down. As you’ll have read in the ‘Cars’ chapter, autopilot can put those who trained under automation at a serious disadvantage behind the wheel or the joystick. There are even concerns that the apparently miraculous tumour-finding algorithms we looked at in the ‘Medicine’ chapter don’t work as well on all ethnic groups. (Kindle loc 2963)

 I definitely enjoyed the book, even though I'd encountered all the ideas in the book previously.  Recommended.

Wednesday, December 01, 2021

2022 Book Reviews

2022 Books of the Year have been chosen!


 Non-Fiction

Fiction
Comics

Monday, November 29, 2021

Review: Renegades of the Empire

 Scott Macdonald told me that his group at Microsoft (DirectX) was so famous that a journalist wrote about it. The book was called Renegades of the Empire, and not only was it not available at any of the libraries near me, but there was also no kindle version. Which meant I had to buy a used copy from Amazon and read it on paper with a booklight and everything.

The book describes Alex St. John, Eric Engstrom, and Craig Eisler's careers at Microsoft, how they started the DirectX effort, shoe-horned it into Microsoft (killing off WinG in the mean time), and then proceeded to try to create a web-browser (named oddly enough Chrome before being called Chromeeffects) which would fail.

The trio's antics are famous and very politically incorrect. The kind of statements regularly made by Alex St. John, not to mention the antics (hiring contractors using the marketing budget), deliberately dissing their own company at product rollouts, would undoubtedly get someone fired today. There's even a story of a food-fight in one of Microsoft's meeting rooms, with the clean up bill sent to then Microsoft VP Brad Silverberg, who wrote an e-mail saying, "I hope you enjoyed yourself."

Having worked with a few ex-Microsoft employees, I now understand much of their behavior. For instance, there are several instances in the book where a manager going on vacation would come back to discover that his team had been taken away from him. That explains why many former Microsoft employees would never take vacation. (To be honest, I think that attitude permeates much of tech companies today --- even at Google one of my friends once reported that taking vacation was given as a reason to deny someone a promotion, so I won't pretend that things are any better today)

Anyway, the book is eye opening, hilarious in parts, and well worth reading for the insight into the way various people you might encounter at work behave. Recommended.

Thursday, November 25, 2021

Review: The Messy Middle

 The Messy Middle is a book about entrepreneurship. Rather than being one about raising money, etc., it's almost entirely about the development of a startup past the initial stages but before being fully successful as an independent entity or being sold. The author started Behance, which was bought by Adobe, and sprinkles his narrative with anecdotes and stories from both his time managing Behance and as a transformative middle manager at Adobe.

The book covers many topics, but the management sections are interesting. In one particular case, he compares a well functioning team to that of a human body system, and describes a well-jelled team as having a healthy immune system, which would wholesale reject any transplant of a foreign entity (such as an new leader being injected into the mix). He describes the manager's role there as helping to suppress the immune system so that the new transplant can contribute. I will note that like many managers, at no point does he consider promoting someone from inside. (And in this particular case, he had been long time friends with the new manager and had faith that it would work out without tearing the team apart)

I switched from the audio book to kindle format in the middle of this book, but there were many anecdotes in this book that were geared entirely towards the product manager, rather than the engineering leader. One thing that particularly stands out is the fact that he considers the most important piece to be self-motivation, mentioning that startups are usually so hard that if you can't motivate yourself you absolutely will not finish.

There are huge sections about motivating yourself, optimizing processes, and right at the end a few notes about getting advice from third parties before any kind of sale happens. It's definitely good stuff and worth your time to read. There's the usual amount of self-aggrandization from any successful entrepreneur, but also enough useful stuff that I wouldn't consider it a problem.

Monday, November 22, 2021

Review: Batman Zero Year

 DC periodically reboots its universe for no reason other than to reimagine/retell all the origin stories from their classic pantheon of superheroes. Batman: Zero Year is of course its most recent retelling of Batman Year One, and in contrast to the grim and gritty Frank Miller approach, goes for the modern, post-apocalyptic viewpoint. 

The art style is modern and clean and a joy to view. The writing and main villain (The Riddler), not so much. Bruce Wayne, for instance, takes a long time to figure out that Wayne enterprises would be key to providing him with resources for his battle. Similarly, there are key scenes that make no sense, such as Lucius Fox injecting Wayne with a vaccine without telling him. The Riddler taking over Gotham City is a nice excuse for providing apocalyptic images, but ultimately shows how much supervillain victories look like the dog catching the school bus. He does nothing with that victory and never seems to be a serious threat.

The denouement, when it comes feels more than a little cliche, with Batman working away from a love interest that was barely introduced and one never cares about. I don't now why anyone would consider this even comparable to Miller's work.


Friday, November 19, 2021

Books of the Year 2021

 I read 69 books this year, including a couple of re-reads. It was heavily tilted towards non-fiction, which makes the non-fiction selection challenging.

By far the most useful book I read this year has to be Noise. A book about how to make decisions and remove jitter from your decisions has to qualify very highly in terms of usefulness. The problem is that the book is on the dry side. I would say that on the political side, the best book I read this year was The Price of Peace, the biography of John Maynard Keynes. It describes the long march and battle of ideas, and really shows how bankrupt the modern economic theories of Milton Friedman et al, are compared to Keynes' vision. It ties right in with Democracy in Chains giving you a complete understanding of the political economy. My favorite topic is still science, unfashionable as it is in this day of vaccine denial. I thought Exercised was a solid debunking of paleo exercise  and diet myths, and explains why we hate exercise so much despite also needing it. I also cannot help having a soft spot for Justice and The Wisdom of No Escape, both of which are exemplars of clear writing and thinking. By far the best business book I read this  year was Working Backwards. It's a clear explanation of how Amazon won so many battles against competitors with much higher margins and frequently better engineers. It's definitely well worth your time.

I guess having said all that, I will go for The Price of Peace as the book of the year.

The best fiction of the year was an easy choice: Project Hail Mary, easily the best novel I'd read in years. If you enjoyed the Martian, don't waste your time dithering. Just get the book and read it already.

I read a ton more comic books than usual, but none of them really stood out. I guess March would take the price, if I had to choose. As you can see, I found a bunch of really good books this year. I hope you try some of them!


Thursday, November 18, 2021

Reread: Use of Weapons

 Use of Weapons was one of the first Iain M Banks books I read oh so long ago, and I decided to read it again recently out of curiosity as to whether it held up. The book runs in two narratives, one moving forward in time, and one moving backwards, revealing the post-singularity society of the Culture as well as the character of Cheradine Zakalwe, who works as an operative for Special Circumstances, the dirty tricks arm of the contact section of the Culture.

The world building is excellent, with reveal after reveal of the culture and the way it operates interspersed with the memory of Zakalwe mixed in. The surprise ending (which I won't spoil) doesn't surprise the second or third time reading the book, and upon reflection, is the weakest portion of the book, since it doesn't actually explain the nature of the identity.

The next weakest portion of the book is the plot, where Zakalwe's generalship surprises the planning and machine minds behind the entire purpose of pulling Zakalwe out of retirement. One would think that having had repeated encounters and use of Zakalwe, the machines/Special Circumstances agents wouldn't be surprised again.

The Utopia that is the Culture is one of the few Utopias in fiction that's believable: a post-singularity society run by machines where the organic peoples are essentially pets does seem like it could be more moral than ones built by humans themselves. I enjoyed the re-read.

Monday, November 15, 2021

Review: Extreme Ownership

Extreme Ownership is a book featuring two SEAL task units' explanation of how leadership principles in the US Navy Seals work, and can be applied to the world of business. As with many leadership principles involved, most of these are common sense, but the authors do a good job of giving these principles catchy names so you can remember.

For instance, Leading Up the Chain can also be called "Managing Up", but hey, no matter what you call it, it's a good principle --- you usually need to overshare information up your management chain, because when they're the ones not directly involved in the work, situations, techniques, and problems obvious to you in your day to day life simply aren't things they aren't going to know about.

Similarly, they point out that in a leadership position, you have to act as though you have agency and effectiveness for all aspects of your organization involved in your mission. Because if you don't, you're just going to fail:

SEAL troops and platoons that didn’t perform well had leaders who blamed everyone and everything else—their troops, their subordinate leaders, or the scenario. They blamed the SEAL training instructor staff; they blamed inadequate equipment or the experience level of their men. They refused to accept responsibility. Poor performance and mission failure were the result. (pg 36)

The stories/anecdotes, and examples from the Iraqi missions are fun, and illustrative of the modern military. Even after they've penetrated an enemy HQ, they still have to collect evidence and document it and label it correctly. It took discipline, but it shows that an elite military unit really can live up to the demands the civilian society asks of it.

Where do the book fall short? Well, the military's enlisted men, by and large, once they've been deployed, do not have the freedom to change jobs. They would face extreme sanction. And of course, once you're in the field self-preservation (and team bonding) ensures that they will stick it out long enough to return to base (though as the book points out, some return in body bags). The modern work environment, however, means that your talent can walk any time. But this makes leadership more important. As the book explains, you really have to explain the why behind every mission and not assume everyone understands it. If you brief your team and get no questions, that means that people don't understand it, or don't believe it and are too polite to let you know.

The book's worth a read. It's entertaining, and yeah, you might know all the common sense stuff, but it's worth reminding yourself of them every so often.


Thursday, November 11, 2021

Review: Influenza

 Why read yet another book about Influenza, when I'd already read The Great Influenza? I kinda skipped the history of the so-called Spanish flu, having already gotten all of those details from that other book, but the modern parts of the book were actually interesting.

For instance, I didn't know that the approval of Tamiflu was actually steeped in controversy. It turns out that it reduces your symptoms by one day, but only if you take it right away. But we stockpile it anyway, thanks to some insider's political involvement during the procurement process. Similarly, I didn't know that the British NHS would only vaccinate the very old and the very young with the flu vaccine and basically not recommend flu vaccines for everyone in between. Again, I don't know if that's changed since the COVID pandemic.

In any case, it seems like any kind of treatment/effective vaccine for the influenza is quite some time away, and of course, since the book was published events have over-taken it and we've gotten effective COVID19 vaccines in record time, so maybe if another influenza pandemic kicked off we might be able to do it again.

I thought the book was good, but not as good as The Great Influenza.


Monday, November 08, 2021

Review: The Math of Life and Death

 While Bowen was in pre-school, there would be days when he would regress, going from playing with challenging problems to something dumb and simple. On those days, I would comment that he'd taken a stupid pill, and just wanted to do something that wasn't an intellectual challenge.

I must have picked up The Math of Life & Death on one of those days when I'd taken a stupid pill. The book doesn't really describe anything I didn't already know, even to the point of rehashing the old Google interview question involving the Birthday Paradox.

While I was working my way through this book, on a bike ride Bowen asked me why even though we're on the decimal system, directions and time were described in minutes and seconds, which were in base 12. And I had just read the section of the book the day before about how certain human cultures counted in base 12 by counting the knuckles of the fingers of one hand (excluding the thumb), which added to 12, while using the other hand to count off the number of 1-12 cycles, which is how you got 60 seconds per minute, 60 minutes per hour, and 12 hours per half day.

Dang, I did learn something from this book after all! The book is transparently written and entertaining with all sorts of factoids like this that kept me going. And hey, it must not have been a stupid pill if it made me sound like a knowledgeable dad to my (now cynical and difficult to impress) 9 year old.

Thursday, November 04, 2021

Review: Mindset - The Psychology of Success

 In recent years, you might have heard of or been encouraged to take a Growth Mindset. Well, Mindset is the book that kicked off this trend. To some extent, the book is similar in philosophy to something that I said about startup a few decades ago: "Your success as a startup is dependent on luck, market factors, and all sorts of vicissitudes you have no control over. However, you might as well plan for success, because if you planned for failure you will achieve it."

Similarly, the book basically eliminates discussion of fixed traits such as IQ, body shape, etc., but basically says: "you should plan as though there are no fixed traits, since no matter what traits you have, you can improve your success at a task through the right kind of work, and the evidence is that the people who approach life with this attitude are much more successful than the people who adopt the idea that their major attributes are fixed with no hope of changing them."

Put in those terms, the book is pretty much common sense. But there are several subtleties that I wouldn't have realized that the book points out. For instance, the book points out that women are much more dependent on external validation/evaluation of their performance than boys/men are:

Boys are constantly being scolded and punished. When we observed in grade school classrooms, we saw that boys got eight times more criticism than girls for their conduct. Boys are also constantly calling each other slobs and morons. The evaluations lose a lot of their power. (kindle loc 1344)

A male friend once called me a slob. He was over to dinner at my house and, while we were eating, I dripped some food on my blouse. “That’s because you’re such a slob,” he said. I was shocked. It was then that I realized no one had ever said anything like that to me. Males say it to each other all the time. It may not be a kind thing to say, even in jest, but it certainly makes them think twice before buying into other people’s evaluations. (kindle loc 1346)

That boys constantly "neg" each other actually gives them power --- control over how they view other people's opinions and evaluation. Similarly, Dweck points out there it's possible to have a fake growth mindset, where the focus isn't really on growth and personal improvement, but on external achievements --- she describes a high achieving high schooler who succumbs to ulcers and other health problems due to the pressure put upon her by her parents.

Dweck also points out that growth mindset is contextual. You might have a fixed mindset about your drawing abilities while adopting a growth mindset about your engineering skills. There's nothing wrong with that unless your approach percolates to your family and children, where they start emulating your mindset. Plenty of examples (long-winded, unfortunately) are scattered throughout the book to drive home her points.

I thought the book was worth reading, common sensical as it was, but maybe that's an indicator of how successful the book was --- you'll read it and kinda think well, of course! But as with everything else in life, adopting that common sense is much harder.

Recommended. 

Monday, November 01, 2021

Review: 3 Doctor Strange Books

 Boen was looking for a movie to watch, and so I pulled out my copy of Dr. Strange, which my wife had watched years before, and rewatched it with him. The special effects on that movie are still good, and I found it enjoyable, though I was very surprised when Boen asked me to read Doctor Strange comics to him instead of his usual non-stop diet of Invincible.

First up, was The Oath, which despite being ranked very highly was a very simplistic story. But it was clearly targeted for little kids and Boen enjoyed it enough to ask for more Dr. Strange. Then I tried The Way of the Weird. This was less dumb, but still not very good, and far too talky. Boen got bored by the 4th chapter and has since gone back to his usual diet of Invincible. I finished it and the book ended in a bad place, so I checked out The Last Days of Magic. This was passable fantasy, but still dumb. There's no sense of wonder, and despite the scope of magic, it clearly has nothing on anything Neil Gaiman or Alan Moore did in the DC Universe: Swamp Thing, The Sandman.

Clearly, the writers tried, but couldn't produce anything of clear literary value. It's amazing to me then, that the Dr. Strange movie ended up being as good as it was!


Thursday, October 28, 2021

Review: A Philosophy of Software Design

 Over time, I've learned to be very suspicious of thick programming books. The thicker they are, the more likely it is that they be crammed with worthless code listings, and pages after pages of diagrams and pontification that's worthless. Thin books like K&R tend to be much more useful. When Steve Grimm recommended A Philosophy of Software Design, I was very happy to discover that it was a thin book.

You probably know many of the things Ousterhout points out, but even if you do, you've probably never seen them articulated this way before. For instance, he mentions that you should aim for API designs that have depth. His expression of "depth", however, might be different in principle from what you've heard before, which is that you should have few APIs/interfaces that are composable in ways that provide maximum functionality and abstraction.  He explicitly compares the UNIX file "open" type system calls vs the Java InputStream set of classes and finds that the InputStream type much to his distaste --- using it requires creating multiple classes stacked on top of one another, leading to verbosity, while the UNIX api just requires an "open."

There are many other common design mistakes that Ousterhout points to, including avoiding pass through methods, avoiding decorators, putting different abstractions for different layers of an API design, and taking on as much configuration complexity as possible as part of the design of the lowest layer of the API, rather than exporting it as tunable knobs at higher levels. In particular, he also points out that the error API like exceptions and return codes are part of a system's interface, and that programmers and designers need to think carefully before exposing them as part of a design --- if you can eliminate an error code, you've simplified the design considerably, and it's worth implementation complexity to do so.

I loved the sections of commenting ("write the comments first" is counter intuitive advice that might be worth trying), and naming hygiene, where he describes a bug that took him 6 months to find because a the same variable name was used to hold both physical blocks and logical blocks, and that one piece of code that confused the two slipped by multiple code reviews and inspections while silently corrupting files in a file system. These are design issues that can only be learned through hard fought experience, and Ousterhout has the scars to prove it.

I also enjoyed his perspective on object-oriented programming, agile development, and test-driven development. (Spoiler: he thinks that test driven development is bad because by writing the unit tests first, you've unconsciously made the cost of changing a design during development higher, thereby making it more likely that you'll try to patch a bad design than radically refactor it)

The book does have limitations. For instance, a lot of the complexity in modern APIs are because of the need to support legacy applications. Ousterhout has no experience with this (and neither do his reviewers, many of whom are Google engineers), and so doesn't comment on it, but it's a major issue in any company that's built a platform or is building a platform, since usually those are built in a hurry and only after success do you realize that you screwed up (the failures never need to be fixed since they have no customers). Many modern programming environments and systems make it easy to pull in libraries and dependencies from open source or other repositories, but this explosion of dependencies actually makes it really hard to debug and fix code. Ousterhout doesn't comment on that either, since most of his designs were base layer operating system type code. Another source of complexity I've found in modern systems is a penchant for putting behavioral controls in config files rather than in code. For instance, many Java logging systems assume you'd want to control logging in a properties file, which I've found to be backwards --- the logging systems should expose a programmer API, and if the application needs a config file to control behavior then there should be libraries available to do that reading and configuration, but making it hard to control behavior through an API actually makes it harder. SpringBoot (where you can spend all your time debugging inscrutable config files) is another example of this sort of misdesign.

No matter the limitations, this is a great book and well worth your time to read if you're an engineer. It's a great discussion of microarchitecture (not systems design) and good API design as well as good programming practices that makes you think. Recommended.

Update: The above was a review of the first edition of this book. There's now a second edition, and Prof Ousterhout has kindly published the additional chapters as a PDF on his web-site.

Monday, October 25, 2021

Review: Measure What Matters

 Measure What Matters is John Doerr's slides about OKRs turned into a book. OKRs (Objectives and Key Results) are given credit in the book as a management tool for companies like Intel, Intuit, Google, and many others for organizing their workforce around a common set of objectives, and driving for continual improvements. They are getting credit for eliminating politics and getting cross functional teams to work together.

Perhaps if I'd been more indoctrinated in the OKR process I would have avoided many career mistakes at Google. For instance, hiring, mentoring, and other important activities were never part of the organization's OKRs, so in retrospect I should have spent zero time on it and focused on my OKRs. Similarly, if you help someone save their job (by moving them out of the PIP process through mentoring or intensive teaching), you were not working on anybody's OKRs. An organization as big as Google really doesn't care.

To me, this is the biggest indictment of OKRs: by the time morale and cohesion of employees has deteriorated to the point where it's important enough to become an OKR, you've already lost. It's too late to stop an exodus of talent. OKRs almost never deal with this until it's too late, which is why you get the Silicon Valley death spiral.

At the back of my mind also is that the book doesn't actually provide any counter-factuals. For instance, there could be companies that have succeeded without OKRs as well, and it could be that Google succeeded not because of OKRs, but because it was in such a great market and had such a great business model that it would have succeeded anyway. Notice, for instance, that OKRs didn't help Google Video win over YouTube. It was having $1.6B in the bank that allowed Google to buy YouTube and then leverage that property into success. But in a business book, you're not allowed to write about alternate hypothesis to the tool you're trying to push.

Furthermore the kind of stuff that's discussed as distractions and innovations (the book makes the point that most innovation happens bottom up, rather than top down, but doesn't discuss the possibility that a laser focus on OKRs would actually usually prevent such innovation) usually turn out to be valuable, but difficult to measure, and probably never on anybody's OKR radar. I once had a conversation with Bill Coughran about OKR myopia and his response was, "The founders worry about becoming quarterly and short term focused after an IPO. I fail to see how the company could become any more short-term focused."

If you work any any company that fully adopts OKRs are an operating principle, this book is essential for your personal and business success. But if you're in the position of thinking about adopting this, just remember that the plural of anecdote is not data.