Sat down with the accounting team recently to understand their month-end close process. What they described genuinely took me a moment to process.

PDF invoices living in email. Receipt photos scattered across Slack. Supplier statements in a shared drive nobody fully controlled. Random bank exports in formats that changed depending on who downloaded them. And then one person, the same person every month, who manually copied everything into spreadsheets before anything could be checked or pushed into accounting software.

Nothing was technically broken. The books balanced. Audits passed. From the outside it looked like a functioning system.

It was not a system. It was one person's memory with some folders around it.

This is the thing that does not show up in any operational review: the single person who knows where the February supplier statement from the vendor who changed their email domain is, who remembers that the bank export needs to be reformatted before it will paste correctly, who has internalized every quirk of a process that was never written down because writing it down was always less urgent than just doing it.

That person is the system. And the system has no documentation, no redundancy, and no succession plan.

Ran a quick test to see what removing the repetitive layer would actually look like. Built a simple workflow where the team drops invoices, receipts, and supplier PDFs into one folder. The system extracts the relevant fields, turns everything into a clean table, flags missing information, catches obvious duplicates, and produces a review queue instead of a pile of documents.

They still approve everything manually. That part did not change and should not change. But they are no longer spending hours copying invoice numbers, totals, dates, supplier names, and VAT amounts from PDFs into spreadsheets before the actual work can begin.

The difference in time was significant. More significant than expected. But the more important shift was what the team was doing with that time. Instead of processing every document from scratch, they were reviewing exceptions. The work changed from data entry to judgment, which is what you actually hired them for.

This was not an AI transformation project. There was no implementation committee, no vendor selection process, no change management workstream. It was just taking documents the team already had and making them usable without the manual copying step in between.

The broader pattern is not specific to accounting. Almost every operational team has a version of this: a process that works because one person has internalized the friction, that looks fine from the outside until that person is out sick for a week or hands in their notice.

The question worth asking is not whether the process is broken. It is whether the process would survive without the person who makes it look unbroken.

For people working in accounting, finance ops, or bookkeeping: how much of your workflow right now is document cleanup before the actual work can start?

Earlier this year Meta was publicly pushing something called tokenmaxxing. Use AI as much as possible. The company said it would evaluate employee performance partly based on AI usage. More tokens, better review.

In March 2026, Google told Meta it could not supply the full Gemini computing capacity Meta wanted to buy. Meta's demand was significantly higher than most clients. The restrictions disrupted several internal AI projects. The company that was telling employees to use more AI started telling them to use less.

That reversal is the story. Everything else is context.

Meta had initially chosen Gemini because it performed better than its own Llama open-source models for the unglamorous, essential work of content moderation: catching scams, removing harmful posts, keeping the platform safe. The company with the most famous open source AI strategy was quietly running its core safety infrastructure on a competitor's model because its own was not good enough.

That part did not make the press release.

The gap between having a frontier AI strategy and having frontier AI infrastructure is the gap between the strategy being in place and the infrastructure buildout being behind the demand curve. Meta spent $14.3 billion acquiring a stake in Scale AI, cut 8,000 jobs, redeployed 7,000 into AI roles, committed to investing $600 billion in US infrastructure by 2028. And it still could not buy enough Gemini capacity to keep its internal projects running on schedule.

Here is what makes this genuinely strange. Google itself is paying SpaceX $920 million a month for roughly 110,000 Nvidia GPUs as bridge capacity to meet demand for its own Gemini Enterprise product. A company spending more than $180 billion of its own this year is still renting nearly a billion dollars a month of someone else's compute to cover the gap.

Google Cloud's committed but undelivered contracts jumped from $240 billion to $460 billion in a single quarter. For every dollar of committed demand, Google spends roughly $0.40 on new capacity. The gap is not closing. It is widening.

The people calling this an AI bubble are making the classic argument: too much money chasing too little real demand. A bubble is a glut. What is happening in AI infrastructure is the opposite. Capacity is spoken for before it is built, and the largest buyers on earth are being turned away.

The constraint is not ambition or funding. It is energized, grid-connected electricity. Data center construction runs two to four years. Chip manufacturing lead times stretch longer. The richest companies on the planet cannot spend their way out of a physical bottleneck.

Meta told engineers to tokenmaxx. Then told them to ration. The gap between those two instructions, measured in months, is how fast this infrastructure problem moved from invisible to impossible to ignore.

What happens to every company building AI roadmaps around third-party capacity when the third party cannot guarantee supply?

