Categories
AI Business

The Wage of Knowing

In 1973 the Los Angeles Public Library installed a telephone line that worked while the building was dark. Dial H-O-O-T-O-W-L on a rotary phone, nine at night until one in the morning, and a librarian would answer. Somebody wanted to know the boiling point of mercury, or who wrote a poem they half remembered, or how many wives Henry VIII actually had, and a person on the other end of a cord found out. This went on for years. Nobody thought of it as data collection. It was just a service, a courtesy, a woman at a desk with a card catalog in her head.

I worked, in another life, in the payments industry, back when a merchant who wanted to charge your card had to call in and ask permission. There were rooms for this. Banks of phones, a bulletin of stolen numbers updated by hand, a floor limit past which a supervisor had to be found. The people answering the phones were, more often than you would guess, college students. Twenty years old, minimum wage, deciding in real time whether a stranger’s card was good. Nobody trained them for six months first. They learned the bulletin, they learned to listen for something wrong in a voice, and they said yes or no.

I have been driven, recently, by a car with nobody driving it. I noticed the wheel turning on its own and I braced for the wrongness of it. Thirty seconds later I was not bracing. I was looking out the window. The data says I was right to relax: across two hundred and twenty million miles, the cars involved in this experiment cause a small fraction of the serious crashes a human would have caused over the same roads. I did not need the data. I needed thirty seconds.

None of these people knew what they were doing. That is the thing about the librarian and the college student and, for that matter, about me learning to trust a wheel that moves by itself. The librarian was not building a search engine. The clerk was not training a fraud model. He was making rent. Their competence was not evidence, to them. It was just Tuesday. It became evidence later, to someone else, in a room they never saw โ€” the accident logs, the chargeback data, the accumulated record of a million correct guesses that turned out to be exactly the material a system needed to learn the job and take it.

This is the part that is easy to get wrong. It is not that the human failed and the machine succeeded. It is that the human succeeding, over and over, in full view, was the demonstration that the job could be learned. You do not automate a task nobody can do. You automate the one being done well enough, often enough, for long enough that the pattern becomes visible. Doing the job right was never neutral. It was the case being built.

Which brings me to a woman I will call the lawyer, because there are thousands of her and none of them are exactly her. She has a laptop open at her kitchen table. She logs into a dashboard belonging to a company that pairs credentialed people with the AI labs that need them โ€” a doctor here, a banker there, a corporate attorney with fifteen years of contract law behind her. She reads a model’s draft of a merger agreement and marks where it reasons like a first-year associate instead of a partner. She rewrites a clause. She explains, in the margin, why the model’s version would get laughed out of a negotiation. She is paid well for this. More, some weeks, than she billed certain clients.

She knows exactly what she is doing. That is the difference between her and the other three. The librarian did not know she was leaving a trail. The clerk did not know his good judgment would become someone else’s weights. I did not know, thirty seconds into that ride, that I was participating in anything at all. The lawyer knows. She is being paid, by the hour, at a rate that respects her expertise, to make her expertise legible enough that it no longer requires her. The company she works for has a name for this. They call it the reinforcement learning economy, which is a tidy way of saying: teach it everything, and then it will not need to call you back.

She does the work anyway. The rate is good. The work is interesting, in the way that teaching is interesting โ€” you learn what you know by trying to say it clearly enough for someone else to use. Nobody is lying to her. The dashboard does not pretend to be anything other than what it is. She logs off at the end of the session the way anyone logs off after a long day of being excellent at something, tired in the specific way that comes from careful work, and she does not, from what I understand, spend the evening thinking about what she has just fed into the machine.

I keep coming back to the rotary dial. Somebody dialing H-O-O-T-O-W-L at midnight in 1973 could not have imagined the lawyer at her kitchen table. But the shape is the same, if you look at it long enough. A person answers a question well. The answering becomes a record. The record becomes a system. The system answers next time. Nobody in the room ever decided this was the plan. It just turned out, every time, to be the plan.

Categories
AI

The Quiet Setup: MacSparkyโ€™s Robot Assistant and the Unfair Advantage Still Available

