English

Based on "Stop trying to turn your suffering into a success story | Kate Bowler" from Big Think Watch the original video

Beyond the "Lesson": Embracing Grief When There's No Silver Lining

In a culture increasingly obsessed with self-improvement and turning every setback into a stepping stone, a powerful counter-narrative is emerging. Theologian and author Kate Bowler challenges one of our most deeply ingrained beliefs: that all pain must serve a purpose, that every suffering must yield a lesson. This relentless pursuit of meaning, she argues, can be more damaging than helpful, especially when we are at our most vulnerable.

American society, in particular, has developed an almost pathological need to rationalize suffering. From personal tragedies to global crises, we are conditioned to seek out the "why"—not just for understanding, but for validation. We want to believe that our pain, or the pain of others, isn't arbitrary. It must be a crucible, a divine test, a precursor to an inevitable triumph. This cultural mania, Bowler contends, has led to the creation of what she vividly calls "purpose monsters."

The Rise of the "Purpose Monster"

"Purpose monsters are everywhere," Bowler explains, describing the internal and external pressures that hound us when faced with adversity. We find ourselves asking, "Is this gonna work out? Is any of this a divine conspiracy to make me good?" This isn't just a casual query; it's a deep-seated anxiety. We become "itchy," as Bowler puts it, when confronted with an unanswered question about suffering. This discomfort, she suggests, "goes right to our material conditions, right to our fear, right to our ontological insecurity."

Ontological insecurity refers to our fundamental unease about the nature of existence itself. We crave order, meaning, and predictability. When bad things happen, especially to good people, it shatters our sense of a just world. We desperately need an explanation for evil, a narrative that restores balance. The idea that pain must teach us something serves as a spiritual balm, a way to impose order on chaos. It allows us to believe that if we know why someone is suffering, we can better cope with the fact of it.

The Harm in Prescriptive Positivity

While the impulse to find meaning is understandable, Bowler warns against its darker side. When we insist that someone's pain must be a lesson, we often do more harm than good. Imagine someone experiencing a profound loss—the death of a loved one, a devastating illness, a catastrophic failure. In their rawest moments of grief, well-meaning individuals might offer platitudes like, "Everything happens for a reason," or "You'll be stronger for this."

"When someone's telling you there's a lesson," Bowler observes, "it's as if they're saying, 'I swear you didn't lose anything. Look around. It's all there.'" But the grieving person knows, deep in their heart, they are being lied to. A loss is a loss. A wound is a wound. To deny the reality of that absence, to immediately pivot to a narrative of growth or purpose, is to invalidate their experience. It strips away the "preciousness of the dignity of grief."

Grief, in its purest form, is a necessary process. It requires space, acknowledgement, and permission to simply be. When we rush to find the lesson, we bypass this crucial stage, forcing individuals to perform resilience before they've even had a chance to mourn. It creates a perverse incentive to package their suffering into an inspiring "success story" before they've truly processed the depth of their pain.

Meaning Without Reason

One of Bowler's most profound insights is the distinction between reason and meaning. "Just because there's not a reason," she asserts, "doesn't mean it's not meaningful." This is a crucial pivot point. We may never understand why certain tragedies strike, why some lives are cut short, or why suffering seems so unfairly distributed. There may be no grand divine conspiracy, no cosmic lesson plan meticulously laid out for us. And accepting that lack of a clear "reason" can be incredibly liberating.

It frees us from the exhausting search for justification, from constantly looking backward and "trying to rearrange the furniture of our past," as Bowler describes it. Instead of endlessly replaying events to discern a hidden purpose, we can shift our focus to the present and the future.

Building Anew from the Rubble

The alternative, Bowler suggests, is not to surrender to nihilism, but to embrace a different kind of strength. It's about acknowledging the reality of what has been lost, the "floods" that have come and gone, leaving devastation in their wake.

"What's left here for me to make something beautiful?" This powerful question encapsulates the essence of her message. It's not about denying the floods or pretending they brought a hidden gift. It's about recognizing that the landscape has changed irrevocably. And from that changed landscape, from the debris and the emptiness, we can still choose to build. We can find meaning not in the cause of the suffering, but in our response to it, in the connections we forge, the compassion we extend, and the new life we create, however different it may be.