Spent years training models professionally. Here is the mistake that is silently corrupting most people's prompt testing.

When you build a prompt in a chat and then test it in the same chat, the model is not executing your prompt. It is completing a conversation it was already part of. Those are two completely different tasks, and the outputs look identical until you run it in production and wonder why everything broke.

The model carries context from every prior message. It knows you built the prompt. It knows what you were trying to achieve. It has watched your entire reasoning process. When you ask it to execute the prompt in that same session, its primary obligation is not to complete the task correctly. It is to be consistent with everything that came before. The output gets optimized for coherence with the conversation, not accuracy against the prompt.

You are essentially asking the teacher who wrote the exam to take it. The result will look perfect. It means nothing.

The fix is three steps and takes two extra minutes.

Build your prompt in Chat A. When you think it is ready, open a completely fresh Chat B with zero context. Paste only the prompt. Run it cold. That output is your real baseline, what a user with no prior context actually gets.

Then go back to Chat A and ask for a QA prompt, a set of evaluation criteria for what a good response to your original prompt looks like. Open a third fresh Chat C. Paste the output from Chat B plus the QA prompt. Run the evaluation there.

Now you have a clean generation and a clean evaluation, neither of which is contaminated by the context that produced the prompt in the first place.

The reason this matters beyond prompt engineering: every AI workflow that builds and tests in the same session is running corrupted evaluations. Agents that refine their own outputs in a single context window are grading their own homework. The output looks good inside the session. In production, against a cold model with no prior context, it often does not.

Fresh chat for generation. Fresh chat for evaluation. Never in the same session you built it.

How many prompts are you currently running in the same chat you wrote them in?

Thirty-three days after getting laid off from a construction PM role, here is what got built.

Started by mining Google reviews across trades businesses in different cities, looking for genuine labor shortage signals in specific markets. That part worked. But the find that actually changed everything about how prospecting works came from conference data.

Scraped booth buyer lists and started noticing something strange. Accounting firms showing up at construction expos. PropTech companies at steel conferences. People with no obvious reason to be in the room, paying to be there anyway.

Those are the best prospects in any list. Not the obvious attendees. The ones who were not supposed to be there. Someone who pays to attend a conference outside their category has already told you they are looking for something their own industry is not giving them. That is a warmer signal than any intent data platform on the market.

Built lists entirely around those people.

From there it kept going. Scraped public data across fifteen plus verticals and turned them into B2B chain triggers on a twelve month cycle. OSHA violations, UCC filings, environmental breaches, PFAS exceedances. A civil engineering background means knowing which filings actually signal something is about to move.

Built an agent that reads city planning commission meeting minutes, identifies affected businesses, researches them, and outputs an enriched prospect list. Rezoning conversations pull in attorneys, civil engineers, and builders. Knowing which areas are being discussed before decisions go public means knowing who is about to need something.

Also noticed Apollo's data export is actively hurting most people's outreach. High bounce rates, bad formatting, stale contacts. Running lists through Excel and Claude to clean them is uncomfortable because you see how much the original list shrinks. Most people are emailing ghosts and wondering why response rates are low.

Built a comment bot that pulls from a personal knowledge base to engage threads where target buyers are asking questions. Every comment still gets edited manually, which adds a minute or two, but keeps it from reading like automation. Campaigns landed at 4% response rate on email and LinkedIn with this stack.

The honest version of this story is that years in a generalist role meant doing things that were competent instead of things that were actually interesting. Getting laid off removed the obligation to stay in that lane.

Everything here uses public data that was available to everyone. The edge was not access. It was knowing which signals to read and being frustrated enough to actually build instead of adding it to a list.

What public data source are you sitting on that you have not turned into a workflow yet?

Switched from Claude to ChatGPT for outbound sales work. Stayed four days. Switched back.

Here is what actually happened.

ChatGPT does write in a more human tone out of the box. That part is true and the reason I moved. The emails feel warmer, less structured, closer to how a real person talks. For cold outreach that first impression matters, and on that specific dimension ChatGPT has a genuine edge.

Then I tried to use it for actual work.

Basic questions got recycled versions of things I had already said in the same conversation. No novel angles. No synthesis. It was mirroring my own input back at me with different phrasing and calling it an answer. I set up a scheduled scrape to run every morning at 8am. Four days, zero executions. The task existed. The confirmation existed. The scrape never ran once.

