Coders: The Making of a New Tribe and the Remaking of the World review

Coders: The Making of a New Tribe and the Remaking of the WorldCoders: The Making of a New Tribe and the Remaking of the World by Clive Thompson

My rating: 4 of 5 stars


This was a very comprehensive look at what it’s like to be a coder – I definitely identified with a lot of it! But the book doesn’t shy away from the downsides of big tech. Overall I’d recommend it!

I didn’t take detailed notes, but a few things that struck me:
– They did one of those studies where they send resumes to companies, some of which have names and some of which don’t, but the rest of the resume is identical. Without names, 54% of the resumes were chosen to have an interviews; when women’s names were added, only 5% were. That is atrocious! (pg 24, citing this CNET article)
– There’s a part about a so-called “rockstar” coder named Rick (not his real name) who churned out a ton of code and it went to his head, as h started thinking he was the only one good enough to work on the project. Anyway, he kept missing deadlines and it turns out his code was nigh unusable due to lack of documentation and whatnot. Once he left, a team took over, and ended up with code that was 20% the size of the original and it worked better, too. Let me just say this is another part of the book I identified with… (pg 165)
– There’s another section about the tech industry’s proclivity for libertarianism, but Thompson argues this is a bit overblown. In 2016 Hillary Clinton got 60 times the amount of donations as Trump from Silicon Valley residents. Even polling tech CEOs had them mostly disagreeing with libertarian ideas like “the government should do nothing but national defense and policing” and agreeing with things like single-payer healthcare. The one big alignment was agreeing that the government shouldn’t be regulating businesses, which isn’t a big surprise… (pg 174, the CEO polling is from this paper)


View all my reviews

The Culture Map: Breaking Through the Invisible Boundaries of Global Business review

The Culture Map: Breaking Through the Invisible Boundaries of Global BusinessThe Culture Map: Breaking Through the Invisible Boundaries of Global Business by Erin Meyer

My rating: 4 of 5 stars


This is an interesting look at the differences between cultures in different countries and, by extension, the people from there. Culture is a big factor in how people behave (bigger than most people believe, I think!), but I appreciate that Meyer emphasizes that people are individuals and seems to try to avoid stereotyping people.

I had a tiny existential crisis while reading this book. It seems the most useful if you’re traveling for business, and some parts specifically reminded me of my trips to India for National Instruments. But I’m getting older and especially now that I have kids two or three week business trips don’t seem to be in my future anymore. But this is kind of dumb, because my team at Mozilla has people from counts 5 different countries!

Anyway, Meyer actually has a comprehensive country mapping tool on her website (not free, though), but here are some things I found interesting:
– I was sold on this book by page 16 where Meyer talks about the “half-shake, half-nod of the head” that’s characteristic to India. I ran into this all the time when I traveled there and people would do this when I was talking to them and it really threw me for a loop! It didn’t take long to figure out what it meant (interest in what you’re saying), but even after being there for weeks my brain still interpreted it as “ack, they’re disagreeing with me” and it was very hard to keep talking!
– The system Meyer created has eight different scales. One of the more interesting ones is “low-context” versus “high-context” communication. The US culture has very “low-context” communication, meaning that people assume that others won’t have much shared context and therefore are pretty explicit about any background knowledge, etc. Countries like Japan (and India!) have “high-context” communication, meaning communication is much more implicit. (pg 32)
– Meyer gives an example of a high-context culture in Iran – if a visitor arrives at 10 PM at your house, you should ask them three times if they want something to eat before bed. It would be considered very rude to answer “yes” the first time someone asks if you want something. As an American this sounds exhausting! (pg 33)
– French is a higher-context language than English. There are apparently seven times more words in English than in French, which suggests that French needs more context to have the same range of meaning as English. I’m not 100% sure I buy this but it is an interesting way of looking at it! (pg 34)
– Related to low versus high context is whether negative feedback is given directly or indirectly. (the US is unique in that our communication is low-context, but negative feedback is indirect, which are kind of at odds with each other!) Meyer gives an example of feedback that her eight-year-old kid got from a teacher in French: “8 errors. Skills not acquired. Apply yourself!” which is so blunt that it made me laugh! (pg 62)
– Meyer talks about how countries where Protestant religions are more popular tend to be more egalitarian than countries where Catholicism is more popular, since the Catholic church is more hierarchical than Protestant religions. Meyer herself says this is a “dramatic oversimplification”, which I gotta say I agree with… (pg 97)
– The book talks about Kurt Lewin’s “peach versus coconut” models of personal interaction. The US is a “peach” culture, where people are friendly (“soft”) with people they’ve just met, but after a little bit of friendly interaction you get to the hard shell of the pit and it’s hard to get to know them. Many European cultures are “coconut” where people are more closed (like the shell of a coconut!) to people they don’t know, but once you get past the shell they open up; relationships build up slowly but last longer. This is one of those things where I feel the US culture in my bones, even if I do see some advantages to being a coconut. (pg 128)



View all my reviews

How Infrastructure Works: Inside the Systems That Shape Our World review – excellent book!

How Infrastructure Works: Inside the Systems That Shape Our WorldHow Infrastructure Works: Inside the Systems That Shape Our World by Deb Chachra

My rating: 5 of 5 stars


