Tag: sjl.us

Categories
Aging San Francisco/California Street Photography

The Permission of Fridays

Doug always walked a half-step ahead, which meant he saw things first, which meant I was usually watching him see them — the tilt of his head, the small pause before he brought the camera up — before I ever turned to look myself. Market Street on a Friday morning has its own weather system, independent of the sky: the gray light fog gives even bright colors.

We would set out with no destination, which was the whole method — what Jay Maisel, who died this summer at ninety-five, called going out empty. Leave the plan at home, he taught generations of photographers, so there’s room left in you to see something you didn’t already expect. You cannot plan to be astonished. You can only put yourself in the path of it and hope.

I have thought about those walks more than I expected to, now that they are gone. Not gone dramatically — no falling-out, no single last Friday we knew was the last Friday. Covid arrived and shut the passes between people the way weather closes a mountain road, and by the time it reopened, the rhythm had broken. We still talk. We just don’t walk anymore, and I have never entirely worked out why something so simple didn’t start back up, the way you’d think a habit that good would insist on its own return. It just didn’t come back.

Susan Orlean, in Joyride, writes about being a writer as a kind of permission — an excuse to linger in places past the point a normal person would move along, and then to go back and report on what was seen. She’s citing Mary Oliver’s instructions for living a life: pay attention, be astonished, tell about it.

A camera grants the identical permission a notebook does. Nobody stops a man with a camera on Market Street and asks him what he’s doing there. The camera is its own credential — I have a reason to be looking at you, at this doorway, at the light falling across these particular twenty feet of sidewalk, longer than is socially normal. Doug and I weren’t tourists and we weren’t reporters and we weren’t, most days, even talking about what we saw until afterward, over lunch. We were two men who had given ourselves formal license to pay attention to a city we loved, as if it might not be there next Friday.

It mostly was there next Friday. Until it wasn’t, in the way that most disruptions to a good practice aren’t dramatic so much as quietly permanent — a scheduling gap that never gets rescheduled, a street that starts to feel unfamiliar again because you stopped walking it with intention. I still have the pictures. A woman waiting at a bus stop with an expression I never satisfactorily explained to myself. The chess player’s hands, mid-reset, waiting on the next stranger. Doug, once, caught by someone else’s lens, walking a half-step ahead of a man he didn’t know was photographing him photographing the city.

The third instruction is the one that survived when the walks didn’t. I don’t walk Market Street with Doug anymore, but I’m telling you about it now, on a blog nobody assigned me to keep for twenty-five years. The credential just changed instruments — camera to keyboard. Orlean’s point, I think, is that the excuse and the obligation were always the same thing. You get to be there because you intend to come back and testify, and the testifying is the toll, due whether or not the place is still there when you go looking for it again.

Doug and I are not going to start walking on Fridays again. I’m too old for that kind of recommitment, and pretending otherwise would just be a nicer way of lying to myself. Plus physically it’s just beyond me now. This essay is itself a kind of substitute — the telling standing in for a habit of attending that got interrupted and never fully repaired.

Mary Oliver’s instructions don’t say what to do when the astonishment outlasts the practice that produced it. Maybe that’s the fourth instruction nobody wrote down: keep telling about it anyway, especially after you’ve stopped going. Or at least remembering.

Categories
AI Writing

The Kitchen Is Not the Meal

A warmly lit home kitchen with late-morning sunlight falling across a wooden counter, where a lemon, fresh herbs, a cutting board, and a bowl sit beside a simple plate of pasta. A closed door recedes into the softly shadowed background.

I watched Katie Parrott talk on Every’s AI & I this week. Natalia Quintero asked her how a working writer uses a model, and Parrott did not start with a manifesto. She started with a kitchen.

The model is the kitchen, she said. The outline is closer to chopping. Composition is closer to heat. None of that matters if the ingredients are stale. You need them fresh, and you need them to be yours, or the plate is just a plate.

I would call what she was doing cooking ideas, then the work after cooking. The phrase is mine, not hers. David Sparks used it years ago — around 2010 or 2012, if I have the years right — when he talked through his writing process. Get the idea into an outline or a map early. Give it little visits. Let it percolate before you try to make sentences. Parrott was doing a later version of that motion with a partner in the room. First the idea gets heat. Then the passes that keep asking whether the spark is still in the sentence.

