Auto Ads by Adsense

Booking.com

Monday, March 30, 2026

Review: American Vampire Vol 1

 Boen's been on a Stephen King kick of late, reading various Stephen King novels like Christine, I saw that American Vampire Vol 1 was available as a Prime free loan, so I checked it out and read it. The narrative is split into two timestreams: one (written by Scott Snyder) set in the 1920s in Hollywood, as two young actresses who're hoping to make it big get dragged into a party for the Hollywood Big Wigs in hopes of landing a great role. Rather than going Harvey Weinstein on them, the big wig instead sucks their blood (hey, it's a vampire book, what did you expect).

The second timestream is set in the time of the Wild West. This narrative was written by Stephen King, and it's obvious that he's new to comic book writing. There's way too much dialog, and not enough time spent making you care about the characters.

The art is good, but the vampire schtick is kinda worn out. It's nothing that you haven't seen in Blade, for instance. I was hoping for more originality. I guess the vampire trope is so worn out that even Stephen King can't come up with a good new story, and is stuck retelling old stories.

Thursday, March 26, 2026

Re-read: Lone Wolf and Cub - The Assassin's Road

 I remember reading and enjoying a few issues of Lone Wolf and Cub as a teenager, so I checked out the first volume, The Assassin's Road from Hoopla. A lot of the art and for instance, the stand-off sword-fight scenes look very familiar, because games like Ghost of Tsushima have adopted the art and the tropes and made them look great.

What I was unprepared for was a reminder that the Japanese do not hide behind a rating system for their comics. There's rape, seduction, lots of blood and gore (in black and white) and obviously, there's the incongruity of a Samurai assassin taking on murderous bounty jobs with a 5-year old in tow.

The whole volume (in which the origin story only appears right at the end of the volume) is full of situations where Itto Ogami (the titular Lone Wolf) through craft, guile, and just sheer amazing swordsmanship, dispatches his targets and then walks off into the sunset, baby cart in tow. There are lots of action lines, and the dynamism of the art leaves no question that this is an action comic.

It's enjoyable in small doses. I think I'll space out my reading of the series.


Monday, March 23, 2026

Review: Apple in China

 I make no bones about my dislike of Apple and everything it stands for. To me, Apple represents the worst of American culture:

  • Disposable, throwaway products that cannot be easily repaired (or even just replace the battery)
  • Form over function, to the point where Steve Jobs told its users "you're holding the phone wrong", when it was clearly a badly designed antenna system
  • User-hostile product design that's designed to make you spend more money on its ecosystem (e.g., taking away the headphone jack, or removing the SIM card slot so you have no choice but to go through Apple to even purchase a cell phone plan)
Apple in China, despite it's subtitle about Apple being the greatest company, is no sycophantic tract talking about how great Apple is. It is a systematic, well-researched history of how Apple "outsourced" its manufacturing to an entire supply chain in China, and in doing so, massively sped up the acquisition of advanced technology in China. The word "outsource" is in quotes as follows:
Apple had essentially cracked the code on how to manufacture the world’s best products without doing any of the manufacturing itself. It wasn’t really “outsourcing” in the normal sense—that would imply it was sending blueprints to companies capable of taking the orders and executing. Instead, Apple was routinely sending its top engineers, designers, procurement specialists, and lawyers from the United States into hundreds of factories across the country, where they’d import machinery, train armies of workers, coordinate the delivery of intermediate goods, and scrutinize suppliers to ensure compliance. Apple’s influence was enormous, but no senior executives lived in China or understood the politics, nor had Apple appointed anyone to oversee the business or manage government affairs. (kindle loc 97)

In fact, as the book discusses, despite American politicians' lamentations about how America has forgotten how to do manufacturing, it's quite clear that all throughout the book, Apple has not forgotten how to do manufacturing, and is in fact, at the cutting edge of advanced manufacturing. What it has done is to deliberately design its products and supply chain to take advantage of the resources available in China in order to scale its advanced manufacturing:

Apple wasn’t, by any stretch, the largest computer maker working in Taiwan, but its penchant for complex designs and intolerance for defects was unique and over-the-top, necessitating a form of intellectual investment shared by none of its rivals. Apple veterans from the time can’t stress enough that nobody else was embedding dozens of engineers into Taiwanese suppliers, then consistently pushing the envelope on what was possible. “Apple is single-handedly responsible for bringing quality into Southeast Asia,” says Robert Brunner, the director of the ID studio from 1990 to 1997. “If you look at the capability they brought up in that region, from a manufacturing standpoint, it’s solely on their presence and their demands on these organizations that caused them to build that competency of being able to make quality things.” For the biggest computer makers at the time, design and R&D were such secondary considerations to logistics and efficiency that Sun Microsystems CEO Scott McNealy once likened Dell to a grocery store: “They’re not in the PC business any more than Safeway is in the food manufacturing business.” (kindle loc 1083)

One of the most interesting examples is the use of end-of-line testing equipment. The book describes these pieces of equipment were originally designed for lab benches, and cost north of $100k each. Apple insisted on buying them in bulk and installing them at the end of factory lines in order to ensure quality. While you might expect that Apple expects its contract manufacturers to foot the bill for these machines, Apple went and bought them and had them flown into the factories and installed. This did a few things. First, these machines were exclusively used for Apple products. Secondly, it was a threat to its supply chain partners. If they ever stepped out of line, Apple would just pull its machines out and place them at alternate factories!

For Dell, ever focused on efficiency, China’s advantages were all about cost and scale—that is to say, they were about margin. But Apple looked at the armies of affordable, available labor and saw a different potential: unconstrained design. Or to put it differently: Western PC companies were shifting to China because of what was available; Apple shifted because of what was possible. Before the return of Jobs, Apple computers were manufactured in a fashion called poka-yoke, a Japanese term meaning “mistake-proofing.” The idea was that products should be designed for easy assembly. And a desire for more automation amplified the trend: From the sketching stage on forward, blueprints for hardware were constrained so machines could put them together without error. But what Apple was realizing was that thousands of laborers cheaply handcrafting Apple hardware on a conveyor-belt production line allowed its designs to be maddeningly intricate, complex, and automation-unfriendly. (kindle 1138)

The book is full of intricate details. For instance, it describes the initial design of the first polycarbonate iMac. What other biographies (usually written by sycophants like Walter Issacson) described as Jobs' genius in pushing his team to the limits and beyond is actually not true! The initial design by Jonathan Ives' group was essentially unmanufacturable! Despite months of Jobs' idiotic pushing, the physics just wouldn't yield. Eventually Jobs sent the design to a firm in Silicon Valley that he trusted, and they responded that the design was not manufacturer. Only then did Jobs believe Apple's manufacturing engineers, and Jonathan Ives went back and in cooperation with the manufacturing engineers came up with a design that was manufacturable at scale. To Apple's credit, the organization learned from these mistakes and from then on, product design would even go so far as to visit Taiwan and work with manufacturing to ensure that their designs could indeed be fabricated.

The shape is a pyramid, with Jony Ive’s Industrial Design team at the top. ID would conceive how a product would look and feel, with an exactitude that drove fear into the rest of the organization. Their creation goes to Product Design, whose role is to figure out the mechanical engineering and make the product functional. Then it moves to manufacturing engineers—a small team back then, and later a distinct unit called Manufacturing Design, or MD—who work with component makers and final assembly partners to actually build the product. Finally, the Operations team comes in. They work with vendors that their colleagues have already selected, and then optimize everything to help the product scale. But crucially, Ops also has a prerogative to find other component makers, other final assembly partners, to build resiliency, cut prices, and to instill competition. (kindle loc 1441)

The relationship with  Foxconn is similarly described in detail. Foxconn bent over backwards to get Apple's business, despite making no profits. This was a deliberate strategy to build up his own company's manufacturing expertise:

“His people used to hate us, because they used to make no money out of us,” says an Apple operations executive. “The Compaq guys”—the Foxconn team building for Compaq—“were making a fortune on bonuses, and no one wanted to come work on the Apple account because there were no bonuses.” But Gou answered to no one. He took a long-term view, knowing that if his team could please Apple, they could please any client. (kindle loc 1410)

 Gou even deployed a clever tactic to rotate his workers on Apple projects, to maximize the learning. “We trained all of them. Then one day we’d be like, ‘Where’d those engineers go?’ ” says Fadell. He’d learn that they’d gone to work on other projects, using their new skills in areas that were more lucrative. Then Apple would be forced to teach a new cohort of people, as if a new semester had started. (kindle loc 2007)

 Page after page, the book's details and research is impeccable and very much worth reading. There's a whole chapter about employee burnout at Apple through constant trips to China. Once in China, the work was non stop and relentless. Apparently, many employees ended up losing their families as a result of this work schedule. To my surprise, Apple's manufacturing engineers must have been extremely poorly paid. The book describes one instance where a wife called up a husband and loudly denounced his upcoming trip to China and threatening a divorce if he made the trip. The manager's solution? Offer the engineer a $10k bonus for taking the trip, buying off the spouse. Even in the mid 2000s, I cannot imagine a single Google engineer's wife considering a $10K bonus (after taxes it would have been $6k) suitable compensation for taking away her husband for months. One engineer was even told by his doctor to quit his job or die on it:

Apple came close to codifying the principle that pushing employees to burnout was acceptable. In a slide deck called Leadership Palette, Apple states: “Fighting for excellence is about resisting the gravitational pull of mediocrity. It involves being dead tired and still pushing yourself, and others, to get it right, every time.” One engineer says the reason he left Apple after more than a decade is that during a routine medical appointment, his doctor noted his high blood pressure and said, “Okay, I need you to do two things for me: lose weight and quit Apple.” The doctor explained that the stress would basically kill him. Some Apple engineers can even rattle off the names of people who died on the production line or upon their return from yet another trip to Asia. The engineers were often in their forties and fifties, and while it’s not possible to conclude that overwork was their cause of death, many believe it was. One longtime veteran recalls that, during the funeral for one of these people, the number of Apple employees who left the Sunday service to join conference calls was unbelievable...Jon Rubinstein, who worked for Steve Jobs on and off for sixteen years, called the long workweeks “shattering,” and it’s what led to his own departure later on. “A lot of people got sick at Apple,” he once said. “The list goes on and on of people who got terminally ill or really ill… and I worried that if I stayed, I’d end up damaging myself, and my health was, frankly, more important.” He added: “Steve used to always tell the groups, ‘This will be the high point of your life,’ and I was thinking, God, I hope not, right? Because that’s really a sad way to think.” (kindle loc 2112 - 2122)

There's even a story of the manager of the Apple store in Beijing voluntarily going to jail in order to defuse a nasty situation at the Apple store. If you remember all those stories  about fights breaking up in China's Apple stores about being given a chance to buy an iPhone? This book explains the background. It turns out all the people in those lines were scalpers who were paid to buy the phones and then those phones got distributed into the Chinese market. 

The book describes Apple's slow awakening into China's politics and how Xi Jinping's ascendence caught them by surprise. But rather than diversifying its supply chain, Apple instead doubled down on it, making itself even more vulnerable to China disruption than before. It took multiple supply chain failures before Apple started taking even small steps to do manufacturing outside China, and even then those steps are half-hearted and slow, mainly out of fear that if Apple moved quickly China would cut them off. I have friends who defend Apple by saying that other manufacturers are similarly vulnerable. This book completely debunks that. It turns out that Samsung makes more phones than Apple but is almost completely immune to a China supply chain disruption:

Samsung, the only company that sells more phones than Apple, is much less vulnerable. Samsung runs its own chip foundries, which are second only to TSMC, in Korea and Texas, and in 2023 the company pledged to invest $230 billion to build five new fabrication plants over the next two decades. Indeed, Samsung is likely to be the biggest winner in the event of an earthquake in Taiwan, be it political or natural. Disruption to supply chains in Taiwan would hinder Samsung’s ability to import certain components, but the impact would be far less than for Apple. (kindle loc 5383)

 Needless to say, the highlights and quotes I've provided in this book are a tiny fraction of the book filled with interesting, insightful stories and never before disclosed details. It definitely disrupts the usual story about manufacturing knowhow being shipped overseas, and it's a far better story than the usual books about China such as Breakneck.  This book makes those books look like the shallow, sophomoric and poorly researched books that they are. If the Financial Times reporting is all like this I should give up my subscription to other magazines and subscribe to FT instead!

I wouldn't be surprised if come November I nominate this book as the book of the year. That's how good it is. Highly recommended.

P.S. One thought I had after finishing this book is that you should be very optimistic about manufacturing in the USA. Apple (and other American companies) still know a lot about manufacturing. If the country ever got its political act together enough to want to do a big manufacturing drive, the fact that China did it so quickly meant that the USA can do so as well. Of course, that depends on Americans politically understanding the situation well enough to vote accordingly. That part of the equation I'm not very opitmistic about.

Thursday, March 19, 2026

Review: Wonders of the Universe

 Wonders of the Universe is the companion book to Brian Cox's TV show of the same name. I read the book on Hoopla, so probably didn't get the best way of viewing the book. The pictures are tiny, and uninspiring, and if the TV show was well produced it probably looks way better than the crappy photos that show up in the book.

It is probably my least favorite Brian Cox book, probably because it covers topics already covered in his many other books, but without the deeper pedagogy displayed in those books. Like Cosmos, it covers a lot more history of science than it actually does the science, and so the science that it does present has to be simplified.

Don't get me wrong, the book's diagrams does teach you new stuff that wasn't in the previous books, but you have to look hard for it, and obviously reading the book on Hoopla doesn't give you the crisp photos that would be in the paper book. In addition, I really question the choice of photographs used in the book --- maybe the TV show would inspire awe, but in the book the photos just look drab and uninspiring. Better to leave the photos out if you're going to choose bad photos!


Monday, March 16, 2026

Re-read: The Magician King

 It's a strange feeling to re-read The Magician King after having seen a few seasons of The Magicians TV show. On the one hand, Lev Grossman is such a bad writer that the best episodes of the TV show are so much better written. By contrast to the TV show, the book's plot structure has our protagonists being driven by events, with no plans and no motivation, with events unfolding one after another as though in a dream.

On the other hand, a novel (even one in a trilogy of fantasy novels) doesn't have the constraints a TV show has, so characters can die a permanent death. In this book, half the plot is about Julia's career as a hedge Magician, working her way up the hierarchy of a series of safe houses. In the TV show, this was all done in parallel with the first couple of seasons, and obviously, the TV show wanted to keep Stella Maeve in the show, so Julia never got the final arc the book gave her.

Once again, the protagonists like Quentin and Eliot aren't very likeable, but the ending, with Quentin getting kicked out of Fillory had a finality that the TV show never achieved in the episodes I watched. (I haven't seen all the season so maybe his exit from the TV show is better) But the book did give Quentin moments of competence as befit the title of the novel, which to be honest the TV show didn't seem to ever do.

