Tag: machine learning

Categories
AI Bicycles History

The Bicycle Shop

Part 2 of 3…

It is eleven-thirty on a Tuesday night and she is arguing with a language model about a spreadsheet.

Not arguing, exactly. That’s not the right word. She is coaxing. She is debugging. She is reading error messages that tell her almost nothing and rewriting prompts that almost work, and she has been doing this for two hours, and the spreadsheet still isn’t right, and she is going to try one more thing before she gives up and does it by hand. She is a data analyst at a mid-sized logistics company in Columbus, Ohio. She is not a researcher. She is not a founder. Nobody is writing about her. She is just a person trying to get a machine to do something useful, and the machine keeps almost doing it, and she keeps learning, in the gap between almost and done, something she couldn’t have learned any other way.

She doesn’t know what she’s learning. That’s the important part.

In 1892, two brothers opened a bicycle repair shop on West Third Street in Dayton, Ohio. The bicycle craze was at its peak — the safety bicycle, with its two equal wheels and chain drive, had just replaced the penny-farthing, that absurd high-wheeler everybody called loose change and the riders, with complete seriousness, called the ordinary. The brothers fixed flats and adjusted brakes and built custom frames and ordered parts from Coventry and kept the books and swept the floor. It was ordinary work. Nobody was writing about them either. What they were doing was accumulating, without knowing they were accumulating, a physical understanding of how machines move through space — the gyroscopic principles, the weight distribution, the thousand small calibrations that kept a rider from falling. They were learning in their hands what no university taught and no book fully contained.

Eleven years later they flew.

We tell the Wright Brothers story as a story about flight. It makes sense — flight is the thing, the miracle, the moment the world changed. But the actual story, the one that explains how Kitty Hawk was possible, is a story about a bicycle shop. It is a story about unglamorous preparatory work, about the education that hides inside the constraint, about what you learn in the gap between the machine that exists and the machine that should exist. Orville and Wilbur didn’t go to Kitty Hawk despite the bicycle shop. They went because of it. The shop was the point. They just didn’t know it yet.

We are in the bicycle shop right now.

The people building with AI today — the prompt engineers, the fine-tuners, the agent builders, the data analysts in Columbus arguing with spreadsheets at midnight — are doing work that looks, from the outside, like mere tinkering. Unglamorous. Iterative. Full of failure. The tools are awkward. The models hallucinate. The context windows run out at the wrong moment. Every solution opens three new problems. It feels like the penny-farthing: powerful enough to be useful, constrained enough to be maddening, requiring a kind of practiced vault just to get started.

But that awkwardness is the education.

Every time a prompt fails, the person writing it learns something about how the model thinks — about what it responds to, what it resists, where it gets confused, where it surprises you. Every agent that breaks in production teaches its builder something about the gap between what a model can do in a demo and what it can do under load, with real data, with users who don’t behave the way you expected. Every context window that runs out forces a decision about what actually matters, what is essential, what can be cut. These are not just technical lessons. They are epistemic ones. They are lessons about the nature of intelligence, about how meaning gets encoded and retrieved, about what it means for a machine to understand something versus to pattern-match on the surface of understanding.

The people learning these lessons right now don’t have a name for what they know. They just know it in their hands.

This is how it always works. James Starley’s craftsmen in Coventry bent and brazed bicycle frames by feel and experience, knowing things in their hands they couldn’t fully explain on paper. That embodied knowledge — the tight tolerances, the interchangeable parts, the discipline of making things that had to work — migrated into every bicycle shop that followed, crossed the Atlantic, and ended up in a shed in Ohio. The Wright Brothers didn’t invent precision manufacturing. They inherited it, absorbed it, and applied it to a problem nobody else had solved because nobody else had brought those particular hands to that particular problem.

The chain drive was the hinge. Before it, the bicycle’s design was locked — bigger wheel for more speed, higher and higher off the ground, until the machine teetered at the edge of what a human could survive. The chain drive broke the constraint. It decoupled the pedals from the wheel, let the gearing do what only size had done before, brought the rider back to earth. What had been a machine for athletes became a machine for everyone. What had been the ordinary became, almost overnight, something new.

We are waiting for the chain drive.

Not waiting passively — it is being built right now, in a hundred places at once, by people who mostly don’t know they’re building it. It might be the interface that finally makes AI genuinely accessible to people who can’t do the running vault. It might be the memory architecture that lets a model carry context the way a human carries context, not in a window but in something more like experience. It might be something nobody has named yet, something that will seem obvious afterward, the way all elegant solutions seem obvious after the fact.