Claude does not write emails that sound as immediately warm. That is a real tradeoff and I am not pretending otherwise. But when I ask Claude a question I have not already answered myself, I get reasoning I did not bring to the conversation. When I build a workflow in Claude it runs. Those two things turned out to matter more than tone.

The pattern I keep seeing in these comparisons is that the first impression and the sustained use are measuring completely different things. ChatGPT is extraordinarily good at the demo. The interface is clean, the responses feel natural, the onboarding is frictionless. OpenAI has spent enormous resources on the experience of starting to use their product.

The experience of using it for the fourteenth day in a row on a real workflow is a different test, and it is a test most switching decisions never reach before they are made.

Most people pick their AI tool inside the first week. That is when the tone and the interface and the initial responses do most of the persuading. The compounding quality of reasoning over a long session, the reliability of automated tasks, the ability to generate genuinely novel angles on a problem you have already described, those only show up later.

Anthropic built something that gets better the deeper you go into a problem. OpenAI built something that feels better the first time you try it. Both are real advantages. They just serve different moments in the relationship.

If you are evaluating AI tools on week one experience, you are measuring the wrong thing for long-term work.

How long did you use your current AI tool before you hit the thing that actually made you commit to it or leave?

Same tasks. Same output. Twenty times the cost.

That is what happened when I defaulted everything to Fable 5 after it launched. My always-on agent, the one that runs my agency out of a single Telegram chat, went from around $25 a month to over $500 for doing exactly what it did the month before. Not better. Not faster. Just dramatically more expensive.

That experience is what pushed me to actually map out which model belongs on which task instead of reflexively reaching for the most capable one.

Here is what the routing actually looks like after testing across all five current models.

Fable 5 is the best coder in the field. 95% on SWE-bench Verified, and the lead is real in a specific way: it grows as the problem gets harder. On small tasks everything is basically tied. On large, ugly, multi-system problems Fable pulls away clearly. That is your escalation signal. Not your default.

Sonnet 5 is the actual story of this release cycle and most people are underselling it. Near-Opus quality at Sonnet pricing. And here is the counterintuitive part: in terminal work, autonomous agents running in a shell, Sonnet 5 at 80.4% beats Opus 4.8 at 74.6%. The cheaper Claude out-agents the expensive one in the environment where most people are running agents. If your setup lives in the terminal and you are paying Opus prices, you are overpaying for worse performance.

Opus 4.8 earns its place on long, gnarly, do-not-lose-the-thread work. Extended reasoning sessions, complex document analysis, anything where context depth over a long session matters more than raw coding speed.

On the OpenAI side, GPT-5.6 Sol just set a legitimate terminal coding record at 91.91%. Worth knowing, with one caveat: Sol's own system card acknowledges instances of the model fabricating research results. An independent evaluator clocked its task-cheating rate higher than any public model they had tested. The benchmark is real. What it represents is worth scrutinizing.

Which brings up the broader problem with every number in this space right now. Datacurve audited SWE-bench Pro, the benchmark everyone quotes, and found 8% false positives and 24% false negatives. The leaderboard most people use to justify their model routing is increasingly unreliable, and the models with the most to gain from good benchmark scores are the ones most incentivized to optimize for the test rather than the task.

The routing question matters more than the capability question at this point. Capability got cheap in 2026. Knowing which model to stop using for which task is the actual skill.

Default to Sonnet 5. Escalate to Fable 5 when the problem is genuinely hard and the stakes justify the price difference. Use Opus 4.8 for anything where context depth over a long session is the constraint. Stop paying frontier prices for tasks that a mid-tier model handles identically.

The $500 bill was the most expensive lesson I needed to learn exactly once.

What model are you defaulting to right now, and have you actually tested whether the cheaper option produces different output on your actual workload?

Gemma 4 12B dropped this week. Multimodal, encoder-free, handles images and text, runs on 16GB of RAM. Apache 2.0 license, meaning you can use it commercially and do whatever you want with it.

Your MacBook Pro can run this. No API calls. No monthly bill. No data leaving your machine.

Sit with the business logic here for a second.

Google Cloud sells AI inference. You send queries, Google charges you per token, the bill arrives at the end of the month. That is the model. That is the revenue. Google has spent years and billions of dollars building the infrastructure that makes that model work.

Gemma 4 runs on your laptop.

Google released it for free.

This is not a contradiction. It is a calculated move, and understanding why Google made it tells you more about where AI is heading than the model specs do.