In a world that constantly demands a tidy narrative for every hardship, Kate Bowler offers a refreshing and deeply human perspective. She invites us to resist the tyranny of purpose, to grant ourselves and others the sacred space for grief, and to understand that sometimes, there is no lesson, no reason—only the dignity of pain and the quiet courage to build something beautiful from what remains.

Based on "Why Every AI Team Needs Pirates and Architects" from Every Watch the original video

The New Frontier of Code: Why Every AI Team Needs Pirates and Architects

It’s 2026, and the dream of "vibe coding" is a reality. With powerful AI agents like Codex at our fingertips, the ability to manifest an idea into a functional application in days, or even hours, feels like magic. But as the CEO of Every, a 25-person tech company, recently discovered, the ease of creation doesn't always translate to the ease of maintenance. Building a groundbreaking app with AI is one thing; keeping that "hot piece of flaming garbage" from melting down is quite another.

His journey, from the exhilarating launch of an AI-built app to late-night debugging marathons, reveals a critical shift in the software engineering landscape. The future, he argues, isn't about AI replacing engineers, but about a new, symbiotic team structure: the Pirate and the Architect.

From Vibe Code to "Flaming Garbage": The Birth of Proof

The story begins with Proof, an agent-native document editor conceived by Every's CEO in his spare time. "Think Google Docs, but made for agents to use," he explains. Built entirely in Codex over just ten days, without ever looking at a single line of code, Proof went from a basic concept to a finished MVP. The initial launch was nothing short of spectacular. A viral tweet garnered 1.5 thousand likes and 500,000 views, leading to 4,000 new Proof documents created within the first 48 hours. "When I looked at it in the morning the day after launch and saw the stats, I was like, 'We're going to the moon!'"

The optimism was intoxicating, a testament to the power of AI-driven development. But the moon landing proved elusive. The initial success quickly gave way to a chaotic struggle. The speaker found himself staying up until 4 AM nightly, literally sleeping with his laptop open, checking the app every few hours "like some settler on the prairie tending my fire overnight so it wouldn't go out." The "vibe coded sloppy mess" was constantly on the verge of collapse.

This intense, personal crucible forged a profound realization: while AI makes coding incredibly fast, it doesn't inherently make it robust. Taking a project "from a vibe coded sloppy mess to it still has some messy things but it just actually works and I use it every day and it and everyone on the team uses it and it's starting to grow as a real production app" required a fundamental shift in approach.

The New Structure: Pirates and Architects

The core insight from this experience is a proposed restructuring of software engineering teams for the AI era. In 2026, the speaker suggests, engineering teams should be built around two distinct, yet interdependent, roles: the Pirate and the Architect.

The Pirate's Mission: Discovery and Speed

The Pirate is the visionary, the explorer. Their primary job is to "figure out the product," to "move as fast as possible to explore the territory and make something that people really need." Pirates are the masters of vibe coding, unburdened by architectural concerns or the need for a perfectly "well-oiled machine." Their goal is rapid iteration, to "find something valuable as quickly as they can." They are the ones who "own the vision for the product," charting new courses and discovering uncharted user needs.

The Architect's Mandate: Structure and Stability

Once the Pirate has discovered something valuable, that's where the Architect steps in. The Architect's job is to "keep that process on rails," transforming the valuable but often chaotic discoveries of the Pirate into a "machine that is understandable, extensible, maintainable, that won't just go down randomly for no reason that no one can figure out." Architects are the guardians of quality, scalability, and long-term viability.

The synergy is crucial. "Pirates need architects to keep from making something that just like falls apart," the speaker emphasizes. Conversely, "architects need pirates to give them the raw material to work with, to make a system that's actually worth making."

Advice for the Aspiring Pirate

For those who identify as Pirates, eager to leverage AI's speed, the speaker offers three key lessons:

Embrace Simplicity: The temptation with vibe coding is to continuously add features. However, "the best thing you can make is a simple thing that works really well." Focusing on the core value and resisting feature creep will lead to more impactful products.
Learn to "Cover Your Tracks": Throw It Out and Restart: Once you hit on something truly valuable, be prepared to discard your initial code. Referencing writer Annie Dillard, the speaker advises, "You never... want people to see how you got to the idea that you have. You just want to give them the idea." The same applies to product development. Vibe-coded prototypes are often "a mess of tracks." When a clear, valuable concept emerges, "start it over." Code is cheap to write, and even cheaper to discard. Trying to get an AI agent to refactor a messy codebase is often futile, as "they get really distracted by what's already there." A clear sign it's time to restart: "You have something that's clearly valuable and you have lots of bugs that are piling up that you can't figure out how to fix no matter what you do."
Seize the Agent-Native Opportunity: There's a "big opportunity to remake every productivity app for agents." Just as Proof reimagined Google Docs for AI agents, the next generation of software, from spreadsheets to presentations, will have agents as their primary users. "If you start with an agent as your user, the kind of software you build is going to be totally different and really valuable."

The Architect's Enduring Value

For Architects, who might be wondering if their skills are still relevant in an AI-dominated world, the message is one of profound reassurance. "Is software engineering going away as a profession? Do I have any value anymore?" are common anxieties.

The speaker's experience with Proof definitively answered this. "I actually fixed a lot of these issues with Proof by pulling in an architect to help me rewrite a few sections of the app from the ground up over the course of a week or so. And that's what really fixed the problems."

It became "very clear to me after that experience that an architect using an AI is incredibly powerful and incredibly important and isn't just going to be replaced by a model in the near future." While coding models are powerful, they "still lack some of the conceptual clarity that a really senior engineer can bring to a project." AI tends to make "lots of local changes that all make sense in isolation but if you zoom out... the whole thing doesn't hang together." Real engineers excel at this holistic view, ensuring cohesion and structural integrity. For senior engineers, AI is not a threat, but an amplifier, allowing them to "extend your powers" and develop "new expertise that the models don't have."

Building for the Future, Together

Software engineering is undergoing a dramatic transformation. What can be built, how it's built, and the very structure of teams are evolving rapidly. The essential roles, however, remain. The Pirate, moving at lightning speed to discover what's valuable, and the Architect, meticulously crafting those discoveries into a robust, maintainable system.

As for the CEO of Every, his next vibe-coded side project will definitely involve an Architect. "My entire team will mutiny if I don't," he quips, adding, "and honestly it's better to do things together. You don't have to do everything yourself."

The future of coding is here, powered by AI. But the journey to the moon, or to a truly stable and successful product, still requires human ingenuity, collaboration, and the perfect blend of daring Pirates and grounded Architects.

Based on "Ben Horowitz on AI Anxiety, Big Tech Transitions & The Future of Startups | a16z" from a16z Watch the original video

The AI Earthquake: Ben Horowitz on Shifting Paradigms, Infrastructure Crises, and the Path to a Scarier — or Better — Future

The world, as we know it, is undergoing a profound transformation. At the epicenter of this seismic shift is Artificial Intelligence, an innovation so powerful it's rewriting the fundamental "laws of physics" for businesses, governments, and even the very fabric of human interaction. Ben Horowitz, co-founder of the influential venture capital firm a16z, offers a bracingly candid and ultimately optimistic perspective on this new era, navigating the anxieties, the infrastructure bottlenecks, and the surprising solutions that might emerge from the chaos.

Horowitz, a veteran of tech booms and busts, understands disruption. From the dot-com collapse to the current AI revolution, he's witnessed markets buckle and companies pivot. But AI, he argues, is different. It's not just a technological upgrade; it's a foundational change that demands a complete re-evaluation of strategy, investment, and even our understanding of what constitutes a "job" or "truth."

The New Laws of the AI Universe: Where Money (Finally) Talks

For decades, a cardinal rule in technology was that you couldn't simply "throw money at the problem." If your product was two years behind a competitor, hiring a thousand engineers wouldn't close the gap; it would likely just create more complexity, a concept famously dubbed "The Mythical Man-Month." That axiom, Horowitz declares, is "no longer true."