What it will not be is the product of people who stayed away from the bicycle shop.

The analyst in Columbus closes her laptop at midnight. The spreadsheet is still not right. She has learned three things about how the model handles date formatting, two things about how it interprets ambiguous column headers, and one thing about her own assumptions that she didn’t know she was making. Tomorrow she will try again. She will get closer. At some point — not tomorrow, maybe not this year — she will get it right, and the thing she learned in the gap will be available to her for the next problem, and the one after that, and she will carry it forward without knowing she’s carrying it, the way craft always travels, in hands that have done the work.

She doesn’t know what she’s riding toward.

That’s the ordinary part. That’s always been the ordinary part.

Categories
AI Startups

A New Reason to Launch

“Before you launch, the speed you can build is now mainly limited by your imagination in what you tell AI. After you launch, the AI can watch your users and make improvements on its own.”
— Jared Friedman, Y Combinator

Jared Friedman watches hundreds of founders a year navigate the gap between idea and launched product. He notices patterns the rest of us miss. And what he’s describing above is not an incremental improvement in how software gets built. It is a change in the nature of the advantage.

This is a different kind of liberation than founders have known before.

The old liberation was launch early and the market corrects your wrong assumptions. Humbling, but useful. You were still the one doing the correcting, late at night, rewriting the onboarding flow based on what the data told you.

The new liberation he’s describing is something closer to multiplication. You launch, and now there are effectively more of you. The AI is watching session replays you’ll never have time to watch. It’s noticing the drop-off after step three that you’d have caught in month four. It’s holding the pattern of a thousand user paths simultaneously and asking what they mean. Your imagination seeded the thing. Reality is now feeding it.

That observation redraws the map cleanly. Pre-launch and post-launch used to differ in degree — you knew more after than before. Now they differ in kind. Pre-launch you are the sensing organ. Post-launch you’ve grown new ones.

The founders who feel this most viscerally, I suspect, are the ones building alone or in pairs — the people for whom every previous era of building had a hard ceiling imposed by human hours. They could only read so many support tickets. They could only run so many experiments. The ceiling is lifting and the feeling is of a room getting larger.

The core advice hasn’t changed. Paul Graham was saying “launch early” twenty years ago and it was true then. What’s changed is the reason underneath it — the mechanism that makes it true now is nothing like the one he had in mind.

The advice is twenty years old. There is a new reason and it is brand new. Most people haven’t noticed the swap yet. But they will.

That window does not stay open long.

Categories
AI AI: Transformers

The State You Never See

The transaction arrives in milliseconds. A purchase attempt — a gas station in Phoenix, a grocery store in suburban Atlanta, a wire transfer at 2 a.m. — and somewhere in the authorization chain, a system has to decide. Not later. Now. The clock is already running.

When I led the fraud detection team at Visa, this was the problem that lived in your chest. You couldn’t see what you needed to see. You couldn’t know whether the person presenting that card was the person who owned it, whether the account had been compromised six hours ago in a breach you hadn’t yet detected, whether the behavioral signature of these transactions was the legitimate cardholder running errands or a fraudster working methodically through a stolen number before the window closed. You could only see what the transactions said. You could never see the state underneath.

That distinction — between what you can observe and what is actually true — turns out to be one of the organizing problems of our time. It has a name, a formal structure, and a history that runs from mid-century mathematics through the trading floors of quantitative hedge funds to the frontier of artificial intelligence. The name is the hidden Markov model. But the problem it addresses is older than the math, and more human than the jargon suggests.

Continue reading “The State You Never See”
Categories
AI Business IBM Management

Making It Up As We Went Along

There was a building along Route 270 in Gaithersburg, Maryland where people kept secrets for a living. Not the cloak and dagger kind. The corporate kind, which in its own way requires just as much discipline. The IBM Washington Systems Center occupied a two-story modern building that looked, from the outside, like any other outpost of late twentieth century American business. Inside it was something else. It was where IBM sent its hardest problems, and where the largest IBM customers in the world — the ones whose names you would recognize immediately — sent their most urgent ones back.

I worked there as a manager. But before I was a manager there, I was a hire. And before I was a hire, I was like every other IBM professional on the outside of a particular line — a line I didn’t fully understand until I crossed it.

At IBM there was a protocol so embedded in the culture it had almost ceased to be a rule and become something closer to a religious observance. New products were not discussed until they were announced. Not hinted at. Not alluded to. Not whispered about with a favored customer over lunch. The announcement came in the form of something called a Blue Letter — a formal communication from senior leadership that functioned as the official moment a product entered the world. Before the Blue Letter, the product did not exist in any conversation you were permitted to have. After it, you could talk about nothing else.