I was on my morning walk with the interview in my ears when I recognized it. I have been in that kitchen.

Mine always starts the same way. A memory, or an insight that arrived attached to a place or a number or a smell. Not a prompt. The private thing is already there. Then a partner. Back and forth. I say what I noticed. It asks. I answer. It tries a shape. I throw the shape out if it has started speaking for me.

The useful part is not that a model can write. Plenty of models can write. The useful part is the interactive pass that moves a private thing toward a piece a stranger can read, without replacing the spark that made it worth sitting down.

Parrott said working with AI made her fall in love with writing again. For a long time the page had been a slog. With a partner she had energy left for the harder questions. The work felt like exploration again — of the tool, and of her own mind.

I have felt that. Not as a conversion. As a return. The chair is less of a stall. The memory does not have to die there because the next sentence is hard. You can get the thing onto the page and still recognize it as yours when you read it back.

Worth sharing, here, is small. A stranger can take the scene, or the distinction, and not need a sermon. What remains should still work.

Then there is the other room. I cannot point to one essay and one accuser. I can only say what I keep hearing in group talk: writing with AI is a stain. People say they can see slop. They get angry when they think they have found it. The test they are running is origin. Did a model touch this. Not: is the spark still in the sentences. Not: did a person start with something only they had.

Slop exists. A first-draft dump asked to stand as a finished piece is slop. Thin assertions. Rhythm that never lands. A kitchen with nothing in the bowl. That object is real. Thin rhythm is something a reader can taste. That tasting is not the other room. The other room begins when the same reader stops tasting and asks who touched the food.

The pile-on does not separate that object from a cooked one. It looks at the door the food came through and decides. A piece that began as a memory and was walked, question by question, toward the page gets the same verdict as the dump. The jury is not tasting.

I am not asking anyone to love the tool. The origin test cannot do the work it claims. It cannot tell a spark that survived the pass from a paragraph that never had one.

Fresh ingredients, heat, a plate. The kitchen is not the meal. The meal is whatever is left when you sit down to it and the private thing is still there.

Categories
Living Memories

The Depth of the Dimes

The lifeguard came out with a canvas bag, and that was the signal. Saturday morning, Kettering, Ohio, the municipal pool not yet warmed by the day, and forty kids arranging themselves along the edge like something had been rehearsed, though nobody had rehearsed it. We knew the shape of the thing without being told. He would walk to about the middle of the deck, and he would start throwing coins into the water.

Not pennies, mostly. I remember that distinctly, the way you remember the specifics of a thing you can’t explain the pull of. Nickels and dimes, a scattering of quarters, no half dollars that I ever saw hit the surface. Somebody in the recreation department had made a decision about denominations, a budget, maybe, or a sense of what a Saturday morning was worth to forty kids in Ohio in the summer, and none of us thought about that then. We watched the coins fall instead. That’s the part I keep returning to — not the diving, the falling. Coins don’t drop through water the way they drop through air. They wobble. They catch light and lose it. They take their time getting to the bottom, and you’d track one the way you’d track a hawk, losing it, finding it again against the pool floor, memorizing the spot before it disappeared into the general scatter of everything else he’d thrown.

We tried to angle ourselves near the shallow end, obviously. That was the whole strategy, such as it was — get positioned somewhere you could stand, somewhere your ears wouldn’t need to fight the pressure, somewhere the breath-holding would be a formality instead of a genuine risk. But the lifeguard wasn’t interested in making it easy. He’d throw a few coins shallow, just enough to keep the little kids occupied, and then he’d load up the deep end, and that’s where the real money went down. If you wanted more than a couple of nickels, you had to go where you couldn’t stand.