Obviously, I enjoyed the book enough to re-read it, so I have to give it a recommended tag.

Thursday, March 12, 2026

Review: Why does E=MC^2? (And Why Should We Care?)

 I guess I'm on a Brian Cox kick, and this time, it's his 2009 book, Why does E=MC^2? I really enjoy the way he finds different ways of explaining similar things. This time, he explains relativity, but without recourse to any Penrose diagrams. He basically starts with 2 assumptions, one driven by experiment, which is the speed of light is measured to be the same no matter where you are, how fast you're going. The second is that causality applies, in other words no way can you ever see the effect prior to the cause.

From there, he uses the Pythagoras theorem, but applied to 4-dimensional space-time, and derives the basic equation. It's an impressive tour de force, and explained clearly and relatively cleanly, even down to the use of complex numbers. He then goes on to explore what mass is, then introduces the standard model of quantum mechanics, and proceeds to describe various relativistic effects.

This book was written before the conclusive discovery of the Higgs Boson at CERN, but was clearly very confident about the outcome of the LHC experiments. I thought it was quite a lot of fun to read. Maybe I should start watching his TV shows as well.


Monday, March 09, 2026

Review: Human Universe

 Human Universe is based on Brian Cox's TV show.  Apparently, that's a show similar to Cosmos. I read it and enjoyed it quite a bit. First of all, unlike his other books that I've read, this is much more of a science history book than a technical book explaining physics. We start rather similarly to Cosmos, with an explanation of our view of the universe and how it went from us being the center of the universe to the solar-centered view of the solar system.