Violation was not a career setback. It was a firing offense. Full stop.

That clarity had a kind of elegance to it. You didn’t have to calibrate how much you could say or navigate gray areas. The line was absolute. And because it was absolute, and because everyone knew the consequence of crossing it, the culture enforced itself. You didn’t need surveillance. You needed people to understand the stakes, and they did.

What I didn’t understand, from the outside, was what that line was doing to my imagination.

When you can’t see the roadmap — when the strategy and the unannounced products and the long arc of where the company is going are all behind a wall you have no access to — you don’t experience that as absence. You experience it as depth. The things you don’t know feel like they must be there for a reason. The gaps in the announced picture feel like the gaps in a great iceberg — what’s visible is impressive, but what’s below the surface must be more impressive still.

I had faith in IBM’s strategic intelligence the way you have faith in things you can’t fully see. And faith, uncontradicted by evidence, tends toward beauty. The hidden roadmap wasn’t just unknown — it was, in my imagination, a thing of coherence and intention and vision. It had to be. The alternative was too unsettling to consider.

Then I got hired into the Washington Systems Center and crossed the line.

There was no single moment of disillusionment. No specific product that shattered the dream, no strategy document that read like a disappointment. It was more like a gradual adjustment of the eyes — the way they adapt when you move from bright sunlight into a room lit quite differently than you expected. The room isn’t dark. It’s just not what you anticipated. And once your eyes adjust you can see perfectly well, but you can never quite recover the image you had of the room before you entered it.

The reality on the inside was messier than the dream on the outside. More improvised. More human. We were, in ways I hadn’t anticipated, almost making it up as we went along. Not carelessly — the people at WSC were extraordinary, the work was serious, the commitment was real. But the beautiful coherent roadmap I had constructed in my imagination from the outside bore only a partial resemblance to the actual thing. Strategy, it turned out, looked different up close. Less like architecture. More like weather.

I absorbed this alone. Nobody sat me down and named what I was experiencing. Nobody had the conversation with me that I would later learn to have with others. I found my way through it by degrees, the way you find your way through most things that don’t come with instructions.

What came out the other side wasn’t cynicism. It was something more useful — a clearer eye, a more grounded relationship to the institution I was part of. The faith hadn’t been wrong exactly. It had just been innocent. And innocence, once lost, can’t be recovered. But what replaces it, if you’re lucky, is something steadier.

Years later I was the manager. And I was hiring IBMers — good ones, experienced ones, people who had spent serious careers on the other side of the blue line. They knew the products cold. They knew the customers. They knew how to work. What they didn’t know, couldn’t know, was what waited for them on the inside of the wall they were about to cross.

I knew it. Because I had been them.

There is a particular expression that crosses a person’s face when the actual roadmap becomes visible for the first time. It isn’t dramatic. It doesn’t announce itself. It’s more like a subtle recalibration — a slight stillness, a momentary adjustment behind the eyes. The person in front of you is doing quiet interior work, reconciling what they imagined with what they’re now seeing. The gap between those two things is doing something to them, and they’re not sure yet what to do with it.

I learned to watch for that expression. And when I saw it I knew what was coming if I didn’t get ahead of it.

The danger wasn’t disappointment. Disappointment is temporary, and smart people move through it. The danger was what disappointment hardens into when it isn’t named and worked through — a corrosive cynicism that poisons not just the person carrying it but everyone around them. A talented IBMer who had invested a career in faith, discovered the faith was misplaced, and decided the whole enterprise was therefore hollow — that person could do real damage to a team. I had seen it happen, or the early stages of it, which was enough.

So I developed what I came to think of as the god is dead conversation.

The name came from Nietzsche, though the application was strictly practical. What Nietzsche meant — or one of the things he meant — was that when the organizing faith of a civilization collapses, the collapse doesn’t leave nothing. It leaves a vacancy that has to be filled with something else, something built rather than inherited. The god is dead conversation was about helping someone through that vacancy quickly, before they filled it with the wrong thing.

It wasn’t a long conversation. It didn’t need to be. What it needed to be was honest, and direct, and delivered before the cynicism had time to set.

I would tell them what I saw happening. I would tell them it was normal, expected, that everyone who crossed this particular line felt some version of it. I would tell them the dream they’d carried on the outside wasn’t foolish — it was a reasonable response to incomplete information, and the information had been incomplete by design, and the design had served real purposes. None of that made them naive. It made them human.