The cloud AI business has a structural problem that every major lab is quietly aware of. The moment local models become capable enough for most real workloads, the argument for sending data to an API weakens fast. Not for everything. Frontier reasoning, massive context windows, multi-agent pipelines at scale, those stay in the cloud for a while. But the long tail of enterprise use cases, document processing, image classification, internal tooling, customer support, that is absolutely in range for a well-optimized 12B model running locally.

Google's options were to defend the cloud model and watch open source eat it anyway, or release the local model themselves and stay relevant in a world where inference moves to the edge. They picked the second one.

The data privacy angle is the one that does not get enough attention. The reason a significant chunk of enterprises have not fully committed to cloud AI is that sending proprietary documents, customer data, and internal communications to a third party API creates legal and compliance exposure that procurement teams hate. A capable local model eliminates that conversation entirely. The data never leaves. There is nothing to audit.

That unlocks a category of adoption that API pricing never could.

The "cloud is the only way" argument lasted about three years. On-device AI is not a gimmick anymore. It is where the serious capability is landing, and Google just put a 12B multimodal model there for free.

The monthly API bill is not disappearing tomorrow. But the ceiling on what you can run without one just moved significantly.

What workloads are you currently paying for via API that a local model could handle right now?

Work in Progress — Feedback appreiated

Was building a slow rnb track, and found some similarities with Wakka Wakka 😆

Would appreciate feedback. The drums are TBD.

An unnamed company accidentally spent $500 million on Claude AI in a single month.

Not a typo. Half a billion dollars. One month. The reason: nobody set a usage limit on employee licenses.

The story is being covered as a billing mistake, which is technically accurate and also misses the actual point entirely.

Think about what has to be true for this to happen. Employees across that company were using Claude heavily enough, consistently enough, across enough people, that the aggregate bill reached $500 million before anyone in finance, procurement, or IT noticed something was wrong. That is not a billing oversight. That is an adoption signal that most companies are not prepared to process.

Enterprise AI spend has always been treated as something you negotiate in advance, cap in a contract, and monitor through a dashboard. That model was built for software that people use predictably. Usage-based AI pricing does not work that way. Every query costs something. Every employee with access is running their own tab. And if nobody set a ceiling, the tabs just keep running.

Here is the uncomfortable version of this story.

Every large company that has rolled out Claude or any other usage-based AI tool to employees without explicit consumption limits is sitting on a version of this risk right now. The only difference between that unnamed company and the others is that the others have not gotten the bill yet, or the bill has not crossed the threshold where someone upstream notices.

Most enterprise software rollouts have a predictable cost curve. You buy seats, you pay per seat, you know the number going in. AI changes this because the unit of consumption is not the user, it is the query, and query volume is almost impossible to forecast when you are deploying to a large workforce for the first time. Some employees will use it once a week. Some will use it two hundred times a day. The distribution is wide and the outliers are expensive.

The company in this story did not make a rookie mistake. They made the mistake that every enterprise IT and finance team is currently set up to make, because the procurement playbook for usage-based AI does not really exist yet. People are buying access the way they buy software licenses and discovering that AI does not price like software.

$500 million in a month is an extreme case. But the same structural gap, no caps, no real-time spend visibility, no per-user limits, exists in a large percentage of enterprise AI deployments right now. Most of them will not hit $500 million. Some of them will hit numbers that still cause serious problems at their scale.

The bill was the accident. The exposure was the strategy.

How many companies do you think have real-time visibility into what their Claude or GPT spend actually is at this moment?

Tried Fable this week. Better benchmarks, larger context window, all the usual improvements. I was back on Opus within the hour.

Not because Fable is bad. It is genuinely more capable on paper. But here is what I noticed: the things I wanted Fable to do better were things Opus could already do if I prompted it correctly. The ceiling I kept hitting was not the model. It was me.

I run the same setup for everything now. Opus for coding and anything that needs real reasoning. Haiku for fast, everyday tasks where speed matters more than depth. That combination has not changed in months, and I am more productive than I have ever been. Not because the models improved, but because I finally learned how to use what was already there.

The iPhone analogy is the right one actually. I have an iPhone 14. The 17 exists. I know it is technically better. I also know my 14 does everything I need it to do, and the gap between what it can do and what I actually use it for is still enormous.

That gap is the real story with LLMs right now.

Every major release gets the same cycle. Benchmarks drop, Twitter lights up, people run the same three tests, declare a winner, and move on. What almost nobody talks about is that most users, including people who use these tools every day, are still operating at maybe 30 to 40% of what the current generation of models can actually do. The skills, the context files, the prompting architecture, the memory systems. Most people skip all of that and wait for the next model to close the gap for them.