I loved this book! I’ve always been interested in infrastructure in a “isn’t that neat!” sort of way, and in reading post apocalyptic books about what happens when infrastructure goes away. This book doesn’t have a lot of nuts-and-bolts information about different kinds of infrastructure (although there is some!), but it talks about about what makes something infrastructure, why we should care about it, and what we can do to make it better. If you’re at all interested in infrastructure and society, I can’t recommend this book enough!

Here are some odds and ends I found interesting:
– Before Britain controlled India, people have estimated India’s share of the world’s economy was around 25 percent. After India gained its independence from Britain, it was down to 4 percent!! (pg 130) This is one of those times where I feel a little smug that the US has done a lot of bad things but at least we weren’t huge colonizers (with the notable exception of the Native Americans, obviously). In fact, Chachra points out that the 60 or so countries that celebrate their independence from British probably makes it the most widely observed secular holiday in the world!) (pg 136)
– Chachra points out that inspections and maintenance are important parts of infrastructure, but of course they’re not as exciting as building new stuff. (pg 174) I kind of relate to this – I used to be more excited about building new apps and projects and websites, but as I get older I’ve learned that keeping old things working can be just as satisfying!
– The colors of those little flags in the ground indicate what kind of pipe is underground: blue is potable water, green is sewage, red is electricity, orange is communication, yellow is natural gas, and hot pink is for “temporary markings” (pg 6)
– One of the dramatic changes as electricity became more widely available is the increased prevalence of light, which is something I hadn’t thought a lot about. In fact, New England today uses about a hundred times more light now than in 1888! (pg 26)
– Before the Civil War, trains in the North used “standard gauge” track (4 ft 8.5 in apart), while trains in the South used “broad gauge” track (5 ft apart). After the war, as trade increased, they decided to standardize on standard gauge track, and in 1886 all the broad gauge southern track was changed to standard gauge in a span of 36 hours! It took tens of thousands of workers pulling up rails and moving them slightly closer to each other! (pg 56)
– In Great Britain in the 1700s, navigators used the official time set by the Royal Observatory in Greenwich (which they needed to calculate longitude), but every place on land set their time independently based on when the sun was at the highest point in the sky. In 1840, railways started to use their own standardized time for train schedules and whatnot, which they kept track of by hand carrying chronometers on the trains. And 15 years later, the Royal Observatory started sending out the time by telegraph! (pg 68)
– Chachra talks about Dinorwig Power Station (commonly known as “Electric Mountain”), which is a hydroelectric power plant but also has pumped storage. Basically, it can store energy by pumping water to the top of a shift to a lake on top of a mountain, and it can harvest that energy by letting it fall back down to a lake on the bottom (and have it run through a turbine). It was built in the 1970s and can store 9.1 GWh of power! (pg 92)
– In the late 1990s, if lots of people in the UK were watching the same thing on TV, when that show or game ended many people would get up and plug in an electric kettle to make tea, which caused a spike in electricity usage! This was known as “TV pickup”, and operators at power plants could anticipate this and have more power ready as soon as the show ended. (pg 93)
– Chachra makes the point that she could go off the grid and have her own water supply, septic system, solar panels, etc. But this would mean she’d be responsible for operating and maintaining all of these, and in a real sense she would have less freedom in her life, not more. (pg 100)
– After recent hurricanes, more people in the US have died of carbon monoxide poisoning (from emergency generators) than from storm surges and flooding! (pg 102)
– Chachra points out that in the US we’re pretty good at providing “public goods” in the economic sense, meaning things that have a small marginal cost to add more people to (things like roads, water systems, and roads). But we’re pretty bad at things that have high social value but are not “public goods” in the economic sense, like food and housing. (pg 109)
– Chachra also mentions that as infrastructure systems such as water, sewage, gas, and electricity spread in the late 1800s and early 1900s, this reduced the burden especially on women, and it may not be a coincidence that this is when the women’s suffrage movements grew in parallel with these. (pg 114)
– People understood that widespread electricity availability was good for everyone, because it meant a lower risk of fires as well as less local pollution from burning things for light and heat. (pg 117)
– Solar storms are bad news – somehow I didn’t realize that a 1989 blackout in Quebec was caused by one! (pg 152)
– Locating buried infrastructure is tricky enough that there’s an International Utility Locate Rodeo! (pg 163)
– Chachra mentions the Austin boil-water notice in 2018 – I’m not sure I ever realized it was due to the heavy flooding that overwhelmed the treatment plant. (and apparently it was the first time Austin had a boil-water notice!) (pg 186)
– Our kids will hopefully live to see the twenty-second century, which is both obvious and mind-boggling to me. (pg 214)
– Heavy trucks (like 18-wheelers, etc.) are 1% of vehicles but contribute 25% of transportation emissions! Yikes. (pg 231)


View all my reviews

The Software Engineer’s Guidebook review – very wide and very shallow

The Software Engineer's Guidebook: Navigating senior, tech lead, and staff engineer positions at tech companies and startupsThe Software Engineer’s Guidebook: Navigating senior, tech lead, and staff engineer positions at tech companies and startups by Gergely Orosz

My rating: 3 of 5 stars

This book is several miles wide and an inch deep.

The most useful/interesting part for me was how other companies tend to work with promotions and titles and whatnot. Since I’ve only worked at two tech companies I have a real lack of perspective here, and Orosz walks through a lot of differences between small startups, mid-size companies, and the tech giants.

I could see this as being useful as a jumping-off point to learn more about insert topic here – the book really does cover a ton of stuff, and sometimes you just need to know the right phrases to search for to learn more.



View all my reviews