From there, we expand out to our understanding of where we are in the galaxy and where our galaxy is in the universe. As the scope increases, we get into deeper questions of cosmology, for instance what happened before the big bang. To my surprise, I actually learned new stuff here. Cox posits that inflation predated the Big Bang, and that the matter that we get were the residue after inflation had slowed down. He further posits that inflation might not have stopped in all parts of the (multi-)universe, and that parts of the universe might still have inflation happening. The speculation is then that the laws of physics that occur outside our visible universe might be different. We get an exposition of the Anthropic principle (both strong and weak versions of it). Cox does all this without reference to String theory, which I appreciate.

We also get an exposition of the Drake's Equation. (By the way, one of my pet peeves is that the Drake's equation doesn't factor in the probability that the planet has a strong enough magnetic field to keep its atmosphere from being blown away by its star --- the fact that Mars doesn't have a magnetic field is an indication that magnetic fields are not a given) There's speculation as to why there aren't any other aliens out there (Cox posits that the transition to multi-cellular life through the evolution of Eukaryotes took 3.5M years, which meant that it wasn't a given!).

I enjoyed the book and learned not a little. Recommended.

Thursday, March 05, 2026

Review: The Quantum Universe

 The Quantum Universe is Brian Cox's introduction to quantum mechanics. Of all the books attempting to teach quantum mechanics that I've tried to read, this is the one that has the best pedagogy. Rather than follow the historical approach (introducing Heisenberg and Schrodinger's approaches first), Cox decides to use the Feynman approach right away. This allows for a geometric and diagrammatic approach to the subject that makes the initial approach relatively easy.

The approach rather than using equations with complex numbers and trigonometric functions like sine and cosine, takes advantage of the fact that you can represent complex numbers with a polar diagram. To make things easier for the layman, Cox describes these as "clocks", with magnitude represented by the size of the clock, and the hour hand (there are no minute hands in these clocks) representing the vector composed out of the real and imaginary parts. He then defines the rules for "adding" and "subtracting" clocks, and then defines how interference and cancellation of waves works. Out of all these mechanics he then gets to show how the famous double split experiment results are described correctly by this system.

From there, of course, the topic only gets harder. We extrapolate this system from photos to quarks, bosons, and Cox waves his hands and says these differ because the rules for the manipulation of clocks are different for each category. We get a walkthrough of how the standard model explains how an atom holds together, how the electrons in a hydrogen atom works, an explanation of the Pauli Exclusion Principle, and how the Higgs boson gives mass to the other particles.

Don't get me wrong. Quantum mechanics is hard. I found myself tired and falling asleep after spending an hour reading chapters of this book. I suspect the best way to approach this is to not try to read this book at bed time (though it did succeed in making me sleepy), but to do it during the day with pencil and paper handy and actually work through all the equations and diagrams he poses.

The book ends with deriving Subrahmanyan Chandrasekhar's result that a neutron star cannot be more than 1.4 times the size of the sun. This is a tour de force, involving everything you've learned so far. I will admit I couldn't follow all of it, but nevertheless I enjoyed the book.


Monday, March 02, 2026

Review: Congratulations, By The Way

 Congratulations, By The Way was George Saunder's commencement speech at Syracuse University. It's mercifully short, and went viral, after which it got turned into a book.

The kindle formatting of the book is awful. It looks like a children's board book with just 4-6 sentences per page, completely disrupting the flow and feel of the speech. I for one, feel like he should have just posted the darn thing on a blog.

I don't object to the content --- of course you should be kind, and of course you should actually take some time to cultivate your kindness. But one thing you have to bear in mind is that fiction writers are essentially professional liars. As Charlie Stross once said: "Give me money and I'll tell you lies." So I suspect that he does regret the time he jumped into a river what monkeys have pooped in in Africa and gotten sick for days afterwards. I certainly would.

The book is also very vague on what kindness is. For instance, many people think it's kinder to lie to someone about how they look, or how smart they are, than to be honest and tell them that they suck. I actually think that a commitment to honesty, at least to the people you care about the most matters more and is kinder than the momentary feel of warmth. After all, if you make a habit out of lying to the people you love you eventually lose credibility and there is no kindness in that. (Then of course, I watch as my two sons tell each other lovingly that they're fat even when they both have BMIs well below the average, and maybe that kind of lying isn't that bad)

It's a quick read, you won't get much out of it, and it should have been a blog post.