Listened Ep. 129 Clive Thompson from

Clive Thompson explains how the values of code become the norm, and how some coders are successfully avoiding the Lust for Scale.

Clive Thompson and Douglas Rushkoff reminisce about the early days of coding when it was more akin to origami. Thompson argues that scale and efficiency created by the venture capital model breaks the social system. This produces a focus on measurement and engagement, A/B testing, over humans and representation. It is interesting to consider this alongside Thompson’s previous book Smarter Than You Think. The challenge we have is to move away from the magic of coding and automation, the focus on coding as a career.
Replied to Leestijd met Team Human en Coders by Frank Meeuwsen

Vandaag kwamen er twee nieuwe boeken binnen waar ik graag in ga beginnen!

I recently finished reading Team Human. Although I should not be surprised, but I found it less about technology (what I have come to expect from Rushkoff) and more about the capacity of humans. In some respects it feels like a modern day book of meditations.

I have started reading Coders. I had read Thompson’s post on women and learning to code, but like yourself bought the book on reputation. Am loving it so far. He really his a knack of telling a story.

Bookmarked Ten Lessons I Learned While Teaching Myself to Code (The Blog of Author Tim Ferriss)
In light on Clive Thompson’s new book, he reflects on the ten lessons associated with learning to code:

  1. The online world is your friend. Start there.
  2. Don’t stress over what language to pick.
  3. Code every day.
  4. Automate your life.
  5. Prepare for constant, grinding frustration.
  6. Build things. Build lots of things.
  7. “View Source”: Take other people’s code, pick it apart, and reuse it.
  8. Build things for you—code you need and want.
  9. Learn how to learn.
  10. Reach out to other coders.

Two points that stood out to me from Thompson’s was coding every day and doing so with purpose. I have been doing quite a bit with Google Sheets lately. I find myself needing to relearn things after leaving things for a few weeks. Repetition is important.

I was also reminded of Richard Olsen’s post on why coding is the vanguard for modern learning.

Replied to

Opps, forgot to pre-order, but just purchased it if that helps 🤷‍♂️
Enjoyed the extracts so far so excited to read the full book.
Liked We Might Be Reaching ‘Peak Indifference’ on Climate Change (WIRED)

The current political moment is incredibly interesting. Anyone who wants to deal with climate change may have only a brief window to sell the public on a plan. In his new book The Uninhabitable Earth: Life After Warming, the writer David Wallace-­Wells talks about the value of panic to pushing collective action; Doctorow says it’s the point “where you divert your energy from convincing people there’s a problem to convincing them there’s a solution.”

Bookmarked The Secret History of Women in Coding (

Computer programming once had much better gender balance than it does today. What went wrong?

In an article adapted from “Coders: The Making of a New Tribe and the Remaking of the World,” Clive Thompson breaks down the gender divide when it comes to coding. He profiles the early journeys of Mary Allen Wilkes and Elsie Shutt. This is contrasted with the current context of a male dominated space. He explores a number of reports, practices and policies that led to the transition from these early years to today, as well as attempts to push back on this.


Once the first generation of personal computers, like the Commodore 64 or the TRS-80, found their way into homes, teenagers were able to play around with them, slowly learning the major concepts of programming in their spare time. By the mid-’80s, some college freshmen were showing up for their first class already proficient as programmers. They were remarkably well prepared for and perhaps even a little jaded about what Computer Science 101 might bring. As it turned out, these students were mostly men, as two academics discovered when they looked into the reasons women’s enrollment was so low.

What Margolis heard from students — and from faculty members, too — was that there was a sense in the classroom that if you hadn’t already been coding obsessively for years, you didn’t belong. The “real programmer” was the one who “had a computer-screen tan from being in front of the monitor all the time,” as Margolis puts it. “The idea was, you just have to love being with a computer all the time, and if you don’t do it 24/7, you’re not a ‘real’ programmer.” The truth is, many of the men themselves didn’t fit this monomaniacal stereotype. But there was a double standard: While it was O.K. for the men to want to engage in various other pursuits, women who expressed the same wish felt judged for not being “hard core” enough. By the second year, many of these women, besieged by doubts, began dropping out of the program. (The same was true for the few black and Latino students who also arrived on campus without teenage programming experience.)

By the ’80s, the early pioneering work done by female programmers had mostly been forgotten. In contrast, Hollywood was putting out precisely the opposite image: Computers were a male domain. In hit movies like “Revenge of the Nerds,” “Weird Science,” “Tron,” “WarGames” and others, the computer nerds were nearly always young white men.

If biology were the reason so few women are in coding, it would be impossible to explain why women were so prominent in the early years of American programming, when the work could be, if anything, far harder than today’s programming. It was an uncharted new field, in which you had to do math in binary and hexadecimal formats, and there were no helpful internet forums, no Google to query, for assistance with your bug. It was just your brain in a jar, solving hellish problems.

Changing the culture at schools is one thing. Most female veterans of code I’ve spoken to say that what is harder is shifting the culture of the industry at large, particularly the reflexive sexism and racism still deeply ingrained in Silicon Valley. Some, like Sue Gardner, sometimes wonder if it’s even ethical for her to encourage young women to go into tech. She fears they’ll pour out of computer-science programs in increasing numbers, arrive at their first coding job excited and thrive early on, but then gradually get beaten down by industry. “The truth is, we can attract more and different people into the field, but they’re just going to hit that wall in midcareer, unless we change how things happen higher up,” she says.

Replied to Remembering the past through photos by an author (Doug Belshaw’s Thought Shrapnel)

A few weeks ago, I bought a Google Assistant-powered smart display and put it in our kitchen in place of the DAB radio. It has the added bonus of cycling through all of my Google Photos, which stre…

This reminds me of Clive Thompson’s discussion of memory in his book Smarter Than You Think. From memory his discovery is that our memory is never as good as we think:

Our brains are remarkably bad at remembering details. They’re great at getting the gist of something, but they consistently muff the specifics. Whenever we read a book or watch a TV show or wander down the street, we extract the meaning of what we see—the parts of it that make sense to us and fit into our overall picture of the world—but we lose everything else, in particular discarding the details that don’t fit our predetermined biases. This sounds like a recipe for disaster, but scientists point out that there’s an upside to this faulty recall. If we remembered every single detail of everything, we wouldn’t be able to make sense of anything. Forgetting is a gift and a curse: by chipping away at what we experience in everyday life, we leave behind a sculpture that’s meaningful to us, even if sometimes it happens to be wrong.Page 28