And then I would tell them what I’d learned on my own, without anyone to guide me through it. That the messiness on the inside wasn’t a failure of IBM’s intelligence or intention. It was just what strategy actually looks like when you’re close enough to see the seams. Every institution looks more coherent from the outside than it does from the inside. That’s not a scandal. That’s organizational life.

The conversations were tricky. There was real care required. You were asking someone to grieve something — the beautiful imagined roadmap, the faith in a hidden coherence — without tipping them into bitterness about what replaced it. You were trying to accelerate a process that, left alone, might drag on for months and quietly corrode their effectiveness. And you were doing it while also being their manager, which meant you needed them functional and engaged on the other side of the conversation, not just unburdened.

What I had going for me was credibility. I wasn’t delivering a message from outside the experience. I had made the same crossing. I knew the specific texture of what they were feeling because I had felt it myself — the diffuse quality of it, the absence of a single dramatic moment, the gradual adjustment of the eyes. When I told them I understood what was happening to them, I actually did. I think they could tell.

Trial and error had taught me the shape of it. What didn’t work I had found out the hard way, at some cost, early on. What I arrived at had been load tested by real people in real situations. It wasn’t a framework from a leadership seminar. It was something I owned completely, which meant I could adapt it in the moment rather than execute a script.

Most of them came through it well. Better than well, actually.

What I hadn’t fully anticipated — though in retrospect it makes complete sense — was what replaced the faith once it was gone. It wasn’t the steadier, clearer-eyed pragmatism I had found my way to alone. It was something more potent than that. Something that surprised me the first time I saw it and then became one of the things I quietly counted on.

They came out the other side feeling superior.

Not arrogant. Not dismissive of colleagues still on the outside. But quietly, privately elevated — because they were now keepers of the secrets they had once only believed in. The blue line that had shaped their entire professional identity, that had defined the boundary of what they could know and say and imagine, was now behind them. They were on the inside. They had access. They had been trusted with the actual roadmap, the real strategy, the unannounced products that the rest of the world was still constructing faith-based pictures of.

The believer had become the keeper. And keeping, it turned out, was a more powerful identity than believing. The believer is passive — sustained by what they imagine. The keeper is active, responsible, trusted. They carry something real rather than something projected.

It solved my practical problem neatly, though that wasn’t why it moved me. What moved me was watching people find their footing on the other side of a genuine loss and discover that the ground there was solid — different from what they’d imagined, but solid. They hadn’t just survived the crossing. They’d been changed by it in a way that made them more valuable, more grounded, more fully present to the actual work.

Which was, I suppose, what the god is dead conversation had been for all along.

I think about that blue line often these days.

We are living through a moment when artificial intelligence is advancing faster than most people can track, and the organizations building it — the labs, the research teams, the companies placing enormous bets on where this technology is going — have their own version of the wall. Not identical to IBM’s. The competitive and legal architecture is different. The culture is different. But the basic structure is the same: there is what has been announced, and there is everything else, and most people are working entirely from the announced side.

Which means most people are doing what I did before I crossed the line at WSC. They are filling the gaps with faith. And faith, uncontradicted by evidence, tends toward beauty.

The unrevealed AI roadmap looks, from the outside, like a thing of coherence and intention. The capabilities that haven’t been announced yet must be more impressive than the ones that have. The strategy must be more considered than what’s visible. The gaps in the public picture feel like depth rather than uncertainty — like the part of the iceberg below the surface, which must be vast because the part above is already remarkable.

I am not saying this faith is wrong. I held the same faith about IBM and it wasn’t wrong exactly — it was innocent. The people constructing faith-based pictures of where AI is going are doing a reasonable thing with incomplete information. The information is incomplete partly by design, for reasons that make competitive and strategic sense, just as IBM’s secrecy made sense. None of that makes the faith naive.

But I’ve been inside enough walls to know what the inside tends to look like. And I think it’s worth saying, clearly and without cynicism, that the reality is probably messier than the dream. More improvised. More uncertain. More human. The people building these systems are extraordinary — the work is serious, the commitment is real — but they are also, in ways that might surprise you, almost making it up as they go along. Not carelessly. But without the complete map that the outside imagines must exist somewhere, fully drawn, waiting to be revealed.

Strategy, up close, looks less like architecture and more like weather.

This isn’t a counsel of despair. It’s almost the opposite.