A single X post caught my attention this week. It described something quietly happening among a small group of solo professionals. They arenโ€™t working longer hours or grinding harder. Instead, theyโ€™ve built a particular kind of setup around AI that carries much of the load.

While most of us still treat powerful models as clever search barsโ€”typing questions and copying answersโ€”these folks have given the AI a rich folder of context, a briefing file that orients it to their world, connections to their tools, and routines that let it produce real work on its own. The result can look like the output of a small team. From the outside it reads as talent or luck. Up close, itโ€™s mostly architecture.0

The post (from @zephyr_hg) emphasized that this advantage remains available because most people havenโ€™t yet made the shift from one-off prompting to building persistent systems. It landed with me because it echoes so closely the practical territory David Sparks (MacSparky) has been mapping for months in his Robot Assistant Field Guide.

MacSparkyโ€™s Approach: From Chatbot to Persistent Colleague

Davidโ€™s work centers on building a true personal assistant using Obsidian (for a local, plain-text knowledge base) and Claude (in its file-aware โ€œCoworkโ€ or project capabilities). The system isnโ€™t a chatbot that forgets everything between conversations. Itโ€™s designed to remember your projects, preferences, and people; triage email in your voice; handle morning briefings; track tasks; process documents; and support weekly reviewsโ€”freeing you from what David calls the โ€œdonkey work.โ€

The key ingredients will sound familiar to anyone who read that X post:

  • A dedicated context layer (your Obsidian vault or structured folder) holding the details of how you work.
  • Briefing/instruction files that tell the model who you are and what good looks like.
  • Integrations that connect it to email, calendar, files, and other tools.
  • Skills and routines that turn one-time intentions into repeatable, low-friction action.

David has been refreshingly transparent about the journey. He experimented earlier with more fully autonomous agents and even shut one down after learning what felt reliable and aligned. The Robot Assistant Field Guide distills those lessons into videos, workshops, templates, and a starter kit that lets people build without needing to code.

Why This Matters Now

Both perspectives point to the same shift in stance: moving from โ€œHow do I prompt better today?โ€ to โ€œWhat kind of system do I want running alongside me every day?โ€

For me, at this stage of life, that question carries weight. Iโ€™m not chasing maximum output for its own sake. I want arrangements that protect attention and energy for what actually mattersโ€”deep reflection, family history work, thoughtful investing, writing that might be useful to others, and simply being present. A well-designed AI setup doesnโ€™t just save minutes; it changes the texture of the day by reducing context-switching and repeated explanations.

It feels like finding a productive seam in the current moment of AI evolutionโ€”one of those hidden transitions where leverage quietly compounds if youโ€™re willing to build the architecture.

The Door Remains Open

The encouraging message in both the X post and Davidโ€™s teaching is that this isnโ€™t locked behind rare talent or expensive infrastructure. The models are accessible. The patterns are becoming clearer. Whatโ€™s required is the decision to treat AI less like a toy and more like a colleague youโ€™re willing to orient and trust with real work.

I donโ€™t have my own โ€œrobot assistantโ€ fully built yet. Iโ€™ve been experimenting with custom agents, structured daily scans, and ideas like โ€œThe Observatoryโ€ for signal synthesis. Reading these sources side-by-side sharpened my sense of the next layer: giving the system a proper home, clear instructions, and meaningful recurring work.

If youโ€™re a solo professional, creator, or lifelong learner feeling the press of too many small tasks, this is worth exploring. Start small. Build a modest context folder. Write a briefing file that captures how you think. Experiment with one routine. Iterate from there.

The setup that outworks the grind isnโ€™t magic. Itโ€™s deliberate, learnable, and still wide open.


What setups are you experimenting with these days? Iโ€™d love to hear in the comments or on X.


Categories
AI Stanford

The Unit of Production Just Collapsed

The lecture was a Stanford CS session, AI-native companies, Garry Tan walking through what it now takes to build something. He’d rebuilt his old startup, Posterous, in five days on a modest Claude plan. A thing that once required a team and a runway. He said it matter-of-factly, the way you describe something that’s already obvious to you and hasn’t yet reached everyone else.

The argument Tan and his colleague Diana Hu were making wasn’t really about AI. It was about the economics of effort โ€” specifically, what breaks when the cost of turning an idea into a working thing falls by an order of magnitude.