Then the countdown, and then all of us at once, forty kids hitting the water in the same three seconds, which meant the water itself turned against you before you’d even started looking — churned, clouded, chlorine stinging worse than usual because now there were elbows in it, knees, someone’s foot near your face. I wasn’t especially good at it. I want to say that plainly, because I don’t think I was; I’d come up with a handful, four or five coins, sometimes a quarter if I’d gotten lucky with the angle, and that felt like enough. Enough to matter. Enough to walk back to the locker room afterward with my trunks pocket sagging and clinking, enough to spend the rest of the morning transferring nickels and dimes into my actual pants pocket like a kid who’d earned something.

There was a boy down the street whose father worked at NCR, and some Saturdays he’d disappear to Old River instead — a real pool, he made sure we knew, an enormous one, with none of this scrounging-for-change business. I remember being aware of that difference without being able to name what it meant. He had the better pool. We had the lifeguard with the canvas bag.

I came across a piece online the other day, something about swimming and what it might mean, the kind of essay that circles a simple physical act until it turns into a meditation on something larger, and it knocked this memory loose after forty years of sitting untouched. I don’t know why that particular Saturday ritual is the one that stayed. Not the swimming lessons, not the diving board, not anything a person would call a memory on purpose. Just the coins going down, and all of us watching them go, already planning where we’d be standing when the countdown ended.

Categories
AI AI: Large Language Models AI: Transformers Authors Podcasts Writing

The Billboard

The fog was still sitting on the hills when I put in my earbuds and headed out.

Sebastian Mallaby was talking about billboards.

Tim Ferriss had asked him the question he asks everyone: if you could put anything up there, for millions of people to see, what would it be? Mallaby has spent years inside the minds of the people who shaped modern finance — the hedge fund managers, the venture capitalists, the builders of things that changed how the world moves money. He has more material than most people accumulate in a lifetime. He could have said anything.

He said: Prepare your mind.

I kept walking. The houses were quiet in the particular way they get when school lets out for summer — no buses, no car doors, no kids at the corner. Somebody’s sprinklers were running.

The phrase comes originally from Louis Pasteur, who understood something that most people don’t: that chance is not democratic. It does not distribute itself evenly among those who wait. It finds the people who are ready. Chance favors the prepared mind. Pasteur said it, and then he proved it, and then the rest of us spent a century and a half learning it was true.

What struck me about Mallaby’s answer wasn’t the phrase itself. It was the way he said it had kept appearing in his research, surfacing in different decades and different worlds, like a message the material kept trying to send him.

He told the story of Arthur Patterson at Accel Capital. Before a new technology arrived, Accel would work through the implications — what company needs to be built, what founder fits the moment, what the right pitch looks like. So when an entrepreneur finally walked in, when the situation was live and competitive, they already knew ninety percent of what they were hearing. They could move fast because they had already moved slow.

That’s preparation as institutional practice. But Mallaby found the phrase again in a different register entirely, embedded in a single human moment that has always seemed to me like one of the hinge points of our era.

He was interviewing Ilya Sutskever, asking him why he had seen it so quickly.

In 2017, a paper called Attention Is All You Need appeared online. It described a new architecture for neural networks — the transformer — that would eventually rewrite the terms of what artificial intelligence could do. On the day the paper went up, Sutskever read it. And then he ran. He went down the corridor to find his collaborator Alex Radford and told him to stop what he was doing. Everything. Stop. We are going to build a language model on this architecture.

Not someday. Now.

Mallaby asked him how he had seen it so clearly, so fast. And Sutskever’s answer, in its essence, was the same two words: prepared mind.

He had been thinking about the problem of modeling sequential data since his PhD in Canada. For years he had been carrying a question the field hadn’t answered yet. And when the answer appeared — when the transformer showed up on a website one ordinary day — he didn’t have to reason his way toward it. He recognized it. The solution arrived and found a mind that had been waiting for it, that had already cleared space for it, that was already arranged around the shape of exactly this kind of answer.

This is what preparation actually is. Not the accumulation of facts. Not readiness in the generic sense, the vague self-improvement sense. It is the long, patient cultivation of a specific question, held close and kept alive until the answer has somewhere to land.

Mallaby chose that phrase for his billboard because it kept finding him — in the venture capital world, in the AI world, across decades and disciplines and very different kinds of genius. The prepared mind is not a personality trait. It is a practice. It is the work you do before the work arrives.