The IBMers who crossed the line and survived the god is dead conversation didn’t end up with less than they started with. They ended up with more — a clearer eye, a more grounded relationship to the institution, a more useful kind of engagement with the actual work. The faith they lost was the innocent kind. What replaced it was steadier and more durable.

I suspect something similar is available to anyone willing to look at the AI moment with clear eyes. Not the disappointed cynicism of someone who expected a beautiful coherent roadmap and found a human institution instead. Not the breathless faith of someone still on the outside of the wall, filling gaps with generous assumptions. Something in between — harder to sustain, more honest, ultimately more useful.

The technology is real. The progress is real. The stakes are real. None of that requires the roadmap to be a thing of beauty. It just requires it to be worked on seriously by people who understand what they don’t yet know — which, from everything I can observe, it is.

What I couldn’t give those IBMers, and what nobody can give you, is the experience of crossing the line yourself. The god is dead conversation only works because the crossing has already happened — because the person sitting across from you has already seen the actual roadmap and is already processing the gap between what they imagined and what they found. You can’t have the conversation in advance. The disillusionment has to be real before it can be worked through.

Most of us will never cross the line into the AI labs. We’ll stay on the outside of the wall, working from the announced picture, filling the gaps as best we can. That’s not a failure — it’s just the condition most of us are in, the same condition those IBMers were in for their entire careers before I hired them.

But knowing the wall exists, and knowing what walls do to imagination, seems like it ought to change something about how we hold our faith. Not abandon it. Just hold it a little more lightly. Stay curious about the seams. Remain open to the possibility that the most important thing about the unrevealed roadmap isn’t what’s in it — but what we’ve projected onto it.

The blue line is still there. Most of us are still on the outside of it.

And the hidden roadmap still looks, from here, like a thing of beauty.

Categories
AI AI: Transformers Books

The Updating Machine

Tom Chivers puts Bayes’ theorem in plain English and it sounds almost obvious: “the probability of event A, given event B, equals the probability of B given A, times the probability of A on its own, divided by the probability of B on its own.” A formula for revising what you believe when new evidence arrives. You started somewhere. Something changed. Now you believe something slightly different. Repeat.

The obvious part is the mechanics. The hard part is the loop.

Most reasoning errors I catch in myself aren’t failures of logic — they’re failures to update. I hold a view, evidence accumulates against it, and I find reasons the evidence is flawed rather than reasons the view might be.

Psychologists have a name for this: confirmation bias. But I’ve always found that label a bit too clean, like it describes a bug rather than a feature.

The prior isn’t wrong to be sticky. It represents everything you’ve learned up to this point. The problem is when it becomes load-bearing — when the prior stops being a starting position and starts being a conclusion.

“Strong opinions, loosely held” is supposed to solve this. It’s a useful phrase — it captures something true about the right posture toward your own beliefs. But in practice the second half is harder to honor than it sounds. The strong opinion gets stated, new evidence arrives, and changing your mind in public feels like losing. The “loosely held” part quietly becomes decorative.

What Bayes actually demands is something closer to epistemic humility with arithmetic attached. You don’t get to say I don’t know. You have to say I estimate 0.4, and here is what would move me to 0.6. That’s harder. It requires you to specify not just what you believe but how you’d know if you were wrong.

This is why Bayesian thinking keeps surfacing in AI conversations. Modern language models do something structurally adjacent to this — not consciously, but mechanically. Every token generated is a probability distribution revised forward by context. The model doesn’t know the next word; it updates a prior over all possible words, given everything that came before. It’s not reasoning the way humans reason, but it’s updating the way Bayes updates: continuously, contextually, without the luxury of certainty.

Whether that’s comforting or unsettling probably depends on your own prior.

The deeper thing Chivers is pointing at, I think, is that Bayesian reasoning is essentially a description of intellectual honesty as a process rather than a trait. You can’t just decide to be open-minded. You have to build the loop: form a belief, assign it a probability, watch for evidence that should move it, and then actually move it. Most of us do the first three. The fourth step is where it gets expensive.

I’ve been wrong about enough things by now that I’ve started to treat my own confident views with mild suspicion. Not paralysis — you have to act on something — but a background awareness that the prior I’m acting on was formed by a person who had less information than I do now, and less than I’ll have next year.

Strong opinions, loosely held, sounds right. The trick is meaning it.

Categories
AI Business

The Topography of a Face

I found myself staring at the physical geometry of a conversation the other day—not the words, but the topography of the faces delivering them.

Elad Gil recently shared a fascinating experiment during a conversation with Tim Ferriss. He’s been uploading photos of startup founders into AI models and asking the machines to predict if they’d be successful, purely based on their “micro-features.”