Their framing: AI-native organizations running as closed-loop systems, agents with access to the real artifacts of work, able to iterate without the error-accumulation that comes from handoffs and headcount. Revenue-per-employee ratios of a million dollars or more, with live examples already in the YC portfolio. Document processing, logistics, voice agents for specialized workflows.

What I kept hearing underneath all of it was a quieter claim: the mental model of what a startup requires is wrong.

Or rather, it’s right about the past and increasingly wrong about the present.

The assumptions embedded in “I can’t do this alone” or “we’d need to hire for that” or “we don’t have the bandwidth” โ€” those are load-bearing assumptions, and the load is shifting.

I have some small version of this โ€” not as a founder, but as someone who retired into curiosity. The blog, the reading, the daily effort to keep up with what’s moving: each one is a practice in staying oriented while the map keeps changing.

What I notice is that the constraint has shifted. It’s not information anymore. It’s not even tools. It’s the capacity to ask better questions of the abundance, to know what matters when everything is accelerating.

That’s the thing I find unsettling, yet also genuinely interesting: the skills that remain irreplaceable are the hardest ones to teach, and the hardest to evaluate in yourself. Knowing what matters. Recognizing when an output is almost right and almost wrong. Setting direction in ambiguous conditions and being willing to be wrong about it. These were always the valuable things. They were just obscured by all the coordination overhead that surrounded them.

The students in that Stanford course were asked to build something called a One-Person Frontier Lab โ€” use the best available tools to extend your own reach over ten weeks. It’s framed as an academic exercise. It doesn’t feel like one.

But I’m not building. I’m mostly watching, and thinking about what this radical new fermentation does to everything downstream โ€” to labor markets, to what a company even is, to how we’ll organize work and meaning when the old unit of production no longer applies. Those are slower questions. But they’re the ones that feel urgent to me.

The old excuses are getting lighter. Not that everything is possible โ€” but that the weight of the usual constraints has changed.

What you choose to build, and whether you choose to build it at all, is more purely a decision than it used to be. That’s either clarifying or terrifying, depending on the day and my mood.

Categories
AI Books Writing

The Tax We No Longer Have to Pay

When Carol Coye Benson and I sat down to write Payments Systems in the U.S., one of the first problems we had to solve wasnโ€™t about payments. It was about history.

To understand why the ACH network works the way it does, or why checks persisted decades longer than anyone expected, you need the institutional sediment underneath โ€” the regulatory decisions, the failed experiments, the path dependencies baked in by choices made in the 1970s that nobody thought would still matter in the 2000s. The history is the explanation. Strip it out and you have a description of current practice with no account of why it exists or what it cost to get there.

But history takes pages. And pages test a readerโ€™s patience. So you compress. You make judgment calls about what survives the cut and what gets left behind, and you make those calls knowing that every omission is a bet โ€” a bet that the reader can follow without it, that the thread holds without that particular knot.

Writing it taught me something. The act of compressing, of finding the minimum sufficient version of a complex thing, forces a clarity that living inside the complexity never quite delivers. You donโ€™t fully know what you understand until you have to say it precisely enough for someone else to follow.

But compression is always a loss. You feel it as you write. The version in the book is thinner than the thing you know.


Garry Tan uses a term โ€” โ€œtokenmaxxingโ€ โ€” that initially sounds like jargon from a performance optimization thread. The idea is simple: donโ€™t be stingy with context. Give the model everything. Every source document, every relevant article, every piece of background that a human reader would never sit still for. Let it synthesize rather than guess.

The instinct it runs against is deep. We have spent decades building information systems around compression โ€” search engines that retrieve rather than ingest, executive summaries that stand in for reports, one-pagers that distill months of work into something a decision-maker can absorb in four minutes. All of it was a rational response to a real constraint: human attention is finite and expensive. You couldnโ€™t afford to read everything, so you built filters. The whole architecture of how organizations manage information was designed around that limit.

Tokenmaxxing is a bet that the limit has moved.

The model can read everything. The cost of giving it full context โ€” the uncompressed history, the original sources, the institutional sediment โ€” is low enough now that filtering before the model sees it may introduce more error than it prevents. Youโ€™re potentially discarding signal when you summarize for the model the way youโ€™d summarize for a human. The model doesnโ€™t need the one-pager. It can handle the report.

