Chapitre 1
When Machines Speak Our Language: The Digital Transformation We Can't Ignore
In a world increasingly dominated by algorithms, John Maeda's "How to Speak Machine" arrives as both a warning and an invitation. Published in 2019, this book has quickly become required reading in Silicon Valley boardrooms and design schools alike, with tech luminaries from Jack Dorsey to Satya Nadella citing its influence. What makes this work particularly compelling is Maeda's unique position at the intersection of technology and design - having served as president of Rhode Island School of Design while simultaneously being deeply embedded in the tech world through roles at MIT Media Lab and venture capital firm Kleiner Perkins.
The book's cultural relevance has only grown as artificial intelligence has moved from specialized research labs to our everyday devices. While many technological primers focus on coding syntax or hardware specifications, Maeda instead offers something far more valuable: a conceptual framework for understanding the fundamental nature of computational thinking itself. In a digital landscape where the average person interacts with hundreds of algorithms daily without understanding their inner workings, Maeda's accessible exploration of how machines "think" has become essential knowledge for anyone hoping to navigate our increasingly automated world.
Chapitre 2
The Infinite Loop: How Computers Think Differently Than We Do
At their core, computers excel at something humans find exhausting: perfect, tireless repetition. While we inevitably fatigue, machines can execute the same task billions of times without complaint or error. This fundamental difference shapes everything about how computational systems operate and evolve.
I first discovered this power of loops in 1979 on a Commodore PET computer. My friend Colin showed me a simple two-line program that printed his name infinitely across the screen. This revelation led me to create a billing program for my mother's tofu shop, laboriously typing 365 separate input routines-one for each day of the year. When my math teacher later introduced me to FOR...NEXT loops, I realized my 14,600 lines of code could be reduced to just 50. This humbling experience taught me that thinking in loops-the computer's native language-transforms manual labor into elegant automation.
Unlike physical machines with visible components, digital machines operate invisibly through "bits" or "zeroes and ones." What we see on screen is merely a representation, not the actual computational machine-like a fast-food drive-thru sign connected to the hidden restaurant. Program code is like a recipe, while software is the cake that comes alive inside the machine.
This invisible computational realm is what science fiction author William Gibson called "cyberspace"-a "consensual hallucination" of "unthinkable complexity" existing in the "nonspace of the mind." Understanding this invisible dimension is essential to truly speaking machine.
The most elegant form of repetition in computing is recursion-defining something in terms of itself. Consider the Mobius strip, a paper loop with a single twist that creates a surface with only one side. In programming, recursion means a function calling itself, creating potentially infinite depth with minimal code. The GNU Project name exemplifies recursion as it stands for "GNU's Not Unix"-an infinite self-referential definition. Unlike regular loops that function like assembly lines, recursion elegantly expresses complex concepts in compact form. Programmers appreciate this as a form of poetry-building enigmas into working machinery.
While loops are powerful, they're also fragile. When computation encounters an error, it stops instantly and catastrophically-the entire computational world vanishes. This is why computers sometimes freeze without warning, causing "computer rage." For programmers, this is like watching thousands of carefully placed dominos fall in sequence until one misplaced piece causes complete failure. Behind every computer screen lies an invisible world of digital information being processed through endless loops-and we must be prepared for the occasional "moth" left by a fellow human being at the most inopportune moment.
Chapitre 3
The Exponential Reality: Why Computational Growth Defies Intuition
The lily pad riddle perfectly illustrates how our minds struggle with exponential growth. When lily pads double daily and cover a pond by day thirty, most incorrectly guess the pond was half-covered on day fifteen. The correct answer is day twenty-nine-the day before full coverage. By day fifteen, we're only at 16,384 lily pads-just 0.003% of the final 536,870,912. We don't reach even 1% until between days twenty-three and twenty-four.
This counterintuitive result demonstrates the difference between exponential and linear thinking. We're naturally wired for linear thinking-steady, incremental growth like plants growing gradually each day. Exponential thinking, which governs the computational world through Moore's law and loop structures, is more like multiplication than addition-creating leaps rather than increments.
Nested loops create exponential power in computing, similar to how dimensions expand space. Just as drawing a cube on paper creates the illusion of three-dimensional space, loops inside loops create new computational dimensions. When we move from a 10mm line (one dimension) to a 10mm square (two dimensions), we jump from 10mm to 100 square mm. Moving to three dimensions gives us 10,000 cubic mm-an exponential increase with each dimensional shift.
In code, placing a loop inside another loop creates this dimensional expansion. For example, nesting loops for years (10), months (12), and days (30) generates 3,600 iterations-like extending a line into a plane, then into a rectangular solid. There are literally no limits to how far each dimension can extend or how many dimensions can be conjured up, opening spaces far larger than our physical neighborhoods or cities.
Computation has a unique affinity for infinity, easily manipulating both the infinitely large and infinitely small. Consider fractals like the Koch snowflake, which demonstrates recursion by repeatedly replacing line segments with smaller replicas of the original pattern. Remarkably, the Koch snowflake has an infinite perimeter but finite area-impossible in the physical world but natural in computation.
The danger comes when spending too much time in the computational world damages human relationships-people seem trivial compared to the absolute compliance and infinite scale of computers. Technology brings both good and evil-like Nobel's dynamite or nuclear technology. Today, when computing impacts everyone's daily micromovements at global scale, we urgently need to speak both machine and humanism to navigate the complex implications of our complicated systems.
Chapitre 4
The Living Machine: When Algorithms Begin to Mimic Life
Biology taught me that life is identified by its reaction to stimuli. Movement is our first clue something is alive, and we instinctively connect motion with living things. While we can't yet be completely fooled by robots into thinking they're alive after close inspection, the line is blurring rapidly.
Interactive technologies of the past were simpleminded and slow, but today's computers respond so quickly they seem not only alive but smarter than us. The faster something responds, the smarter we perceive it. These computational "zombies" concern us because we'll never win arguments with them, and it's increasingly difficult to distinguish them from humans.
Joseph Weizenbaum, my MIT AI professor and inventor of the Eliza program in the 1960s, created the first computer program to simulate conversation convincingly enough to fool students. Eliza used "symbolic computation" with IF-THEN statements to process language by either repeating words as questions or triggering templated responses based on keywords. The program could simulate listening by referring back to previous statements, creating validating conversations that made people feel heard.
Weizenbaum, who fled Nazi Germany as a child, was troubled by his invention and spent years warning about computational dangers rather than profiting from it. He predicted computers would eventually impersonate humans by knowing everything about them. Three barriers to this prediction have now fallen: smartphones collect personal information, cloud systems observe our behaviors, and artificial neural networks process this information more effectively than symbolic computation.
Neural networks, once abandoned in the 1960s, were revived thanks to graphics processing units (GPUs) originally designed for gaming. Unlike symbolic computing with logical code steps, neural networks use interconnected neuron-like elements that "learn" patterns through numerical relationships between inputs and outputs-similar to how muscles learn sports through practice rather than conscious steps. This "deep learning" approach teaches computers to think by observing behavioral patterns rather than following IF-THEN rules.
I compare traditional AI to French bread made with natural yeast (pain au levain) versus neural networks as bread made with chemical yeast (pain a la levure). Both satisfy basic needs but differ fundamentally. The old AI had a distinctive "smell"-you could tell it was robotic. The new AI is "automation on steroids" as Andrew Ng puts it, not sentient but a tireless zombie that excels at mimicking human behavior based on patterns.
Artists see beyond the surface to understand the essential core of things. The artist's ability to hold both foreground and background simultaneously in their thinking creates unexpected connections. I experienced this at RISD's Nature Lab when a student showed me butterfly wings under a microscope, revealing feather-like scales rather than powder. Similarly, my collection of Conus textile shells displays patterns resembling Stephen Wolfram's "Rule 30" algorithm, suggesting surprising links between organic reality and computational patterns. This algorithm, which transforms rows of numbers through simple rules, creates complex patterns that mirror natural forms, raising profound questions: Does nature speak machine? Can machines speak nature? Are we just machines?
Chapitre 5
The Incomplete Product: Why Digital Design Defies Perfection
Software developers use peculiar terminology like "agile," "lean," and "scrum"-all describing a philosophy of shipping incomplete products followed by continuous revisions, rather than attempting perfection.
Traditional "waterfall development" follows a linear process from requirements to design, implementation, testing, and maintenance-like building a physical product. But this approach can lead to absurdities, like car designs with fax machine compartments that became obsolete before production.
Digital products enjoy the business advantage of "marginal cost close to zero"-there's no financial downside to producing additional copies, no inventory management, and no distribution costs. This computational property means companies can lower development costs by never shipping "finished" products, instead continuously improving them through remote monitoring and updates.
In the computational age, speed defines quality-"good" means how quickly features reach users and become useful. Products imperceptibly improve daily through incremental changes compounded over time, enabled by cloud connectivity that allows any networked device to be refreshed and synchronized.
This makes pursuing "timeless design" irrelevant. What matters is being timely, evolving in real time, and finding satisfaction in perpetual obsolescence. Unlike traditional planned obsolescence that generates waste, software's intrinsic property is being "always obsolete" with minimal environmental impact.
Traditional design lives in physical objects-antique chairs, Swedish flatware, leather cases-not in the cloud. Museums and galleries worship these objects in what I call the "Temple of Design," a cartel of institutions that decree what constitutes great design.
But this hierarchy is falling to data-gathering networks and rational-minded outsiders. Silicon Valley's financial capital combined with widely available computational power means quality design can be democratized at low cost through electronic devices. You need never be "out of style" when computational products continuously update.
For computational product designers, success means lowering standards and embracing "MVPs"-minimum viable products. Rather than pursuing perfection, you reduce grand ideas to bare-bones forms that barely resemble your vision. The goal isn't creating something perfect but something appropriate for early-stage testing.
The beauty of delivering unfinished products is continuous improvement. Unlike traditional design that aspires to finished perfection, computational design evolves constantly. This is why the Temple of Design initially rejected web design-it prevented achieving their standards of perfection. They're waiting for technology to stop changing, but that's not happening.
Chapitre 6
The Instrumented World: How Machines Watch and Learn From Us
On my desk sits a pile of iron bells from my parents' tofu shop-simple mechanical telemetry that alerted us when customers entered despite the noisy manufacturing area. This low-tech sensing capability symbolizes the power of telemetry that extends back to 19th-century France, where scientists transmitted snow depth data from Mont Blanc to Paris.
Unlike those one-way sensors, today's internet enables high-speed two-way communication. This requires constant "handshakes" between devices to ensure reliable data transmission, meaning each device must listen to and learn from the other. Once your device connects to a network, software can send information back to its manufacturer-like crash reports that help improve products.
This connectivity means anything you do online can be observed. Cloud-based services through web browsers can telemetry 100% of your activity to remote servers, giving companies a kind of "telepathy" about user behavior. They don't just collect explicit feedback but can infer meaning from your actions-how long you linger on images or when you abandon partially completed fields.
The Japanese concept of omotenashi-anticipatory hospitality-exemplifies how knowing customers enables superior service. In Japan's precise train system, this customer-centric philosophy contrasts with unreliable public transportation elsewhere. True omotenashi involves anticipating needs without asking, like the legendary tea server who provided three perfectly timed cups to a thirsty warrior-first a large lukewarm cup, then a hotter half-cup, finally a small exquisite cup with piping hot tea.
Online, this manifests when websites greet you by name, but becomes uncomfortable when unfamiliar sites know too much about you. This tension between convenience and privacy defines our computational era-we constantly trade personal information for better service.
With billions of smartphones being unlocked over a hundred times daily, the volume of data generated justifies the term "big data." Modern computational systems can analyze trillions of data points through simple nested loops that sift through information from all devices connected to cloud servers. Data scientists-dubbed "the sexiest job of the twenty-first century" by Harvard Business Review-must not only code but communicate insights through compelling data storytelling.
Instrumented systems excel at testing ideas in real-world conditions. Rather than deploying a single solution, we can simultaneously test variations to determine which performs best-like attaching different fishing lures to see which catches most fish. This iterative approach reduces risk and improves product design through compounding gains. The math is compelling: improving by just 1% daily compounds to a 37.8-fold improvement annually, while 2% daily improvements yield an astounding 1,377-fold gain.
Chapitre 7
The Automated Imbalance: How Technology Amplifies Inequality
The tech industry's systemic imbalance perpetuates itself through optimization for "culture fit"-hiring people "just like us" to reduce onboarding friction and maintain harmony. This creates monocultures where people think alike and come from similar backgrounds, often favoring graduates from the same handful of universities and those with similar socioeconomic experiences. The pressure to move fast and scale quickly frequently overshadows diversity considerations, resulting in homogeneous teams that can inadvertently embed their shared blind spots into products affecting millions.
Unlike traditional industries where mistakes might impact hundreds or thousands, tech's errors scale at computational speeds-an "oops" can affect millions instantly across global platforms. Amazon's AI hiring tool that demerited women's college graduates became a cautionary tale, showing how seemingly neutral algorithms can amplify existing biases. Similar issues emerged with facial recognition software struggling with darker skin tones and translation systems perpetuating gender stereotypes. These "computer program errors" are actually "culture errors" stemming from homogeneous development teams.
Forward-thinking leaders now recognize this challenge as both a moral imperative and business opportunity. Companies like Google, Microsoft, and Salesforce are investing in "product inclusion" initiatives, creating dedicated teams to ensure products work for all users. Promising approaches include shifting from "culture fit" to "culture add" in hiring, implementing transparent pay scales to address gender gaps, and rethinking tech education. Harvey Mudd College's achievement of gender parity in computer science through curriculum redesign and mentorship programs demonstrates how structural changes can create lasting impact.
In the computational era, we've become overly reliant on quantitative data from thousands of users, often neglecting deeper qualitative insights. While A/B tests and usage metrics provide valuable information, they can miss crucial context and human elements. Numerical data appears more scientific and objective, while qualitative insights from individual users are often dismissed as subjective anecdotes from customers who don't understand the product vision.
Neither approach alone reveals absolute truth since both deal with unpredictable human behavior. The most effective strategy combines quantitative "big data" with qualitative "thick data." Thick data requires significant time investment-conducting in-depth interviews, observing users in their natural environments, and understanding the broader context of their needs and challenges.
When gathering thick data, researchers must focus beyond surface-level interface problems to understand users' fundamental goals and motivations. This means not just fixing immediate issues but understanding the broader journey and desired outcomes. Modern AI systems, while powerful, operate as "black boxes" learning from historical data, which means they can perpetuate and amplify existing societal biases. Their inability to predict novel situations or understand nuanced human contexts makes human insight and diverse perspectives more crucial than ever.
The challenge ahead lies in building technology that serves all of humanity, not just those who create it. This requires deliberate effort to diversify tech teams, combine multiple data approaches, and maintain awareness of how automated systems can inadvertently amplify existing inequalities.
Chapitre 8
Minding the Humans: Balancing Technology With Humanity
Open source represents the opposite of exclusion-making code accessible to everyone. While closed systems provide valuable control (as Apple demonstrated with Mac computers and iPhones), open approaches like Android now power more devices globally. By 2019, Apple's closed approach began weakening.
"Open source" refers to code that anyone can modify, contrasting with "closed source" that governs most apps we use daily. The term was coined by Christine Peterson in 1998 to better reflect community values than "free software." WordPress exemplifies this community spirit-"People Helping People"-welcoming anyone to learn computation without cost.
The difference resembles cooperation versus collaboration: cooperation keeps parties at arm's length while collaboration embraces mutual benefits through compromise. Open source provides transparency that could eliminate the need for government regulation of tech companies by making code inspectable.
With AI systems becoming opaque "black boxes" of numbers rather than readable code, new efforts aim to create "gray boxes" with more transparency or teach ethics to AIs. Open technologies allow us to share, collaborate, and reduce fear through shared values and community responsibility.
After a pre-dawn jogging accident in Palo Alto where I fell and seriously injured myself, I experienced a profound realization about technology and humanity. Alone, bleeding, with a broken arm and no phone, I imagined myself as a Mars rover with redundant systems, methodically making my way back to safety in small increments.
At the hospital, medical professionals helped me gain perspective. A doctor's comment that I was "lucky" to move my neck filled me with gratitude. A nurse scolding me about jogging in dark clothing made me realize how easily I could have been hit by a car.
As anesthesia took hold before surgery, I had an epiphany: the computational era needed to address the imbalance between technology and humans. During my ten-month recovery, I observed not just the technology repairing me, but the compassionate humans working alongside machines-doctors, nurses, technicians, hosts who cared for me, and countless unseen people who created the tools for my recovery.
This experience deepened my commitment to inclusion and made me recognize my privilege. As computational thinkers, we must "mind the humans" who brought the computational era into existence. We need to work inclusively to address imbalances that will otherwise be automated, moving beyond mere cooperation to true collaboration. Cooperation means working together independently, while collaboration means working together dependently. For too long, everyday humans have been merely cooperating with machines, while computational thinkers have been collaborating with them. Now that you've read this far, you too can speak machine-if just a "bit."
Chapitre 9
The Future Speaks Both Languages: Finding Balance in a Computational World
The speed of AI development follows the principle of compound interest-small gains that multiply exponentially over time. While a penny at 1% interest becomes just 2 cents after fifty years, at Moore's Law's rate of 66.66%, that penny would grow to over a billion dollars.
This exponential growth led computer scientist Vernor Vinge to predict "the Singularity"-the imminent creation of entities with greater than human intelligence. Ray Kurzweil further predicted that by 2015 computing would surpass a mouse's brainpower (which happened), by 2023 it would surpass a human's, and by 2045 would exceed all human minds combined.
We've already made a quantum leap from obvious computation to AI that bears no computer scent. Millions of invisible computational loops running in the cloud are compounding in strength, drawing upon artists' understanding of humans to create computational surrogates that blink, smile, express uncertainty, and even flirt with us.
To avoid being replaced, we must become moving targets by continually outgrowing our capabilities. Be audacious like the younger generation, unafraid to leap into the unknown. As my late mentor William J. Mitchell would say: "Blast away at it. Get it done!" A warrior can't be a worrier-run toward challenges instead of away from them.
The most successful approach to our computational future combines technical mastery with human values. Software developers create massive invisible machines without physical evidence of their labor, quietly manipulating millions of numbers to build systems that transform information at extraordinary scales. But the shift to cloud-based subscription models has transformed business relationships from one-time purchases to ongoing relationships where pleasing customers becomes critical.
While engineers naturally focus on functionality, today's diverse user base expects more than just technical reliability. The Minimum Viable Product (MVP) approach has become dominant, but I prefer "MVLP" where "L" stands for "lovable," incorporating the Japanese concept of aichaku ("love-fit")-that special connection to something that fits your life perfectly. Creating lovable experiences alongside robust computational machinery is now a "need-to-have," requiring bridges between technical and design perspectives.
We're at a turning point that will irreversibly impact humankind's future. At our current rate of progress, with a minority of computing "haves" imposing their vision on the "have-nots," we risk permanently encoding the biases of a narrow band of creators into the cloud. The Singularity hasn't happened yet-this may be our last chance to ensure diversity of thinking in our computational future.
