Hospitality – Trouble
Their first album was sharp aristocratic twee that was fun on its own, but I mostly knew it as a good Spotify Radio seed. Trouble steps up the game quite a bit, breaking out a range of styles that all hang together. Really solid stuff.
Courtney Barnett – A Sea of Split Peas
I’m not usually big on lyrics but I love Barnett’s.
El Sportivo & The Blooz – Nights & Weekends
Found via a Marc Maron playlist linked from the Hospitality page on Spotify. I love Spotify.
Prince – Dirty Mind
I saw that Prince hairstyles post on Kottke and thought “I should listen to a bunch of Prince albums today”. That’s how I found out I don’t really like Prince albums all that much, except for this one.
Japandroids – Post Nothing
I like their newer albums, too, but I keep coming back here for Heart Sweats.
Smoke Fairies – Blood Speaks
If nothing else they sure know how to name things.
Dinosaur Jr. – You’re Living All Over Me
I forget about this album for long stretches and then it pops back on my radar somehow and I remember how perfect it is.
Ground shipping is a huge industry that’s saddled with huge human costs, and Google is setting itself up to be able to tackle every aspect of it.
Google Maps provides turn-by-turn directions and traffic analysis. StreetView cars have to be scheduled and dispatched efficiently. Shopping Express is a fairly quiet learning exercise for how to become a delivery link in at least a few supply chains. But all of these capabilities are basic requirements for the industry, nothing special yet.
The big disruption comes on the human end. Google’s further along than anyone on self-driving cars, and the sleep-enfeebled long-haul trucking industry won’t be able to compete with an automated rig that never has to stop. Seems like the tech is almost ready, the biggest obstacle there is going to be the legal questions (more on that later).
Fedex, DHL, and UPS all employ hundreds of thousands of people, many (most?) of them warehouse workers or delivery drivers. Warehouse workers are already in the process of being replaced. Delivery drivers, on the other hand, have seemed safe. Customers want packages at their door, and the only way to provide that right now is to send a human out to drive and then, critically, walk them there.
But Google has been making some interesting purchases lately. They’re loading up on robotics companies, including the terrifyingly amazing Boston Dynamics.
Imagine this: a self-driving delivery truck loads up and heads out, parks at some optimal location, and dispatches a dozen robots who walk the packages that last twenty precious yards to a dozen people’s doors, in parallel, and then load back up, move over a block, and do it again.
This is more plausible to me than Amazon’s drone idea. Drones buzz over people’s homes and in their faces. They’re more susceptible to wind and rain. They can’t handle heavy or large items. They can’t open doors to slip packages in when you’re away. Automated trucks and grounded smartbots, on the other hand, build on existing infrastructure and would interact w/ people in more-or-less the same way that delivery drivers do now. Just way more efficiently.
So how do we get there?
First, states and cities need to make self-driving trucks legal. Some states are getting there with preliminary laws allowing limited autonomous vehicles, but full-blown automated trucking is probably a ways off; people aren’t comfortable sharing the road with self-driving anything yet, much less massive trucks.
But what if the first self-driving things were actually small, light, slow, and all-around non-threatening? Like, say, a specialized StreetView vehicle that only needed enough ‘vehicle’ to hold the StreetView rig? It seems like it should be relatively easy to get that past a legislature or two.
That’s the wedge in the door. People become acclimated to seeing driverless vehicles on the road, the allowed sizes gradually go up, and then we have trucks, first only on highways and then everywhere. No big legal questions about opening up airspace, and the seemingly fundamental questions of agency and liability for driverless vehicles gets sidestepped here because these are commercial vehicles and Google the Company is obviously the entity that has both.
Second, the technology needs to get there. Watch those Boston Dynamics videos again. On a ten-twenty year scale, I think the tech side is going to be fine.
Third, people need to be ready for it, and not just in the legal sense; I’m cynical enough to believe a powerful company like Google could make the legal issues disappear before people were actually ready to see them go. But if nobody wants to buy things that are going to get delivered by scary robots, then the whole thing falls down.
Ground shipping at first doesn’t seem like the sort of sexy tech people want to picture when they think of Google. It definitely won’t be the only thing they’re doing (if they’re capable of this, they’re going to be capable of a lot of other really cool things, too). But there’s just so much money sitting there, and so much room for improvement over an industry that’s obviously bottlenecked on its humans, that it would be crazy for Google to pass up the opportunity it’s creating for itself.
Always having a plan ready to go. Always driving a stake in the ground. Always pushing harder, working more hours, moving faster than anyone else. Always willing to ruin other people’s careers and even lives. Getting Things Done, not because they are good or make sense but because they play well for the press and make money for the bankers and provide jobs for the unions and earn votes for the politicians, because they grease the wheels for getting yet more things done, for consolidating yet more power.
Robert Moses’ highway and housing projects grew like cancer, aggressively with no regard for the healthy functioning of the host. Where mass transit would have been cheap and provided capacity for thousands more commuters, roads brought suffocating congestion and the constant ‘need’ for more roads. Where highways could have been moved a block to route around healthy functioning neighborhoods, hundreds of homes and businesses were wiped off the map and whole sections of the city blighted. Where low-income communities could have been shored up with federal money, handouts to corrupt developers for doomed projects turned surrounding areas into full-blown ghettos far worse than what was there before.
Robert Caro’s The Power Broker delves deep into the Moses legacy that remains everywhere in New York. I live in Brooklyn not far from 3rd Avenue and the dark, dripping damp elevated Gowanus Expressway that runs above it. Driving down to the Verrazano Bridge with windshield wipers on, you see little brick buildings with struggling businesses on the ground floor and cheap apartments above tucked in among the warehouses and parking lots, and wonder about their story. Who would build that there, right under this monster road? But of course, it’s the other way around. Caro describes the scene before the expressway opened in 1941: a working-class neighborhood served by an elevated train that ran above 3rd Avenue, bringing commuter foot traffic to a lively street lined with shops, movie theaters, and restaurants. Going a block the other way, over to 2nd Avenue, led to waterfront warehouses and corresponding blight, but 3rd Avenue was the demarcation line that had held for decades. Residents pleaded for the highway to run above that already ruined avenue instead, but Moses used the 3rd Ave El to make the case that no additional right-of-way would need to be acquired – a lie, as the road was more than twice as wide as the tracks and would require exit and entrance ramps for access. As soon as the expressway was opened, the neighborhood collapsed, its people and businesses chased away by the constant roar of traffic overhead and dank shadows below.
For a brief time I lived at 107th & Amsterdam, and always wondered at the grimy few blocks out of the otherwise affluent Upper West Side that I had to hurry through dodging junkies while walking south to the 96th St subway. This area is the site of the Title I slum clearance development project known as (before it was tarred with scandal) Manhattantown, today Park West Village and the Frederick Douglass Houses. Moses condemned blocks of property worth $15 million and turned it over to politically connected developers for $1 million. Those developers proceeded to sit on the property as slumlords, raking in rent payments for years without doing any actual development save for demolition that pushed families out of their homes and left the remaining buildings surrounded by debris piles and boarded up shells which attracted rats, addicts, dealers, and prostitutes. When the developers were finally kicked off the site and the massive housing complexes that are still there today were built by another company, the previous lead investors, Seymour Millstein and Jack Ferman, were ‘punished’ with a payoff of hundreds of thousands of dollars and a 32% equity stake in the continued project.
These are only two of the stories pulled from the book, the two about places I’ve lived near, but there are so many more: a detailed account of a Bronx neighborhood destroyed by an expressway that could have just as easily moved a little bit south; the building of bridges that were intentionally too low for buses to drive under so that poor people couldn’t travel out to newly constructed parks on Long Island; the choice to cut a highway through the last unspoilt forest on Manhattan rather than take a more logical, cheaper route, because of the unfounded fear that it would be too close to an existing bridge and not earn enough tolls; the spiteful destruction of the Fort Clinton Aquarium as revenge for losing the fight to build a bridge connecting lower Manhattan to Brooklyn; a man with a heart condition berated for having the temerity to tell Moses the World’s Fair was insolvent, who days later had a heart attack and subsequently died; the constant construction of new bridges and highways, each accompanied by a promise that it would finally bring traffic under control, each and every one instantly gridlocked upon opening. The case that Caro lays out for how New York could have been better without Robert Moses is, simply, devastating.
But you put the book down less convinced that it actually *would* have been better without him. Caro details how New York state and city government prior to the rise of Al Smith and Fiorello La Guardia, who put Moses into power, was dominated by Tammany Hall machine politics, with public works projects crippled for decades by graft and incompetence and parks languishing without even the most basic upkeep. The disaster of Moses’ 1964-65 World’s Fair, which Caro argues finally destroyed Moses’ public popularity, was on par with that of Grover Whalen’s 1939-40 Fair. The mayor who finally attempted to oust Moses, John Lindsay, was a bumbling political lightweight who made a fool of himself in the process, and the governor who finally succeeded in ousting him, Nelson Rockefeller, needed a lie to Moses and a backroom deal with Chase Manhattan Bank (run by his brother) to do it. The various people who opposed Moses over his career were unable or unwilling to do the work needed to counteract him; the legislators who passed the bills Moses drafted did so out of ignorance of what those bills contained or fear of what he knew about them; the press gave him free reign for the large majority of his career, headlining his successes and ignoring his failures; the banks, unions, and developers all took his money and worked on his behalf to keep it coming; the public stupidly accepted roads as progress, parks as panacea, and the plight of others as not their problem. Given this context, this cast of alternatives, without Moses, without that single figure to lay the problems of 44 years at the feet of, would New York really be in a better place today? This isn’t to defend Moses, but to cast a wider net of blame, on our willingness to be corrupted or to tolerate corruption in others, on our deference, out of laziness or ignorance, to action, on our resigned acceptance of injustice and suffering.
From Robert Caro’s The Power Broker:
On July 15, [1936,] La Guardia had [agreed to let Moses tear down the 92nd St Ferryhouse to extend the East River Drive] – although the Mayor said that ferry service should not be stopped for sixty days so that the ferry riders would have time to find other means of transportation.
Moses was not willing to wait sixty days. Defying the Mayor, he decided to stop the service immediately – by tearing down the ferry terminal.
He ordered the contractor building the East River Drive approach, A. N. Hazell, to procure two barges and install a pile driver on one and a wrecking crane on the other. When they were ready, on July 21, he waited until the Rockaway had unsuspectingly pulled away from Manhattan for one of its early-afternoon trips to Astoria and then, without warning, ordered the barges towed into the ferry slip and lashed together there so that the Rockaway would have no place to dock when it returned. And he ordered the pile driver and the crane to pound and pull the slip to pieces. Attacking simultaneously from the land side, he dispatched crews of workmen to tear up York Avenue’s cobblestones in front of the ferryhouse to cut off all access to the terminal by land.
[Deputy Commissioner Andrew] Hudson could hardly believe what was happening. … Hundreds of regular ferry commuters, who had come to Manhattan by boat that morning, would be left stranded there – with their cars and home on the other side of the river. But when, assuming there had been some mistake, he pointed this out to the contractors and asked them to stop work until matters could be straightened out, they told him that they had orders from Moses to continue working no matter who tried to stop them – and even while Hudson was arguing with them, the pile driver continued to smash away at the dock.
La Guardia meanwhile contacted Moses and pleaded with him to call the contractors off. If the demolition stopped, he promised the Park Commissioner, he would call the Sinking Fund Commission back into session to shorten the sixty-day waiting period. Moses refused. Telephoning Police Commissioner Lewis J. Valentine, the Mayor – in a voice so choked with fury that it was barely coherent – ordered him to send a squad of patrolmen to the scene.
Expecting the contractors to yield to a direct police order, the Mayor and Valentine had instructed the officer in charge at the scene, Deputy Chief Inspector Edward A. Bracken, not to use force. But the contractors knew whose orders they would have to follow if they wanted to keep working for Triborough. When the Inspector ordered contractor Hazell to quit, Hazell said, “I’m not going to.” Moses had told him not to, he said. And the pile driver continued to smash away. By this time, much of the dock had been destroyed and the hundreds of rush-hour ferry passengers standing on York Avenue were watching the workmen on the barges pry away heavy boards that had been loosened on the rest of it. Only force would stop Moses and La Guardia finally realized it. Put through to Bracken on the telephone, the Mayor ordered the Inspector to “drag those men off the boats if they don’t quit.” Those of the workmen who didn’t drop their tools when a fifteen-man police boarding party swarmed over the side had them struck from their hands and were shoved, along with the rest, onto what was left of the dock. Within minutes, a police launch was standing alongside the barges and when a launch carrying the night shift of contractors’ men appeared, it was warned away. A city tugboat pushed the contractor’s barges away downriver. As night was falling, a procession of barges bearing piles and lumber to repair the slip and workmen worked all night under floodlights to rebuild the terminal and repave York Avenue. By morning, the Rockaway was back in service – under the protection of a squad of patrolmen – and La Guardia could tell reporters, with a smile of satisfaction, “All is quiet on the eastern front”.
But the last smile was Moses’. La Guardia waited a week for the story to fade from the front pages and then quietly had the Sinking Fund Commission transfer the terminal to Moses in another forty-eight hours. At 11:25pm, July 31, … as the old tub left for the Brooklyn pier where she was to be laid up, her captain blew three long, dolorous whistle blasts of farewell. Hardly had the last note faded when it was succceeded by dull heavy thuds – the pound of Moses’ pile driver, tearing the ferryhouse down again.
Grand visions of holiday productivity, including wrapping up all outstanding book notes, were predictably optimistic. Continuing on:
Boomerang: Travels in the New Third World by Michael Lewis explains the European financial crisis as experienced by Iceland, Greece, Ireland, Germany, and the United States. Lewis is at his best when he can focus on a few key people and develop richly constructed characters who serve as personifications of larger ideas. Here, though, with each chapter built around a single whole country, the scope of the subject and the brevity of the treatment reduces much of his human explorations to thin stereotyping. The best chapter, on Greece, illustrates the dichotomy directly, where weak potshots at the whole Greek people pepper an otherwise funny and intriguing profile of a sect of monks improbably at the center of that country’s ills. If you keep up with Lewis’s Vanity Fair writing, there’s not much new here.
Six Easy Pieces is a selection of some of the more generally accessible chapters from Richard Feynman’s Lectures on Physics, focused on the intuition over the math. Feynman has a gift for cutting through the bullshit, and here he offers the clearest, least mystical lay explanation of quantum theory that I’ve read.
CODE by Charles Petzold builds a computer starting from the underlying idea of basic code, moving from the telegraph system to electronic circuits to graphical operating systems. If computers seem like magic boxes to you, or if you need a refresher on your freshman Computer Engineering course, this is a great book, though at times it gets bogged down in details that should have been left in the manual.
One of my favorite reads of 2011 was James Gleick’s The Information, so last year I picked up Chaos from his back catalog. The book zips its way through the history and ideas of chaos theory, covering the butterfly effect, fractals, strange attractors, universality, and dynamical systems with more restraint and grounding in reality than you’d maybe expect but more hype than you’d probably like. By the time Gleick declares chaos Kuhn-tastically revolutionary, you’re ready to dive right in to another book that tells you where these ideas have actually gone in the intervening 25 years. A solid read nonetheless.
Aaron Swartz killed himself yesterday, 2 years after being arrested for illegally downloading journal articles from JSTOR on the MIT campus, and 4 months after prosecutors filed a superseding indictment that expanded the charges from four to thirteen felony counts. I didn’t know Aaron personally except for a small email exchange, but I always admired his work and spark from a distance. His loss hurts, and this post is surely in part borne out of that hurt, but the thoughts are not new.
The prosecutors in this case, Carmen M. Ortiz, Scott L. Garland, and Stephen P. Heymann, deserve to be shamed. I do not blame them for Aaron’s death; that was his own tragic doing. But I emphatically blame them for pressing these charges in the manner they did, threatening Aaron with decades in jail and millions of dollars in fines for a non-violent offense against two private parties under a law that another federal circuit, the 9th, has said should be adjudicated in civil court. JSTOR has publicly stated that their legal interest ended when they got their documents back, and the damage to MIT was a few days inconvenience. Where is the compelling public interest that spurred the government to be at all involved? What possible reading of the crime demands impoverishment and a life in federal prison for justice? The pursuit of this case by these prosecutors was, plainly and simply, disgusting.
It’s hard to decide which larger issue to focus on. Society’s witch-hunt reaction to crimes involving computers? The wrong-headed incentives that drive prosecutors? The dying industries that keep throwing money at politicians to keep these laws on the books? Surely all of these and more are a part of this conversation, but it’s all been said and will continue to be said. Right now we just sit back, exhausted, and mourn the wholly unnecessary loss of a brilliant and inspiring individual.
Rest in peace, Aaron.
I’ve fallen hopelessly behind in my book reports, so I’m going to dribble out the backlog in short rundowns by the end of the year:
The Selfish Gene by Richard Dawkins is a book that I’ve been putting off for years. The evolution “debate” has always struck me as pointless, and for whatever reason I had thought that’s what this book was about, but it’s only given a brief dismissal in an early chapter and then ignored entirely in favor of good, meaty, mind-bending capital-S Science. Dawkins posits that the gene, as opposed to the whole individual organism or the species, is the unit of evolution, and walks through this idea’s broad explanatory power while developing an intuition for game theory along the way. The 30th Anniversary edition that I read includes copious footnotes explaining how intervening research has reinforced or occasionally refuted the original text. Highly recommended.
The Social Animal is David Brooks’ attempt to explain the inner workings of “wonderfully fulfilling lives”. The book follows a fictional couple, Harold and Erica, from cradle to grave, placing them on a rhetorical treadmill where each phase of their lives occurs circa 2010. The approach serves as a sort of manipulable petri dish for the ideas and policies Brooks wants to explore: How can poor children beat the odds and become successful adults? What do the ancient Greeks have to teach us today? How does the mind work? How do relationships form and evolve? What does it all mean? We see the questions and answers play out in the lives of his characters. The scope is ambitious, but Brooks isn’t up to the task, wasting large swathes on cringe-inducing caricatures (“crude-talking, hard-partying, cotton candy lipstick-wearing, thong-snapping, balls-to-the-wall disciple in the church of Lady GaGa”), dropping lame hints at a spirituality he’s too timid to talk about directly, stumping for the return of the Whig party, or constructing odd scenarios that just ring false (one example: Harold longs to have children, but after decades of resentment at Erica’s refusal to even discuss the topic, he finds that being a camp counselor one summer is just as good). I continue to be oblivious to what people see in David Brooks.
A Mathematician’s Lament by Paul Lockhart is a short exhortation for a curriculum focused on real mathematics rather than rote mechanics. For anyone as interested in applications as theory, Lockhart’s insistence on teaching pure math solely for its own sake might be a little off-putting, but the examples of what such a curriculum might actually look like are beautiful and inspiring, and make his follow-up Measurement a must read.
The behavior and requirements of distributed data storage systems are frequently counterintuitive (eventual consistency, anyone?). One of these counterintuitive behaviors is something I call “the extra node paradox”: if you add an extra node to your cluster, you actually increase your likelihood of data loss. This follows from two simple observations:
Say you have a cluster of n nodes, with each data block replicated to r of those. Then
For reasonable configurations, any r-node simultaneous failure results in data loss.
There are only (n choose r) possible ways to replicate a data block in a cluster. This number is probably far smaller than the number of data blocks that you’re storing, which implies that if your data is evenly distributed across the available replications, any r-node loss will hit some blocks replicated to only those r nodes. To make it concrete: say you have a 20 node cluster with 3TB storage per node, a block size of 512kB, and a replication factor of 3, so that you can store 1TB (~2m blocks) per node, or about 40m blocks total. The number of unique replications available is only (20 choose 3)=1140, implying a loss of roughly 35k blocks for any 3 node failure. Holding everything else constant, if you bump the cluster size to 200 nodes, you jump to 1,313,400 unique replications, guaranteeing a loss of 30 blocks. To have any chance of not losing any of your 40m blocks, your cluster would need to have 623 nodes, each storing only ~64k blocks (~32GB). For the same data set but with larger blocks (say 64MB, the hdfs default), you would have a total of 3.125k blocks. With 20 nodes you would lose 274 blocks, and you’d need 125 nodes to have any chance of not losing data, each storing only ~2.5k blocks (~162GB).
As n goes up, so does the probability of at least r nodes failing simultaneously.
By analogy, if you flip 2 coins and fewer than 2 land on heads, you’re not very surprised, but if you flip 50 coins and fewer than 2 land on heads, you are. If you have more nodes, there are more nodes that can fail, and so more will (read up on the binomial distribution if you need to convince yourself).
The ‘paradox’ is that if you’re considering the impact of adding an extra node on your chance of losing any given block, that probability goes down – you’re getting an increasing overall likelihood of data loss from a group of blocks that are individually growing less likely to be lost.
Finding the actual probability of a simultaneous r-node failure in a real-world system is complicated by the fact that ‘simultaneous failure’ actually means ‘within the window of time when the data from the first failed node is being redistributed to good nodes’, but it doesn’t fundamentally change the conclusion. The main takeaways from this are that you can’t stop worrying about single-node reliability just because you’re distributed, and that the actual level of safety you get from a given replication factor is sensitive to the size of the cluster.
I’ve been hunting for a good little history of the world, a quick read that I can pick up every few years to get a reminder of the sequence of it all. To that end, E.H. Gombrich’s A Little History of the World has the title exactly right. It turns out that it’s aimed at children, but given that the list of books I want my future kids to read is heavily biased towards fiction right now (The Phantom Tollbooth, the Wrinkle in Time series, the Chronicles of Narnia, etc.), I thought I’d give it a chance to see if it could make the cut.
Unfortunately, though, the book falls short of what I want in many ways. Despite its title, it isn’t really “of the world”, it’s “of Europe from an Austrian’s perspective”. While Gombrich dedicates a few chapters to India and China in early history, the East is shelved from the birth of Christ until European colonialism brings it back into the picture. North America makes nothing more than a small cameo appearance, and South America and Africa outside of Egypt are both ignored almost entirely.
Worse, Gombrich focuses rather narrowly on the sequence of religions, rulers, wars, and empires that shaped the Continent. Science is wholly represented by nameless cavemen, Leonardo da Vinci, an account of Galileo in which math is equated with magic, one mention of Niels Bohr in the afterword, and vague references to technology and progress. None of Pythagoras, Archimedes, Euclid, Copernicus, Kepler, Newton, Descartes, Euler, Darwin, Maxwell, Einstein, or others even merit a namecheck, while the story of the Reformation goes deep enough to include such household names as Jan Hus and Huldrych Zwingli. I can’t deny the impact of war and religion, but any book that uses more ink to romanticize those who worked so hard at tearing the world down than to even just acknowledge those who have built it up is not one that I want to use as the foundation of my kids’ understanding of history.
That said, the book does have a lot of good things going for it. While you never forget that it’s aimed at children, it’s well written and not afraid to touch on challenging ideas. There are genuinely nice overviews of the founding stories of some of the major world religions, thanks at least in part to Gombrich’s revisions with the help of his son, a preeminent scholar of early Buddhism. And I don’t mean to imply that a strong European focus is inherently bad – as long as you realize that’s what you’re getting, it’s perfectly fine, and if you don’t know your Visigoths from your Ostrogoths, your Guelphs from your Ghibellines, or your Babenbergs from your Habsburgs, this book will do a nice job of catching you up.
In Daniel Kahneman’s Thinking, Fast and Slow, the mind is divided into two systems. System 2 is the deliberate serial thinking process which we commonly regard as our self, and System 1 is the automatic parallel reacting process which makes up much more of us than we generally realize. System 1 is responsible for the first assessment of any information that comes in, most of which will be filtered out or handled without System 2 ever getting involved. When System 2 does come into the picture, it’s slow and lazy, frequently only giving a cursory assessment to System 1′s preference before confirming it. Most of the time this is fine – in fact, a key trait of expertise is that System 1 becomes adept at making these first decisions – but System 1 also has characteristic biases that this book explores in fascinating detail.
A principal bias that Kahneman describes is ‘WYSIATI’: what you see is all there is. WYSIATI is the “remarkable asymmetry between the ways our mind treats information that is currently available and information that we do not have”. System 1 is “a machine for jumping to conclusions”, forming opinions from information that’s at hand without stopping to consider what other information might be needed to actually justify those opinions. Some of the effects of WYSIATI include being overconfident in cases where we may be missing critical information, regarding the same information differently depending on how it is presented, and neglecting base rates when examples are readily available.
This idea appears repeatedly throughout the book, and where it isn’t explicitly summoned it’s often easy to see lurking in the shadows. The ‘anchoring effect’ describes how we latch onto numbers that are in front of us when trying to estimate quantities, even if we know that those numbers are completely random. The ‘availability heuristic’ answers questions about an event’s frequency or significance by simply gauging how easily instances come to mind (an example of ‘substitution’, our tendency to avoid hard questions by answering easier ones in their place). And ‘hindsight bias’ leads us to “assess the quality of a decision not by whether the process was sound but by whether its outcome was good or bad”. When our response ought to be “I don’t know”, System 1 comes up with an answer anyways, and System 2 often just simply goes with it.
Kahneman won the Nobel Prize for his development (with Amos Tversky) of prospect theory, and he dedicates several chapters to explaining the subject and its implications. Prospect theory is a critique of expected utility theory, which was developed to explain why rational decision makers might select a sure thing over a bet that has a larger expected value. For instance, we might prefer $100 over a 30% chance at $1000, despite the latter having a higher expected value of $300. If we choose the natural logarithm as the basis of our expected utility function (other functions can work, too), the expected utility of $100 is ln(100)*1 = 4.61, while the expected utility of a 30% chance at $1000 is ln(1000)*0.3 = 2.07. If we’re attempting to maximize utility, the choice of the sure thing over the gamble is clearly justified in this scenario.
Prospect theory observes that this model of decision making is incomplete in that it neglects the reference point of the decision maker. From different reference points, the same payout looks like either a loss or a gain, and we’re more averse to loss than we are to risk: when faced with a potential loss, we frequently become risk-seeking. Going back to our example of the choice between $100 and a 30% chance at $1000, prospect theory observes that a person starting with nothing may actually see the bet as a potential loss of the $100 they were otherwise guaranteed. In contrast, a person who already has the $1000 in hand perceives the certain option as a loss of $900, and is more likely to take the gamble despite its lower utility.
The implications of loss aversion are significant. The ‘endowment effect’ describes our decreased willingness to trade something we have for something we don’t, even if when we lacked both items we would have considered the second greater in value than the first. We work harder to avoid failure than we do to exceed expectations. Credit card companies seek legislation that requires differential pricing on cash and credit transactions to be called “cash discounts” rather than “credit surcharges”, because we’re more willing to accept forgone discounts than pay a surcharge – we make inconsistent decisions when equivalent scenarios are framed as a loss versus as a gain.
The last section of the book focuses on the distinction between the ‘experiencing’ and the ‘remembering’ selves. In one experiment, subjects who had to go through a painful medical procedure were asked at regular intervals during the procedure how much pain they felt at that moment. After the procedure was complete, they were asked to rate the total amount of pain they had experienced. The value that people assigned to this final question did not correspond to the sum of values they had assigned to the questions during the procedure; instead, they followed what Kahneman calls the ‘peak-end rule’ – their rating corresponded to an average of the peak level of pain during the procedure and the level of pain right at the end. In addition, the length of the procedure had no impact on the rating of total pain, a phenomenon called ‘duration neglect’. Our remembering selves punish our experiencing selves by causing us to make choices that lead us to suffer more in the moment than we’ll remember afterwards.
Very little is said about the actual mechanisms for all of this. Kahneman stresses that System 1 and System 2 do not correspond neatly to specific parts of the brain or body, but are instead rhetorical shorthand for complex interactions that manifest themselves as behaviors that can be observed via experiment. This decision to focus on observable behaviors is much appreciated, as it sidesteps the need for the Anatomical Latin laundry lists that are annoyingly common in psychology books aimed at the general public. Avoiding impenetrable anatomy recitations isn’t the only way that this book is better than its shelfmates. Where other books try to punch things up with jokes or hackneyed narrative, Kahneman keeps us engaged with concise and insightful discussion. Compare this to Dan Ariely’s Predictably Irrational, which covers much of the same ground but includes so much ‘entertaining’ filler that it feels thin and condescending. Kahneman trusts his audience enough to avoid doing this, and the result is a rich and rewarding read that I highly recommend.