This doesnโ€™t dissolve the need for curation entirely. More context isnโ€™t always better โ€” models can lose the thread in noise the same way humans do, just differently. The skill shifts from summarizing to selecting: not whatโ€™s the minimum version of this but whatโ€™s actually worth including. Different judgment, still essential.

But the deeper change is upstream of any particular project. The compression we built into every research process, every briefing, every book โ€” that was never the goal. It was the tax we paid for human cognitive limits. Part of the process doesnโ€™t pay that tax anymore.

When I think about writing that payments book today, I donโ€™t think the book itself would change much โ€” it still has human readers with finite patience. But the map we drew before writing it, the synthesis work, the โ€œwhat connects to what across fifty years of regulatory historyโ€ work โ€” that could happen at a different depth now. The understanding you bring to the writing can be informed by everything, not just the subset you had time to read.

The payments book was written entirely for humans, with all the compression that implies. But Tyler Cowen just published what he calls a โ€œgenerative bookโ€ โ€” 40,000 words released free online, paired on the same screen with a Claude interface so readers can discuss, interrogate, and extend it in real time. Heโ€™s writing for both audiences simultaneously now. The human reader and the model that will help that reader go deeper. The text is optimized not just to be understood but to be used โ€” as context, as a jumping-off point, as raw material for a conversation that the author wonโ€™t be in.

Thatโ€™s a different kind of writing. Not better or worse. Different. The compression decisions change when one of your readers has no patience to protect.

Writing still clarifies thinking. That part hasnโ€™t changed. But what youโ€™re clarifying, and who youโ€™re clarifying it for, is quietly expanding.

Categories
AI Business Work

The Curator of Intent

I have always found a certain comfort in the “clatter” of a digital workday. Itโ€™s that specific, rhythmic hum of a mind in motionโ€”the clicking of a mechanical keyboard, the invisible friction of parsing a difficult paragraph or balancing a complex budget. For years, weโ€™ve treated this white-collar grind as our intellectual sanctuary.

But Mustafa Suleyman, now steering Microsoft AI, recently laid out a timeline that suggests the sanctuary walls are evaporating.

From an article in the Financial Times:

โ€œWhite-collar work, where youโ€™re sitting down at a computer, either being a lawyer or an accountant or a project manager or a marketing person โ€” most of those tasks will be fully automated by an AI within the next 12 to 18 months,โ€ Suleyman said.

This isn’t just about efficiency; itโ€™s about a fundamental shift in the “professional grade.” We are entering the era of the autonomous agentโ€”AI that doesn’t just wait for a prompt but “coordinates within workflows,” learns from its environment, and acts. Just ask any programmer that you know how AI is impacted their daily grind.

If Suleyman is correct, the “knowledge worker” is about to undergo a forced evolution. When the “doing” is handled by an agent that can learn and improve over time, what remains for the human? Will the models actually be able to learn from each of us in a personalized way – like an intern learns from her mentor?

โ€œCreating a new model is going to be like creating a podcast or writing a blog,โ€ he said. โ€œIt is going to be possible to design an AI that suits your requirements for every institutional organisation and person on the planet.โ€

It seems like our primary job description shifts from “Expert,” but “Curator of Intent.” We aren’t the ones finding the answers anymore; we are just the ones responsible for asking the right questions.

The next 18 months won’t just be a test of our technology, but a test of our egos. We have to learn to find our value not in the work we produce, but in the vision we hold and the questions we ask. We are shedding the “task” to save the “craft.” I just hope we remember the difference.


As we move toward this curated future, Iโ€™m left with a few questions I canโ€™t quite shake. Iโ€™d love to hear your thoughts:

  1. The Wisdom Gap: Can you truly be a “Curator of Intent” without having ever been a “Doer of Tasks”? If we skip the apprenticeship of the mundane, where does our intuition come from?
  2. The Metric of Value: If output becomes “free,” how should we measure a human’s value in a professional setting?
  3. The Line in the Sand: Is there a part of your workflow you would refuse to automate, even if an AI could do it better?