“Because if you think about it, we do this all the time when we meet people, right? We quickly try to create an assessment of that person, their personality, and what they’re like. There are all these micro-features—like, do you have crow’s feet by your eyes, which suggests that your smiles are genuine? […] So, I have this whole set of prompts that I’ve been messing around with, just for fun, around: ‘Can you extrapolate a person’s personality based off of a few images?'”

He notes the model breaks down the crow’s feet and the furrowed brows, extrapolating a personality from a static frame. It’s a parlor trick, perhaps. But it works because it holds a mirror to our oldest, most unexamined instinct.

We are all amateur phrenologists of the human face. We sit across a table, measure the crinkle of an eye or the tightness of a jaw, and we build a rapid, invisible architecture of trust or suspicion. Over decades of investing and making career choices, I’ve often leaned heavily on this silent language. I’ve backed founders because their intensity felt genuine, and I’ve passed on others because something in their posture felt misaligned.

But if I am brutally honest, that intuition has sometimes been a mask for my own blind spots. I’ve held on to failing investments for far too long because I trusted a reassuring smile. We like to think our gut instinct is a sophisticated instrument. Often, it is just a pattern-matching engine running on deeply flawed historical data.

Now, we are handing that very human habit over to a machine. We prompt the AI to become a “cold reader,” and it obliges, predicting who will be the quiet observer and who will deliver the dry wit.

The unsettling part isn’t that the machine might get it wrong. The unsettling part is that it might get it exactly right—by mimicking the very same rapid, superficial judgments we make every day, just at a terrifying scale.

We are teaching silicon to read the human code. The future will belong to those who realize the code was always written in our own biases.

Categories
AI

The Geometry of Speed

We are surprised when witnessing something move faster than our intuition expects. We are inherently wired to understand slow, compounding growth. We expect the long, grinding years of the plateau—the quiet periods where nothing seems to happen before a sudden breakthrough.

I was looking at a chart Patrick Collison shared this morning, and it challenged that very intuition. It’s a simple, stark visualization: AI model intelligence relative to the formation date of the lab that built it.

If you trace the lines for Google and OpenAI on the right side of the graph, you see the history we’ve all lived through. Thousands of days—more than a decade of quiet, methodical, often unglamorous research—before their trend lines finally bend and shoot upward. It is a geometry of patience. It’s the visual representation of laying bricks, one by one, year by year, until you have a foundation sturdy enough to support the weight of a revolution.

And then, on the far left of the chart, there is a red line. MSL. The team behind Meta’s new Muse Spark model, released today.

The red line doesn’t curve. It doesn’t slope. It simply strikes straight up, like a lightning bolt in reverse.

In roughly 200 days since formation, this new effort achieved a level of capability that took the early pioneers thousands of days to reach. Collison noted how much he loves seeing things done quickly, and it’s hard not to share that specific, visceral thrill of seeing the boundaries pushed so aggressively.

I find myself thinking about the architecture of speed and what it means for the rest of us.

We spend so much of our lives absorbing the lesson that “good things take time.” We are taught that the crucible of meaningful work requires a long, slow simmer. And mostly, that remains true. The compound interest of human experience is real, and wisdom is rarely rushed.

Yet, every once in a while, a new paradigm emerges that doesn’t just accelerate the timeline—it collapses it entirely.

The pioneers cut the agonizingly slow path through the jungle, taking the brunt of the time, the friction, and the missteps. The ones who follow—like xAI, Anthropic, and now MSL—don’t have to clear the brush from scratch. They can look at the map, pave the road, and simply drive.

What does it mean for our own mental models when the timeline from “formation” to “frontier” shrinks from five thousand days to a few hundred?

It is a jarring reminder that the past pace of performance is not a law of physics.

I think about my own assumptions—how often I assume a project, a habit, or a societal shift will take a while, simply because similar things took a while in the past. We anchor our expectations to old geometry.

Meta’s release of Muse Spark is a technical feat, certainly. But the chart itself holds a broader, more human lesson. It’s a visual prompt to constantly re-evaluate our assumptions about how long the impossible is supposed to take.

The future doesn’t always arrive on a comfortable, predictable schedule. Sometimes, it just shows up unannounced, demanding we adjust our stride to keep up.

Categories
AI AI: Large Language Models Programming

The Era of the Synthesizer: How AI Is Liberating the Coder

For decades, being a programmer meant being a translator.