The sprinklers had clicked off by the time I turned back toward home. The fog was starting to lift off the hills. I was thinking about what I had been preparing for, whether I even knew.

Categories
AI Apple Bicycles History

The Best Lathe in the Shop

Part 3 of 3…

There is a version of this story where Apple is the Wright Brothers.

It is not an unreasonable version. Apple has done the safety bicycle move more times than almost any company in history — taken a technology the engineers built for engineers and brought it down to earth, made it a machine for everyone. The Mac. The iPod. The iPhone. Each one was a wheel coming down. Each one arrived after a period of apparent slowness, of critics saying Apple had lost its edge, of the industry having already moved on to the next thing. Each one was, in retrospect, obvious. Apple had been in the bicycle shop the whole time. You just couldn’t see what they were building.

So when Apple showed its hand at WWDC this week — a rebuilt Siri operating at the OS level, accessing your messages and mail and photos in real time, understanding context across apps, doing things the old Siri could only approximate — it is tempting to read it as Kitty Hawk. The long preparation made visible. The brothers finally leaving the shop.

It might be. It also might not be. That is the only honest thing to say.

What Apple showed was real. The new Siri, built on Apple’s own Foundation Models with help from Google’s Gemini, is not the Siri that became a punchline. It holds context. It moves across apps without being asked. It knows what you were doing five minutes ago and connects it to what you are doing now. It can surface a photo without opening Photos, build a navigation route from an image, draft a message in the tone of the conversation it is joining. These are not features. They are the beginning of an operating system that understands you, which is a different thing from an operating system that executes your commands.

The structure of the keynote said more than the words did. Apple led with fixes before features. iOS 27 is a Snow Leopard update — performance, reliability, the underlying machinery — and Siri AI was presented as one item on a long list rather than the main event. This is Apple’s tell. When they are doing something foundational they tend to understate it, the way a craftsman doesn’t announce the quality of his work but simply does it and lets you find it. The penny-farthing riders called their machine the ordinary. They didn’t think they needed to explain.

But here is the thing about the bicycle shop analogy that the optimistic version leaves out. The Wright Brothers knew what they were trying to build. They had been thinking about flight for years before Kitty Hawk. The bicycle shop gave them the craft knowledge, the physical intuition, the hands-on education in how machines move through space. What it did not give them was the destination. They brought the destination themselves.

The question Apple has not answered for me — the question this week’s keynote raised rather than resolved — is whether they know where they are going. Or whether this has only been a partial reveal and there’s much more behind the curtain?

The OS-level integration is the chain drive. Decoupling AI from the app, letting it run through the substrate the way a chain runs through a drivetrain, is exactly the kind of architectural insight that changes what a machine can do. It is not a feature you add. It is a rethinking of what the machine is for. Every previous AI assistant lived above the operating system, looking down at your data from a remove. Apple’s new architecture lives inside it, which is a different relationship entirely — the difference between a mechanic who reads about your car and one who has driven it for a year.

That is the Coventry precision. The tight tolerances. The discipline of making things that have to work at the level where failure is not an option.

What nobody knows, including Apple, is what you build with it.

There is also this: Tim Cook will not be driving this evolution. He announced that John Ternus takes over in September, which means this WWDC — this particular showing of the hand — is the last one Cook owns. Ternus is a hardware engineer, the man who built the Apple Silicon transition, the person most responsible for the Neural Engine that makes on-device inference possible. He is, in the bicycle shop metaphor, the craftsman who built the lathe. Whether he knows how to use it to make something that flies is the question the next several years will answer.

History is patient about these things. It lets the work speak.

In 1892, two brothers opened a shop on West Third Street in Dayton and started fixing bicycles. They were not trying to change the world. They were trying to make a living, to learn a machine, to understand in their hands what the books couldn’t teach them. The flying came later, and it came because of the shop, not despite it. The shop was the point. They just didn’t know it yet.

Apple has the best lathe in the bicycle shop. They have the chain drive architecture, the on-device precision, the installed base of two billion devices that will carry whatever they build into more hands than any other platform on earth. They have a new set of hands on the wheel starting in September, hands that know the metal intimately, that built the engine the whole thing runs on.