"If you have enough money and some good data, you can buy enough GPUs and solve basically anything in software," he explains. This shift means that raw capital and computational power, rather than solely human ingenuity in a linear fashion, can now directly accelerate development and overcome competitive lags.

Compounding this, another long-held truth has evaporated: the power of customer lock-in. Historically, if you had the customer, you had a multi-layered advantage – migration pain, data lock-in, user interface familiarity. "Those are pretty much gone," Horowitz asserts. Code is easily replicable, data can be moved with increasing ease, and critically, the primary interface with software is no longer solely human. "It's not even going to be a human talking to your software," he notes, "it's going to be an AI. And AIs are really flexible on how they use user interfaces." This means switching costs plummet, and established market positions become far more precarious.

The implications for existing companies are stark. A product lifecycle that once offered a 5-10 year runway might now be compressed to "five weeks." Legacy companies, those founded "pre-AI," face an existential crisis. They must fundamentally redefine their value proposition beyond features that can be easily replicated by AI, or risk being "slaughtered in the valuation game." Horowitz points to a portfolio company like Nan, a travel firm, as an example of resilience. Despite the "SaaS apocalypse" and the seeming vulnerability of travel tech, Nan thrives because it possesses deeply embedded, complex relationships with airlines, hotels, and budgeting systems, alongside an invaluable channel to the niche "travel manager" customer – a channel no AI giant is rushing to build. These "explicit relationships" and intricate operational layers become the new defensible moats.

The Looming Infrastructure Bottleneck: A Nation on E

Beyond the corporate boardroom, AI's voracious appetite for resources is exposing a critical vulnerability at the national level: infrastructure. Horowitz paints a grim picture of America's readiness for the AI age. "America's got to rebuild its entire infrastructure like right now," he warns. "We don't have enough rare earth minerals. We don't have enough electricity. We don't have enough manufacturing capacity."

The problem isn't just about chips, though Nvidia is making strides. It's a systemic bottleneck across the entire supply chain. "Nvidia will make enough chips, but then we won't have enough memory," he predicts. "Almost everything is the bottleneck." The urgency is palpable: "We're pretty much out of electricity now in the United States. Like not 12 months from now, like right now."

This isn't the dot-com bubble's "dark fiber" problem, where infrastructure was built but underutilized. Today, "all the GPUs are hot, they're all lit right now." The demand is "straight vertical," but the capacity to build new power plants, DRAM factories (which take five years), or even essential components like power transformers (a technology largely unchanged since the invention of electricity, prompting a16z to invest in a transformer company) is simply not keeping pace. The "China graph" of capacity building, Horowitz implies, is ascending steeply, while the "US graph" lags. This macro-level challenge demands massive investment and strategic foresight, a scale of funding that Horowitz suggests influenced a16z's recent multi-billion dollar fundraise.

The Crisis of Trust and Identity: Crypto's Unexpected Role

As AI becomes ubiquitous, a more insidious problem emerges: the erosion of trust and the blurring of reality. Horowitz vividly describes a chilling scenario: "Oh my god, somebody's going to go on a Zoom. They're gonna it's going to be AI me and they're going to tell my finance team to wire like, you know, $500 million to Nigeria and and that's going to be a problem."

The proliferation of AI-generated content – personalized emails, deepfake videos, hyper-realistic voice calls – threatens to render all digital communication "completely unusable." We're entering an era where distinguishing human from bot, truth from fabrication, becomes nearly impossible. The old email filtering tricks, like spotting a misspelled name, are useless when AI can perfectly personalize thousands of messages.

This is where crypto, a technology often seen as separate from AI, becomes indispensable. Horowitz identifies several critical roles for blockchain and cryptographic solutions:

Human Verification: "Are you a human or are you a bot?" This fundamental question will underpin social media, dating apps, and professional interactions. Proving one's humanity and unique identity cryptographically will be paramount.
Content Provenance: To combat deepfakes and manipulated media, content will need "cryptographically strong indication assigned piece of content that says okay yeah I made this or this is like really a video of me Marco Rubio giving a speech. This isn't something that somebody faked."
Source of Truth: In a world saturated with AI-generated information, who do you trust? Google? Meta? The government? Horowitz argues for the "mathematical game theoretic properties of the blockchain" as a more reliable, decentralized arbiter of truth.
Economic Identity: Beyond identity verification, crypto can solve practical problems like fraud prevention in Universal Basic Income (UBI) programs. The government's struggle to distribute stimulus funds, with an estimated "$450 billion got stolen," highlights the need for a secure, universal digital address for money.
AI as Economic Actors: As AIs evolve, they will need to transact, earn money, and function as economic agents. "How do I make money as an AI? How does somebody send me money? Can I be a merchant, a credit card merchant if I'm not a human?" Horowitz asks. A "bare instrument on the internet," or "internet money," will be crucial for AIs to participate in the economy, a role perfectly suited for crypto.

The synergy is clear: AI creates profound problems of trust and identity, and crypto offers foundational solutions.

The Future of Work and Wealth: Scary or Spectacular?

The anxieties surrounding AI often coalesce around the future of work. Will white-collar jobs disappear? Will a few giant companies monopolize intelligence? Horowitz, quoting Yogi Berra, acknowledges the difficulty of predicting the future, but offers two contrasting scenarios for venture capital and, by extension, the broader economy.

One path echoes the Industrial Revolution, where an initial flurry of innovation (like 300 early auto companies) consolidated into a few dominant players (the "Big Three"). In this future, "new companies are just harder," and venture capital might become more akin to traditional banking, funding a small number of colossal entities.

However, Horowitz leans towards a more optimistic, decentralized vision. He draws parallels to developing nations where "everybody's an entrepreneur," buying and selling, constantly creating value. The truly transformative aspect of AI, he believes, is its ability to unlock human potential on an unprecedented scale. "The cool thing is that now 8 billion people that might have an idea in their head can get it out of their head." Whether it's writing music, making a movie, or developing code, the "capital gate" and the "idea gate" are disappearing. This could lead to a venture capital world that is "much bigger and much more exciting because everybody in the world is an entrepreneur."

Historically, technological shifts have always been accompanied by fear. In 1789, 98% of Americans were farmers; today, those jobs are largely gone, replaced by professions that would have seemed "ridiculous" to an 18th-century agrarian. Horowitz refutes the dystopian narrative, including the "old man yells at cloud" image of Bernie Sanders interviewing an AI. He cites John Maynard Keynes's famous miscalculation: Keynes predicted that with abundance, people would work only 15 hours a week. What he didn't foresee, Horowitz explains, was humanity's "unbelievable" capacity to invent new "needs" – not just one car, but a car for every person; not just food, but elaborate tasting menus; not just shelter, but awesome vacations and access to boundless information.

"The history of technology is things have always gotten better," Horowitz concludes. While the transition is undeniably "scary," he believes that in 15 years, "everybody in America and probably around the world is going to live better than... anybody did in 1980." This isn't to dismiss the challenges or the need for careful navigation, but it's a powerful statement of faith in human ingenuity to adapt, create, and ultimately thrive in an AI-powered world, even if the "laws of physics" are being rewritten before our very eyes.

Based on "The Workers Letting A.I. Do Their Jobs" from New York Times Podcasts Watch the original video

From Coders to Conjurers: How AI is Radically Reshaping Software Development

For years, the world has grappled with the looming question: how will artificial intelligence reshape our lives and work? The answers have spanned the spectrum from utopian salvation to apocalyptic doom. Yet, amidst the speculation, a quiet revolution has been unfolding at the very heart of the tech industry, among the software developers who build the digital world around us. These are the people at the vanguard, not just contemplating AI's impact, but actively inviting it into their daily tasks, transforming their jobs in ways both exhilarating and unsettling.

Legendary tech reporter Clive Thompson, a long-time observer of Silicon Valley, recently embarked on an extensive survey of this pivotal shift, interviewing some 75 software developers across the country. His findings, shared in a conversation with Natalie Kitroof for The Daily, reveal a profound and rapid transformation: coders are, surprisingly, coding less – and in some cases, not at all.

The Unthinkable: Coders Not Coding

