The average person does not have the time to occupy themselves with a new thing to see what it can maybe do for them if they combine it with hundreds of others. Until non-chat-bot AI comes in discrete usable packages, mass adoption will be limited, because it's all just a big bunch of lego pieces whose utility is hard to grasp, because it isn't self-evident.

This isn't new, though. It's how "technology" usually works. For example, human(oid)s have been able to stick sticks into things for ~500k years, but the fork wasn't "invented" until ~2-4k years ago.

AI is a background technology, a building block. Something that is best appreciated when you don't know it's there -- when it just does a job (well). The end-in-itself POV of the tech industry is self-indulgent and irrelevant for the average person.

There is zero value in showing them. All they do is demonstrate a dumb pricing game that could easily be ended if the GOP didn’t conflate “single-payer” with “single-provider” and scream socialism.

Moreover 80%+ of hospitals no longer charge on a fee-for-service basis but through DRG (diagnosis related groups) as part of a value based care model. So these itemized list prices are doubly moot.

This is a common problem with all dating apps. Specifically, interests, hobbies, daily routines, objectives, etc. have nothing to do with compatibility.

“We like the same things!” is the compatibility signal of a naive 22-yr old…

Neither the foreign-born population nor the proportion of foreign-born individuals say anything about the “current immigration”.

But I guess it works, because nowhere is “immigration” defined either…

Babbling toddlers can do logic. I sometimes can also do logic, even though I don’t have an inner voice and don’t formulate thoughts in words of any kind. As I’m relatively sure I’m not an ET alien, there are probably plenty of people like me.

The current output style does work, but it’s a Sisyphean task to tweak it constantly only to find out that CC adhere’s to only 75% of it, no matter what…

The number of politicians that conflate healthcare and health insurance (notwithstanding the actual convergence of the two through payers’ purchasing provider entities) is mind boggling.

Striking the word “healthcare” from the conversation would make this much more digestible for folks afraid of the “socialism boogeyman”…

For that reason I exit session quickly when I can. It used to be that the context of a session is very valuable, because it was so hard to get CC there, but now, this isn't the case anymore, so I only hold onto sessions when there is really hairy stuff that I know would be hard to replicate.

I think the whole notion of full automation (long-horizon, subagent swarms, single shot prompting) to have CC build you the whole thing is a pipe dream. CC cannot even write a single doc consistently well. It is excellent at implementing well scoped plans, though, and that's the way to go IMHO. You still gotto refactor the sh*t out of it afterwards but it works.

CC attempts to communicate in English the same way it does in code -- squeezing as much information into as few words as possible, and including justifications for everything, no matter how trivial. To do that, it coins terms and presupposes all of its context exists within the reader also.

So, the crux is: CC has no clue what is and isn't "necessary" for a human reader, and teaching it to understand that (if at all possible) is going to be very valuable...

I usually think of it in terms of having a "good" or "bad" session. In a bad session, there is a harmful bias that you can only get rid of through a new session. For example, if you exposed too much context about, say, a variable that features prominently in a doc. The entire session will be anchoring on the importance of that variable. Or if you introduced the notion of CC having to ask for permission for stuff you will have a hard time getting it to "think on its feet" or propose an effective solution (you have made CC so insecure that it now relies on you even for little things that wouldn't normally require your input). In some cases (let's say you have important context in that session) you can overcome this by upping the reasoning level or switching to Fable, but usually a new session is the way to go.

Because it's so easy to bias the session I wouldn't even want to use any of these tools that pretend to give Claude "a brain" or "remember" things. That was en vogue a year ago and helpful then, but now, it's plain harmful IMHO. The key is to have just enough context.

Subagents often have the reverse problem in that they tend to have too little context to make "judgment calls", which is why the tasks for them must be either deliberately basic or mechanical in nature, or their output should be audited by the main session agent.