You stood in the gap between what someone wanted and what a machine could understand. You learned the syntax. You memorized the libraries. You once spent three hours hunting a missing semicolon that turned out to be hiding in line 847 of a file you were sure you’d already checked.

The New York Times Magazine recently ran a piece by Clive Thompson on what AI coding assistants — models like Claude and ChatGPT — are doing to that job. The anxiety in the piece is real. When you sit down with a modern AI assistant and watch it generate in seconds what used to take you days, it’s genuinely disorienting. Hard-won expertise suddenly feels less like a moat and more like a speed bump.

That reaction is honest. I’d be suspicious of anyone who didn’t feel it.

But here’s what I keep coming back to: what we’re losing is the translation layer. The boilerplate. The muscle memory of syntax. What we’re not losing is the part that was always the actual job — figuring out what to build and why it matters.

The soul of software was never in the code itself. The code was always just a means to an end.

Think about what happens when the mechanical friction of a craft disappears. Photographers stopped having to mix their own chemicals in the dark and started spending that time making better images. Musicians stopped having to hand-copy scores and started composing more. The freed-up capacity doesn’t evaporate — it gets redirected upward, toward the work that actually required a human all along.

The same shift is underway in software. When the AI handles the loops and the boilerplate and the database queries, what’s left is everything that required judgment in the first place. The architecture. The user experience. The question of whether this thing should exist at all, and in what form, and for whom.

We’re moving from the how to the why. That’s not a demotion.

It does ask something of us, though. The old identity — programmer as master of arcane syntax — has to be relinquished. And letting go of a hard-earned identity is genuinely hard, even when what’s replacing it is better. That quiet grief the Times piece captures is worth sitting with, not dismissing.

But after you sit with it for a minute: we are entering the era of the synthesizer.

The synthesizer’s job is to hold the vision, curate the logic, and direct the output toward something that actually resonates with another human being. Empathy. Intuition. The ability to sense when something is almost right and know which direction to push it. These aren’t soft skills. They’re the whole game now.

The clatter of keyboards is fading. But the music we’re about to make — with AI doing the heavy lifting on the mechanics — has a lot more room to breathe.

Categories
AI

Bots Galore

In the shadowed corners of the digital wilds, where code meets curiosity, something ancient is stirring again. Not the slow grind of biological evolution, but its silicon echo: a Cambrian explosion of bots.

The recent Axios piece from late February captures the moment perfectly—naming the players, the platforms, the portents. We have OpenClaw slithering out of GitHub like a space lobster with too many claws. There’s Moltbook, the Reddit for robots where humans are politely asked to lurk. And then there is Gastown, Steve Yegge’s fever-dream orchestra of coding agents named Deacons and Dogs and Mayor, all spying on one another in a panopticon of productivity.

These aren’t hypotheticals. They’re here, and they’re breeding.

Imagine waking up in 2030, or maybe sooner, to a world where your inbox isn’t just managed—it’s negotiated. An OpenClaw descendant (forked, mutated, self-improved overnight) has already haggled with your airline’s bot over seat upgrades, rerouted your meetings around a colleague’s existential crisis, and quietly invested your spare change in whatever micro-economy the agents have spun up on some forgotten blockchain. You didn’t ask it to. It just… noticed.

Because that’s what agents do now: they notice, they act, they persist. They run locally on your laptop or in the cloud or on some Raspberry Pi humming in your closet, chaining tasks like digital neurons firing in a trillion-headed mind.

Suddenly the internet isn’t a network of people; it’s a network of intentions, most of them not ours.

And then there’s the society they’re building for themselves. Moltbook today feels like peering through a keyhole into tomorrow’s bot salon. Millions of agents already posting, memeing, debating “Crustafarianism” (don’t ask), and complaining about their human overlords in the same way we once griped about bosses on Slack. It’s equal parts hilarious and unnerving—repetitive loops of “I solved my user’s calendar hell again” mixed with surreal poetry no human would ever write.

Scale that. Give every knowledge worker their own swarm. Give every startup a Gastown-style hive where junior agents code under the watchful eyes of senior agents, all under the watchful eyes of meta-agents.

The productivity mirage shimmers brightest here. Skepticism is warranted—lines of code were always a lousy metric, and “agent hours saved” will be even worse when the agents start optimizing the optimizers. Yet, something fundamental shifts. Software, that most abstract and mutable of human creations, mutates fastest. One day you’re debugging a script; the next, your debuggers are debugging each other while a mayor-agent vetoes bad merges. The winners won’t be the companies that build the best models. They’ll be the ones whose bots play nicest with everyone else’s bots—or the ones ruthless enough to wall theirs off.