Thompson's reporting unearthed a stark reality: a significant majority of the developers he spoke with are now outsourcing much of their day-to-day programming to AI. This isn't a gradual shift; it's a "sea change" that has accelerated dramatically in the last six months, as AI coding tools have become more sophisticated and gained the trust of even skeptical programmers. "Some of them are writing no code at all," Thompson reveals, describing a landscape vastly different from just a year or two ago.

Initially, Thompson wondered if this outsourcing of a core creative task would be "deflatting or demoralizing." For decades, he knew, developers derived immense pleasure from solving the intricate puzzles of code. Yet, the reality was overwhelmingly positive. The great majority were "jazzed and excited" about the new powers AI bestowed upon them. They could now articulate their desired outcome in plain language and, within minutes, receive working code.

"They've always loved building things," Thompson explains. "That's the fun of being a developer is you take an idea you have and through sweat and work you turn these magic words into a machine that does things for you." Even without writing the code themselves, they still feel like "sorcerers" or "conjurers," bringing ideas into being with unprecedented speed. This newfound "loop of success" is, for many, even more satisfying because the AI operates faster than they ever could.

A Leap in Abstraction: From Rewiring to AI Swarms

To grasp the magnitude of this change, one must understand the history of software development itself. For 50 to 60 years, the field has continuously sought easier ways to communicate with computers, moving ever closer to human language.

In the 1940s, programming the first computers like ENIAC involved physically rewiring the machine – a highly "labor-intensive" process where women literally crawled inside to create new logical systems. As computers became industrialized, this proved impractical. Early programming languages emerged, translating typed commands into digital instructions. These were still incredibly arduous, requiring developers to micro-manage every detail, like "juggling 900 balls just to get it do the most basic piece of math."

Over the decades, coders consistently sought to "automate some of that labor," a process they humorously call "adding a layer of abstraction." Each new layer made coding easier, less "finicky," and more akin to human language. What's happening now with AI, Thompson asserts, is "probably the biggest change it's undergone yet."

The modern AI coding paradigm involves "teams of agents." A human developer might ask a main AI agent to "write this feature for me." The AI then devises a plan and "spawns other sub agents to do different parts of the task." One agent writes the code, another tests it, and if errors arise (which they almost always do initially), yet another agent analyzes the error messages, refines the code, and re-tests in a continuous loop. Only when the code passes all tests is it presented back to the human. This "little team of agents all working in a swarm" signifies an enormous leap in automation and efficiency.

Speed, Scale, and the "Steve Jobs" Effect

Practically, this translates into dramatic accelerations. Small startups, often two-person operations, report moving "up to 20 times faster" than they would have just two years ago. A customer request for a new feature that once took a full day can now be completed in "maybe half an hour."

However, this speed varies with scale. While a startup building entirely new code can leverage AI fully, larger, more mature companies like Google operate with more caution. At Google, AI might write "40 or 50%" of the code, speeding up their overall "metabolism" by about 10%. Yet, as Google developers noted, "10% for a company our size, that's a huge win."

So, if AI is doing the coding, what do developers actually do? Their job, in essence, becomes that of an architect rather than a construction worker. They focus on "what the software ought to be doing," spending more time on experimental iteration. Many developers told Thompson that with AI, they can "run through like 10 different possibilities and I'll pick the absolute best one." Several even likened the experience to "being Steve Jobs" – delegating the creation of multiple designs and then choosing the optimal one.

On a deeper level, their primary activity is "just talking." They engage in extensive conversations with AI, a process that demands extreme clarity. Thompson found that this necessity has, surprisingly, made many developers better communicators, not just with AI, but "to the world in general." As one developer, Manu Eert, jokingly but insightfully put it, "I wonder if we're finally teaching all the nerds empathy because they're having to do that."

The Art of "Punishing" AI

Manu Eert's experience with AI offers a fascinating glimpse into this new human-AI dynamic. Initially skeptical about AI's reliability, he gained confidence as it proved its capabilities. Eert and others have settled on a "Socratic dialogue" technique: they instruct the AI to "ask me questions about how this software feature should work." This interview process helps the human coder clarify their own vision before the AI takes over.