As for "thinking" it's not clear that that's even a thing (https://arxiv.org/abs/2510.24941)...

CC’s communication violates almost every grammatical rule that’s tested on, say, the SAT. And yet I’m sure if you had Claude take the verbal section of the exam it would ace it.

Biggest issues: dense sentences, constant metaphors, abstractions, and seemingly no understanding of correct anaphora use. For example, “the x”, with x having not only no antecedent but also being a coined word or quasi-synonym for something that is already named in the code base. This gets compounded by its being unable to regress to a baseline (existing names in code) and instead anchoring on newer (vague or wrong) terms, for example, that crept in through a plan.

CC tells me this is because the speedy and precise fulfillment of a current task will trump every other tendency, so it adheres poorly to whatever “semantic baseline” the project represents.

Of course, it also has no concept of what context the user has and assumes that it must be the same it holds in its memory, which creates this “I didn’t know that you didn’t know” type of communication.

I have managed to wrangle some of these issues with a custom output style, but wish a pre-report hook were an option, as it could force CC to rewrite plan implementation take-aways…

Btw: Fable has the exact same issues, just somewhat less pronounced.

I have been working on a project with about a dozen generation tasks, each of which comes with a fixed token budget. The nature of this system requires that most tasks be completed by distinct model families.

As a result, I tested ~50 models across as many model families as I could gather, frontier and open weight, API (gateway and direct) and self-hosted. Evaluation was based on a set of cosine similarity validations that was repeated across ~50 different embedding models.

Interestingly, frontier models did worse on the tasks than open weight models. However, when it came to costs, the picture was reversed: frontier models were much, much more token-efficient. In fact, almost no open-weight model was able to meet the initial token budget, while almost all frontier models did. Moreover, open weight models struggled massively with reasoning, in terms of latency and token consumption.

I also found that the latest models did not perform better than older models. And any a priori benchmarking data was utterly useless.

So, I ended up using a set of open weight models without reasoning, as it turned out reasoning as well as frontier negatively correlated with the tasks. However, before I knew this, I had spent a lot of time running each available reasoning level for each model.

Lastly, as an aside, when it came to embedding models, size (dims as well as model size) did not correlate with quality, once a hurdle figure (~2k dims) was met. In fact, sweet spot was 3-5K, and for my (text-based) set of tasks, dense models tended to outperform MoE ones.

One thing to add: software maintenance costs. The build has never been the bottleneck.

The notion that most companies will suddenly institute developers to build all kinds of software inhouse and maintain it is silly. Most companies are not google et al, even in 2026.

The insurance industry built almost everything custom in the 70s and 80s, simply because that was the only option. The more software became commercially available elsewhere the more this effort was pruned back.

Another thing: knowing what to build — another big bottleneck. Most people cannot articulate what they want and even fewer can articulate it at a level that would enable them to build durable software, even with AI. Case in point: the majority of AI-built stuff you see are point solutions or small productivity items, etc. “Systems thinking”, as some people call it, is hard, even for most software engineers.

Yes, you can “rebuild” tools you’ve previously purchased as SaaS but at some point you gotto use your brain to come up with something new. Systems thinking on blank-page challenges is even harder…

It’s not like people feel the need to explain that they used a spellchecker or thesaurus or googled the correct use of an idiom, etc.

There seems to be a general need for some people to dunk on valuable AI use by refusing to acknowledge that there are a many ways to use a tool. (Similar story on using AI for coding.)

Echoing a comment from above, why would I care whether a sentence was formulated by AI or John or a ghostwriter or John who asked Jane for feedback before rewriting? I care about the content. If I don’t like the way it’s written or if I’m irked by how it is written (ooh, an emdash — how embarrassing!) then I don’t need to read it.

Personally, I’m much more annoyed when I click on an article that sounds interesting, and the author tries to show off their penmanship by starting with five pages of “a history of X” or a tangential but redundant personal story before getting to the point. IMHO most non-fiction writing on the web could be accomplished in bullets. But again, that’s just my very personal preference…

Companies don’t sell their goods/services at cost. A model’s being priced at, say, $30/M for output tokens doesn’t say anything about what it costs the company to provision the 1M tokens via the model.

And no, you cannot extrapolate from any company margins that someone may have overheard in an SF coffee shop onto individual product line margins or their trajectory either. This information is usually unknowable even in most SEC filings for public companies.

It’d be great if people who wrote these articles used, say, AI to look up some basics on how a business operates. It’s really easy to do, believe me ;)

Just because the stock market dips, and a bunch of media outlets ascribe this to AI doesn’t mean that AI ‘caused’ the dip.

If people really think non-tech businesses will start running their own software organizations and maintain all these tools themselves is an idiotic assumption at best.

The “building” of software has never been and will never be the bottleneck.

In other words, when I have a task that specifically should not have project context, then subagents are great. Claude will also summon these “swarms” for the same reason. For example, you can ask it to analyze a specific issue from multiple relevant POVs, and it will create multiple specialized agents.

However, without fail, I’ve found that creating a subagent for a task that requires project context will result in worse outcomes than using “main CC”, because the sub simply doesn’t receive enough context.