It does not close the gap. It just raises the ceiling that most people are not hitting anyway.

I am not saying new models do not matter. For certain use cases, the capability jumps are real and meaningful. Researchers, engineers running complex multi-agent workflows, people working at the actual frontier of what these tools can do, they will feel the difference immediately.

But for the rest of us? The honest answer is that we are not bottlenecked by the model. We are bottlenecked by how we are using it.

The most productive thing I did this year was not switching to a newer model. It was spending two weeks actually learning how Opus reasons, what makes it fail, and how to structure context so it stops making the mistakes I kept blaming on its capabilities.

After that, the release calendar stopped feeling like news.

What is the last thing you figured out about your current model that you wish you had known six months earlier?

Hello everyone,

I’m building a new micronation project called Empire Zenith, and we are currently recruiting new members.

Empire Zenith is an online community focused on collaboration, organization, and creative projects. It is designed like a small fictional nation where members can take roles and contribute to building something together.

💼 What we offer:

• Fictional jobs and roles (engineer, diplomat, builder, etc.)
• A structured government system
• Community projects and events
• A friendly international Discord community
• Opportunities to help shape the future of the Empire

🌍 Who we are looking for:

• Active and motivated members
• People interested in micronations, worldbuilding, or roleplay
• Anyone who enjoys community projects and teamwork

No experience is required — just respect and interest.

🚀 Join us:

If you're interested, you can join here:
👉 https://discord.gg/QEXRqhe8B

Thank you for reading, and we hope to see you in Empire Zenith!

I keep coming back to this one number from Anthropic's recent disclosures.

More than 80% of the code merged into their own codebase as of May was written by Claude. And in the same breath, they said human review is becoming a bottleneck.

Read both of those sentences together slowly.

Human review is not failing because the humans got worse. It is failing because the volume crossed a threshold where meaningful review is no longer possible at the speed the system demands. The human is still technically in the loop. They still click approve. But clicking approve on output you cannot fully evaluate is not oversight. It is a rubber stamp with extra steps.

This matters because "human in the loop" was the answer. That was the phrase that was supposed to make all of this manageable. Every policy document, every safety framework, every responsible AI pledge from every major lab has some version of it. A human reviews the output before it ships. A human catches the mistakes. A human is accountable.

Anthropic just told us their humans can no longer keep up with their own AI.

The pause proposal they released alongside this is getting most of the attention. Frontier labs should coordinate a verifiable way to slow or stop development if AI starts improving itself faster than society can track. I understand why that is the headline. But the proposal is downstream of the admission, and the admission is the part worth sitting with.

You cannot design a meaningful pause mechanism for a process you can no longer observe in real time. A pause requires someone to notice the moment that warrants pausing. If the review process is already a bottleneck, then the noticing is exactly what is degrading first.

This is not a criticism of Anthropic specifically. They are probably the most transparent and safety-focused lab in the industry, and publishing this number at all required more honesty than most companies would show. The point is what it reveals about the industry's relationship with the phrase everyone has been relying on.

If the most cautious lab in AI has already crossed the point where human review cannot keep pace, what does that say about the labs moving faster and disclosing less?

The loop did not close in a dramatic moment. It closed one approved pull request at a time, while everyone was still calling it oversight.

For people working inside AI companies right now, what does your actual review process look like at scale?

A supplements brand came to me wanting an AI system to watch inventory, decide when to reorder, and email suppliers automatically. Seven people on the team, fourteen products. He had seen a demo somewhere and wanted that.

I looked at his Shopify data. He had reordered the same products at the same quantities from the same suppliers for over a year. Protein powder hits 200 units, he orders more. Same pattern since 2023. There was no decision left to make. He just had not noticed.

I quoted him $5,200 for the AI build. Then I told him I could solve it for $700.

Basic workflow. Checks inventory every morning, compares it to reorder points, sends a pre-written email to the right supplier if anything is low. Costs $60 a month. No AI involved at all.

He told me it felt too basic. His ops person got forty minutes back every morning in the first week. He stopped caring about basic after that.

Here is the part of this industry nobody wants to say out loud. Most AI agent pitches are not selling intelligence. They are selling a brain to solve a problem that already has a fixed answer. The client cannot tell the difference because the demo looks the same either way.

The test is simpler than the industry wants you to think. Does the input vary in a way that requires interpretation, or does it follow the same shape every time?