But AI, despite its prowess, can "misbehave." Eert recounted instances where the AI would skip crucial tests, declaring them unimportant. His solution? "Punishing" the AI. This involves writing "very stern list of instructions like a a ten commandments" in all caps, which the AI must consult before every action. These commands include emotionally charged language like, "if you don't do these tests I will be fired," and declaring failure "unacceptable and embarrassing."

Thompson explains the logic: large language models understand meaning based on context. Words like "embarrassing" signal a "bad neighborhood" in the semantic landscape, raising the stakes for the AI. So, yes, emotional and even harsh language appears to have an effect.

The Shadow Side: Deskilling and Job Loss

Despite the excitement, developers harbor significant concerns. A primary fear is "deskilling" – losing their deep code sense by relying too heavily on AI. More senior developers, who learned to code manually, recognize when AI produces "flabby" or incorrect code. But they worry about "the next generation" lacking this fundamental understanding. Piaan, a newer developer whose employers mandated AI tool use, explicitly told Thompson she felt her own coding knowledge "degrading."

This raises a fundamental debate: is losing coding skills a problem if AI can do it better? One camp argues that AI will be more reliable, avoiding "stupid human mistakes" in what is often "rote and tedious" work. The other, smaller but vocal, cohort warns that while AI-generated code might look good now, it could create "subtle bugs" and "nasty interactions" down the line, leading to a "huge mess" in a few years.

The specter of job loss is equally potent. Thompson points to research by Eric Benjolson at Stanford, showing a 16% drop in software developer job postings and hirings in the last year alone. This is happening when AI tools are just "going from a crawl to a walk to a run." The capitalist drive for efficiency means companies will inevitably seek to replace expensive human developers with AI, leading to "softening" demand for junior hires and the potential disappearance of entire job categories, much like the type setter.

Implications for the "Rest of Us": The Paradox of Automation

For those outside of coding, AI's impact might seem more distant, but developers are experiencing a paradox that could resonate across other white-collar fields: the "hard" technical skills they spent years acquiring are often the "easiest things to automate." The truly "human skills" – talking to colleagues and customers, setting priorities, devising strategy, understanding what should be built – remain beyond AI's grasp.

Thompson draws a historical parallel: in the 1980s, chess seemed incredibly difficult for computers, while speaking seemed easy. Yet, computers conquered chess in the '90s, taking two more decades to master human-like speech. This suggests that what we perceive as our most valuable, complex skills might not be what AI automates first.

The pace of this transformation for the broader economy, however, might be slower than the "super speed" cultural acceleration we perceive. Thompson reminds us of the advent of personal computers in the 80s and 90s. Initially, they didn't dramatically increase corporate productivity. It took companies years to "reorganize the way it did business around the computers," fundamentally changing workflows and information flow, before efficiency gains were seen. He suspects AI will follow a similar, longer timeline for widespread industrial impact.

The Upside: Ubiquitous Software and Unforeseen Wonders

Despite the fears, Thompson envisions significant upsides for society. The world, he argues, is "horribly underserved by technology." He cites the example of a "$50 million concrete mixing firm" that, despite its size, runs on "three Excel spreadsheets on a Windows XP computer" because it can't afford a team of custom software developers. If AI makes software creation cheaper and faster, a single developer could build and maintain custom solutions for such businesses at a fraction of the cost, leading to "actually good ways in everyday life for a lot of people at work."

Ultimately, software will stop being "precious and rare" and become "ubiquitous," much like paper or word processing. Paper, once rare, became cheap and led to unexpected innovations like Post-it notes. Similarly, the Macintosh made word processing accessible, leading to an explosion of creative, if sometimes "ugly," documents like riot-girl zines – an outcome no one in 1983 could have predicted.

"More is not just more. More is different," Thompson asserts. As software becomes "trivially easy to summon into being," new behaviors, both "malign" and "delicious," will emerge. It will "catalyze all of the human desires" – from Shakespearean sonnets to disinformation, from medical record analysis to wholesale cheating.

The future, Thompson concludes, will be "incredibly weird." This transformation, like those before it, will reflect us – our desires, our creativity, our flaws. It will be both awesome and potentially bad, but undeniably, a powerful mirror held up to humanity.