What they do not have yet — or if they have it, they are not showing it — is the image of what they are flying toward.

Maybe that’s the ordinary part. Maybe that’s always been the ordinary part. You don’t know what you’re building until you’ve built it, and by then the world has already changed, and everyone says it was obvious, and they are right, and they are also completely wrong about when the decision was made.

The shop is open. The lathe is running. Work is underway.

What happens when someone finally knows what to make?

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

Beyond the Summary: Using AI to Find the “Friction” in Your Thinking

We’ve reached the “Summary Plateau.”

You see it everywhere. Every browser extension, every note-taking app, and every enterprise LLM now offers a “Summarize” button. It’s the ultimate promise of the efficiency era: Give us the 2,000-word essay, and we’ll give you the three bullet points. But there’s a hidden tax on this kind of efficiency. When we ask an AI to summarize, we are asking it to smooth out the edges. We are asking it to remove the “noise.” The problem is, in the world of ideas, the noise is often where the signal lives. The friction—the parts of an argument that make us uncomfortable or that we don’t quite understand—is where the actual learning happens.

If we only consume the summaries, we aren’t thinking; we’re just acknowledging.

The Mirror, Not the Maker

I’ve been experimenting with a different approach. Instead of asking the model to make the content shorter, I’ve been asking it to make my engagement with the content harder.

I don’t want a “Maker” to write my thoughts for me. I want a “Mirror” to show me where my thoughts are thin.

When I’m wrestling with a complex piece—perhaps a deep dive on the future of venture capital or a philosophical treatise on Arete—I’ve stopped clicking “summarize.” Instead, I feed the text into the LLM and use these “Friction Prompts” to find the sand in the gears:

The Essential Toolkit

  • The “Steel Man” Challenge: “I am inclined to agree with this author’s conclusion. Find the three strongest counter-arguments that this text ignores, and explain why a reasonable person would hold them.”
  • The “Recursive Logic” Audit: “Identify the three most critical ‘logical leaps’ the author makes—points where a conclusion is reached without sufficient evidence. If those leaps are wrong, how does the entire argument collapse?”
  • The “Blind Spot” Audit: “What are the underlying cultural or economic assumptions this author is making that they haven’t explicitly stated?”
  • The “Cross-Pollination” Filter: “Connect the central thesis of this article to a seemingly unrelated field (e.g., Stoic philosophy or biological ecosystems). How does the logic of this text hold up—or fail—when applied to that different domain?”
  • The “Analog Translation” Test: “If I had to explain the core mechanism of this abstract concept using only physical, analog metaphors (like plumbing or woodworking), how would I do it? Where does the metaphor break down?”
  • The “Socratic Sharpening”: “Don’t summarize this. Instead, ask me three probing questions that force me to apply the core logic of this essay to a completely different industry.”

Sharpening the Blade

Summary is about completion (getting it done). Friction is about cognition (getting it right).

When the AI points out a blind spot in an article I loved, it creates a moment of cognitive dissonance. That “click” of discomfort is the sound of a mental model being updated. It’s the digital equivalent of using a whetstone on a blade—you need the friction to get the edge.

As we move further into this age of “Flash-Frozen Cognition,” the temptation to automate our understanding will only grow. But discernment—that uniquely human trait we’ve discussed here before—cannot be outsourced to a bulleted list.

The next time you’re faced with a daunting PDF or a dense long-read, resist the “Summarize” button. Ask the machine to challenge you instead. You might find that the most valuable thing the AI can give you isn’t an answer, but a better version of your own question.

A Deep Dive (Further Reading from the Archive)

If you resonated with this piece on cultivating discernment, you might find these earlier synthesis experiments worth a revisit:

  • On Flash-Frozen Cognition: A foundational post discussing how LLMs are freezing the current consensus, and how we must resist it.
  • The Harvest and the Algorithm: Comparing 1920s ice harvesting to 2020s cognition—the critical shift from scarcity to abundance.
  • The Arete of Attention: A look at the Stoic concept of virtue as the intentional direction of our most scarce resource: focus.
  • Longhand Thinking: Why the physical act of writing is the ultimate antidote to digital velocity.