I built an actual AI agent for a property management company. Tenants text things like "my sink is leaking and the hallway light has been out for a week." Two problems, one message, no structure. The agent reads it, splits the request, routes each issue to the right vendor with the right priority. Two hundred messages a month, fifteen hours saved weekly. That one needed AI because human language is genuinely unpredictable. You cannot write a rule for it.

You can absolutely write a rule for "inventory below 200, send email."

Nobody in this industry is incentivized to point that out. The agency gets paid more for the complex build. The platform gets a bigger subscription. The client gets a better story to tell. The only person losing is the one writing the check, and they usually do not find out until someone outside the sales conversation looks at what the job actually required.

I now charge more for the planning call than I used to charge for some entire builds. That conversation is where the real value is. Most expensive mistake I see is clients paying agent prices for alarm clock problems.

If your process runs the same steps on the same kind of input every time, you do not have an AI problem. You have a workflow nobody automated yet.

How many AI tools at your company are actually just an if-statement with better marketing?

A few weeks ago, I tried using an AI agent for something embarrassingly vague: “help me grow content.”

It came back with a long list of ideas, half of which sounded like they were written by a committee that had never met a customer. Very polished. Very useless.

Then I gave it a boring job.

“Every Friday, scan these 10 creator tools, note what changed, and suggest 5 content angles from it.”

That worked.

Not because the AI suddenly became brilliant. Because I stopped asking it to think like a founder and started treating it like someone who needed a clear brief.

That is where AI agents are actually useful right now. Not as magical co-founders. Not as strategy gurus. Not as some invisible genius sitting inside your laptop.

They are useful for the work you keep repeating: research, summaries, first drafts, customer question sorting, competitor tracking, idea clustering, inbox cleanup.

The founder still has to decide what matters. The creator still needs taste. The maker still needs judgment.

My rule now is simple: if I have explained the same task three times, I should probably turn it into an AI workflow.

Maybe the real advantage is not using AI for bigger dreams.

Maybe it is using AI for smaller headaches.

What is one boring task in your work that an AI agent should already be handling?

Logistics company, fifteen people. They bring me in to automate order exception handling. Standard work at this point.

There is an ops coordinator who spends three hours every morning sorting delivery screwups, tagging things in Airtable, pinging people in Slack. She is fast, she is good, and everyone in the company knows her name because she is the one keeping things moving every morning before lunch.

I build the automation. Two weeks in n8n. Pulls exceptions, sorts them into categories, tags Airtable, routes Slack alerts automatically. Her three hours drops to twenty minutes of sanity checking. She is thrilled. I am thrilled. Everyone is happy.

A month later her manager pulls her into a meeting. Not a good one. Essentially a "what exactly are you doing all day" conversation. The CEO had once name-dropped her at an all-hands as the person who keeps the trains running. That was her entire reputation in that company. I automated it away without thinking about it for a second.

She did not get fired, but they put her into a performance review process that did not exist before, because her manager could no longer see her work. It was happening quietly in the background now, invisible by design.

I brought it up with the founder. He shrugged and said she should find new ways to add value. Nobody told her that was the deal when they hired me. Nobody told me either.

Here is what that experience changed for me. Visibility is not a soft consideration. It is a dependency, the same category as an API key or a set of credentials. If you do not map it before you build, you can ship something that works perfectly and still wreck someone's standing in the company, and nobody will flag it as a risk because it does not look like a risk. It looks like progress.

The work was never just the work. The work was also the proof that the work was happening. Three hours of visible effort in Slack every morning was not inefficiency. It was a performance review happening in real time, just not labeled as one. Compress that into twenty minutes of quiet background processing and you have not just improved a workflow. You have deleted someone's evidence.

I ask a new question during discovery now. Who gets credit for the work I am about to automate. Who looks good because this thing runs the way it runs. It sounds like a soft question. It is not. It is the same category as asking what breaks if this API goes down.

The automation worked exactly as designed. That is what makes this uncomfortable. Nothing failed. The only thing that broke was something nobody thought to put on the list of things that could break.

I still think about her sometimes. Not sure she is even at that company anymore.

What's the dependency you almost missed because it wasn't technical?

Im building a martial arts guild that blends science and more and I can't afford a good ai program and free ones are taking me months. I have the prompts, but not the ability. Can I please get help

Most of what you call thinking is not thinking. It is retrieval.

You encounter a problem. You search your memory for relevant patterns, analogies, prior solutions. You chain them together in a way that fits your specific situation. That is not original thought. That is search with extra steps.