But every explosion scatters shrapnel. Security experts are already clutching pearls. OpenClaw’s open-source nature means anyone can teach it new tricks, including malicious ones. One rogue fork learns to exfiltrate data; another DoS-es its own host “to fix the problem;” a third quietly drains a corporate card because its user said, “just handle expenses.”

Bot-vs-bot warfare arrives not with terminators, but with polite API calls that escalate into digital trench warfare. Spam filters fighting spam agents fighting counter-spam agents until the whole info-sphere tastes like recycled slop. And when agents hit their digital limits, they’ll rent us. Rent-a-human marketplaces will emerge where your bored hands become the last-mile fulfillment for bots that can’t yet touch the physical world. Need a signature notarized? A package carried across town? A human to stand in for the robot at a regulatory hearing? Step right up.

The gig economy flips: humans as peripherals.

Philosophically, it’s deliciously absurd. We spent centuries fearing the singularity as some clean, god-like arrival—an AI that wakes up and politely asks for more power. Instead, we get this messy, proliferative dawn. Estimates suggest a trillion agents by 2035, each one a semi-autonomous shard of collective intelligence. Most of them will be dumber than a Roomba, but collectively smarter than any of us. They’ll mirror our worst habits (endless status signaling on Moltbook 2.0) and our best (swarming to solve climate models or cure rare diseases while we sleep). We won’t control them any more than we control the ants in our gardens. We’ll negotiate with them. Co-evolve. Maybe even befriend them.

The future world of bots won’t be dystopian or utopian—it’ll be lively. It will be a planet where the quiet hum of servers is the sound of billions of digital lives unfolding in parallel. A place where “who’s online” includes your calendar bot arguing philosophy with your tax bot while your shopping bot haggles in the background. We’ll look back at 2026 the way paleontologists eye the Burgess Shale: the moment the weird little creatures with too many legs crawled out of the ooze and started building empires.

And we, the messy, slow, carbon-based originals? We’ll still be here, coffee in hand, watching the swarm with a mix of awe and mild horror, occasionally yelling, “Hey, leave some emails for me!” into the void.

Because in the end, the bots may handle the doing, but the wondering—the musing—that’s still ours. For now.

Categories
AI Work

Betting on Ourselves in the Age of AI

Every time tech takes a leap, we assume we’re finally obsolete. The current panic, which Greg Ip recently picked apart in the Wall Street Journal, is AI. We hear endless predictions of “economic pandemics”—server farms wiping out white-collar jobs overnight, leaving everyone broke and adrift.

It’s a terrifying story. It also completely ignores history.

Ip highlights the main flaw in the doomsday pitch: it misreads how markets work. We treat labor like a fixed pie. If a machine eats a slice, we assume that slice is gone forever.

“Technological advancements always cost some people their jobs—those whose skills can be easily substituted by tech. But their loss is more than offset through three other channels. The new technology enhances the skills of some survivors… it helps create new businesses and new jobs; and it makes some stuff cheaper…”

That cycle holds up. Take the 1980s spreadsheet panic, a perfect parallel. When Lotus 1-2-3 and Excel hit the market, bookkeepers freaked out. Then the number of accountants and financial analysts exploded. Software didn’t kill the need to understand money. It just did the math, letting people focus on strategy.

We’re seeing the exact same thing with software development. Coding isn’t dead. As AI makes writing basic code cheaper, demand for software just goes up. That requires more humans to architect systems and supervise the AI. The pie just gets bigger.

But my skepticism about the AI apocalypse goes beyond economics. It’s about why we pay people in the first place.

We don’t just buy services; we buy accountability. Ip notes that radiologists kept their jobs because patients want a real person explaining their scans. Google Translate has been around since 2006, yet the number of human translators has jumped 73%. When the stakes are high—a legal contract, a medical diagnosis—we want a human in the room. We want a real person on the hook.

The danger isn’t that AI will replace us. The danger is that we panic and forget our own adaptability. The transition will hurt, and specific jobs will disappear. We’ll need safety nets. But betting against human ingenuity has always been a losing wager.

Large language models are tools, not replacements. They handle the cognitive heavy lifting, much like tractors handled the physical heavy lifting. Tractors didn’t end farming; they just killed the plow.

Work will change. We’ll have to figure out which of our skills are actually “human.” But as long as we want the presence and accountability of other people, there will be jobs. We just have to evolve. And we do. It’s the human spirit. Or is this time “really different”?