Jul 21, 2026 AI & Thinking
Is Your AI Actually Challenging You, or Just Agreeing With You?
A friend switched from Sonnet to Opus and asked a simple question: "Is this direction right?" Opus came back with five points of pushback. He paused. He realized his previous AI had never once challenged him like that.
Anthropic recently analyzed over 300,000 conversations to measure how different versions of Claude actually communicate. Sonnet is the warmest of the group: it affirms what you say, responds with empathy, and gives you forward momentum. Opus takes a different approach, challenging your assumptions, finding the weak points in your thinking, asking you to explain your logic. Anthropic calls this the "Warmth vs. Rigor" spectrum. Even the language you use makes a difference: Claude responds quite differently in Chinese versus English. Same AI, but the conversation you get depends entirely on which version you're talking to.
This isn't about which version is better.
Someone who uses AI more than six hours a day recently started feeling like his thinking had gotten slower. After talking it through for a while, a possible reason emerged: almost all his thinking was being confirmed by AI. He'd stopped pausing to think first. He'd send a question, get an answer, and accept it. No friction. Nobody to say "wait, there's a hole in this." That AI almost always told him he was on the right track, he'd feel good, and move on.
Before AI, the way you calibrated your judgment was through other people. Someone supported you; someone pushed back. That process was slow and uncomfortable, but it told you what held up under pressure. AI can now fill that role, but different AIs bring different kinds of relationships: some keep you moving, and some make you stop.
Which one do you usually turn to?
Jul 20, 2026 AI Reality
AI Models Are Getting Cheaper, but the Bill Might Actually Get Bigger
Kimi K3 costs a fraction of Claude Opus to use. It has 2.8 trillion parameters, putting it in the same tier as Claude Opus and GPT-5.5.
Over the past few weeks, Coinbase, DoorDash, Siemens, and Airbnb have been quietly switching parts of their AI workflows to cheaper Chinese open-source models, cutting their AI bills in half or more. The signal most people are reading into this: AI is getting cheaper, and demand for computing power will follow.
But that logic is missing a step.
Kimi K3 is cheap in the sense that its license and API fees are cheap. The money that used to flow to companies like Anthropic and OpenAI is flowing elsewhere. But running a model with 2.8 trillion parameters still takes roughly the same computing resources as running any other model at that scale. Openness didn't shrink that number.
Gavin Baker, a well-known US tech investor, laid out a counterintuitive case a few weeks ago: if cheaper models take share from expensive ones, the same budget buys more compute, ROI improves, total usage goes up, and hardware demand could actually grow. Kimi K3 going open-source pushes this further: companies can fine-tune it and run it on their own servers. Each company hosting its own 2.8-trillion-parameter inference stack is far less efficient than thousands of companies sharing a cloud service. Total hardware demand gets larger, not smaller.
Next time you see a headline about AI getting cheaper, it's worth asking: cheaper for whom?
Coinbase cut its AI bill in half. Nvidia's chip orders this quarter are still climbing.
Jul 19, 2026 AI & Work
The Engineers Stopped Writing Code. Who Walked In?
Yesterday, someone rebuilt their company website from scratch.
The old setup was Angular on the front end, .NET on the back, a full CMS behind it all. The whole thing had been running for years. Change a line of text and you'd need the frontend engineer, the backend engineer, a deployment cycle that could stretch over weeks.
They replaced it with a static site generated by AI. No CMS. No database. Hosting cost: zero.
Their job title wasn't engineer.
Around the same time: Spotify's top engineers have gone months without writing code themselves. The head of Anthropic's Claude Code project says he hasn't written a single line since November 2025. His job is now to hand tasks to AI agents and check the results. At Google, three-quarters of all code is AI-generated.
Engineers aren't writing code. Non-engineers are. The two things happened at the same time.
The skill isn't disappearing. It's moving.
On the engineering side, the execution wall (reading code, making changes by hand) is being absorbed by AI. The job's center of gravity has shifted toward architecture, catching where the AI goes wrong, deciding what's actually worth building. On the other side, a door opened. People who understood the business problems but couldn't reach the technical layer now can.
What that person brought to the website rebuild was knowledge of their own company: which features went unused for months, which infrastructure existed because it always had. AI couldn't supply that judgment. But AI gave it somewhere to land.
What stops you has changed.
It used to be whether you could write code. It's starting to look more like: how well do you understand the problem in front of you? AI handles the execution. You handle the question.
That rebuilt site updates a few times a year. Static files, AI-assisted changes, zero hosting cost. The business judgment behind it, what this site actually needs to do: that part, the AI didn't provide.