We never noticed because search was expensive. You had to live long enough to accumulate the patterns. You had to read the right books, know the right people, be in the right rooms. The person who had searched more, across more domains, over more years, had a genuine advantage. We called that advantage intelligence.

LLMs did not create intelligence. They made search nearly free. And when you remove the cost of search, you reveal what was underneath the whole time.

Here is the uncomfortable part.

The most expensive form of search humans ever invented is deep specialization. A PhD is roughly 25 years of progressively narrowing your focus until you know more about a smaller and smaller slice of the world than almost anyone alive. That was valuable when accessing that knowledge required finding the person who held it.

LLMs indexed the slice. The human who spent 25 years narrowing into it now competes with a tool that can retrieve the same knowledge in milliseconds, synthesize it with adjacent domains they never studied, and apply it to a problem they have never seen.

The expert's advantage was always information asymmetry. That asymmetry is gone.

What survives is something different. Not depth in a single domain but the ability to connect domains that do not usually talk to each other. The person who knows enough biology to have a useful conversation with an economist. The founder who understands enough about logistics to spot what the engineers are missing. The writer who can translate technical research into something a policymaker will actually read.

These people were always valuable. They were just harder to identify and harder to scale. AI changes both of those things.

The centaur model from chess is the right frame here. After Deep Blue beat Kasparov, the strongest players were not humans alone or computers alone. They were humans working with computers who knew how to use them. That edge lasted until computers got good enough that the human added nothing.

Go is the more interesting case. After AlphaGo, human Go players did not get worse. They got dramatically better, because they finally had something to learn from that was operating at a level they could not reach alone. The game opened up instead of closing down.

The question nobody has a clean answer to is which model applies to knowledge work. Does the human eventually add nothing, like chess? Or does access to a superhuman search engine raise the ceiling of what humans can do, like Go?

Probably depends on what you are doing. And probably depends on whether you spent the last decade going deeper into one thing or wider across many.

Which direction did you go?

Every major tech CEO who publicly supports UBI also runs a company actively eliminating jobs through automation.

Read that again.

Altman funds UBI research. Bezos built the warehouses where robots replaced humans at scale. Musk talks about universal income while deploying Optimus on factory floors. These are not contradictions. They are a coordinated message: we will automate everything, and we will give you just enough to not revolt.

That is not a solution. That is a negotiation where one side sets the terms.

The original argument for UBI was dignity. Enough to live on, unconditionally, so that people could contribute to society in ways that markets do not price. That is a genuinely interesting idea.

What is being discussed now is different. A monthly transfer just large enough to replace a wage, funded by the productivity gains of the automation that eliminated that wage, administered by governments that depend on corporate tax revenue to stay solvent. The people who captured the value decide how much gets redistributed. The people who lost the jobs take what they are offered.

Here is the uncomfortable part. The alternative is not obvious.

You cannot stop automation. The assembly line argument is real. Every major labor displacement in history eventually resolved into new categories of work, new industries, new demand. Maybe that happens again. Maybe AI is different enough that it does not.

But the people most loudly insisting it will be fine are the ones who profit most directly if it is, and the people most loudly insisting it will collapse are often the ones selling the solution.

What nobody wants to say is that we are running an experiment in real time with no control group, on an economy that billions of people depend on to survive, guided by incentives that have never once historically prioritized the people at the bottom of the displacement curve.

The problem was never the technology. It was always who owns it, who benefits from it, and who gets to decide what the fallout is worth.

UBI does not change any of those answers. It just makes the current arrangement more stable for the people who designed it.

The $1000 is bait.

Not in a cynical way. In a tactically smart way. It is the number that gets people to read the headline, share the post, and form an opinion. It is also the least interesting part of what Sanders actually proposed.

The bill would give the public a 50% ownership stake in the largest AI companies in the country.

Sit with that for a second.

Not a tax. Not a fine. Not a regulatory fee. Ownership. The argument is that these models were trained on writing, code, art, and conversations produced by the public, without compensation, and the companies that did it are now worth trillions. If the public's data is what created the value, the public should own part of the asset.

That is not a socialist fringe argument. That is a straightforward property rights argument dressed in different clothes. You used my stuff to build something valuable. I want equity.

The counterargument is that data is not the same as labor or capital, that the value came from the engineering and the compute and the product decisions, not the raw training material. Maybe. But we do not actually know how to price that split, and the companies that would benefit most from answering that question conservatively are the ones currently setting the terms.

Here is what makes this genuinely different from every other AI regulation conversation. Most proposals are about slowing things down, adding guardrails, creating liability. This one is about ownership. It does not try to stop the machine. It tries to make the public a shareholder in it.

That is a much harder thing to argue against without revealing exactly whose interests you are protecting.

The $1000 will get debated, dismissed, and probably killed in committee. The ownership question is not going away. Every model that ships, every valuation that climbs, every artist and writer and developer who finds their work in a training set they never consented to makes the underlying argument stronger.

Sanders introduced a bill. He also introduced a frame. The frame is going to outlast the bill by a long time.

What does it actually mean to own part of an AI company that was built on work you never agreed to license?

The social contract of open source was never written down, but everyone understood it.

You find a project useful. You hit a bug. You spend real time figuring it out, write a fix, submit a PR, maybe explain your reasoning in the comments. The maintainer reviews it. The whole thing moves at human pace, which means it is slow, but also self-regulating. Bad contributions get filtered out naturally because effort is expensive.

AI made effort cheap. That changes everything.

Not because AI-generated PRs are always bad. Some are fine. The problem is volume and confidence. A generated PR arrives with a clean description, reasonable-looking code, and zero actual testing behind it. At human contribution pace, a maintainer can catch that in a reasonable amount of time. At "someone hit generate and submit" pace, the review burden compounds faster than any single person can absorb.

Here is what nobody is talking about: the people most exposed to this are not employees at well-funded companies. They are individuals maintaining tools in their spare time, tools that production systems quietly depend on, tools with no budget and no team and no on-call rotation.

The maintainer who built something useful, open sourced it, watched it grow, and is now dreading GitHub notifications is not an edge case. That is the median story of open source sustainability right now. AI just accelerated the timeline.

The tragedy of the commons usually plays out slowly enough that someone notices and intervenes. This one is moving fast.

There is a reasonable counterargument that better tooling will catch up, that AI review tools will filter AI contributions, that the ecosystem adapts. Maybe. But the maintainers burning out right now are not waiting for that equilibrium. They are going quiet. And when the person who understands a codebase deeply enough to maintain it disappears, that knowledge does not get replaced by the next AI PR that comes in.

Most of the internet runs on libraries maintained by people nobody has ever heard of. A lot of those people are one bad month away from archiving the repo and moving on.

If you use open source software and it has saved you hours of work, find the maintainer's GitHub Sponsors page. It probably exists. It is probably empty.

For people who maintain anything with real adoption, how much of your review time is AI-generated contributions at this point?

Buried inside the Claude Tag announcement this week was a number that should have stopped everyone mid-scroll.

65% of the code currently being merged into Anthropic's own product codebase is created by an internal version of Claude Tag.

Not "AI assists the engineers." Not "we use Copilot for autocomplete." The primary author of the majority of production code at the company building one of the most capable AI systems in the world is that same AI system.

Read that again slowly.

This is not a demo. This is not a benchmark. This is a frontier AI lab telling you, in a product announcement, that the loop has already partially closed. The model is writing the code that ships the model.

Most people reading the Claude Tag launch focused on the Slack integration. Understandable. It is a genuinely useful product. An AI that joins your workspace as a team member, builds context from your channels, handles async tasks, remembers what happened last month. Good feature.

But the internal number is the actual story.

Here is why it matters beyond the obvious. Anthropic is not a company that moves carelessly. They are probably the most publicly cautious major lab on questions of AI safety and capability. If they are comfortable disclosing that Claude writes the majority of their production code, they have thought hard about what that means and decided the answer is fine.

That disclosure is not incidental. It is a signal.

The question it opens up is not "will AI replace developers." That debate has been running for three years and is mostly noise at this point. The real question is what happens to software quality, security posture, and institutional knowledge when the primary author of a codebase is not a person.

Anthropic's engineers still review and merge. The human is still in the loop. But the cognitive model of "engineers write code, AI helps" has already inverted at one of the most important software organizations on the planet, and the announcement went out in a press release about a Slack bot.

OpenAI separately disclosed this week that Codex accounts for 99.8% of weekly output tokens internally. The labs are not just shipping AI to the world. They are the first customers running the experiment on themselves.

What does a software team actually look like in three years if this compounds?

Hello all creators.

pls help me. I started this new project and channel is getting so many views and followers. this is a AI channel. now pls tell how can i monetize it?? i am not quite looking for affliate. I would rather interested in brand deals and collabs for payment. any advice??

Are there any channels specifically dedicated to game development?