I talk to engineers at other companies every day and hear the same thing: one person is 10x'ing their output with Claude but the rest of the org hasn't caught up.
Watching teams adopt AI, I keep seeing the same 4 steps.
I mapped them out here: Steps of AI Adoption https://t.co/kQnRAUMKpP
We're building AI that people and organizations can shape and make their own. AI should extend our will and judgment instead of neglecting it; enabling that is the technical challenge we are working to solve.
https://t.co/Bi558y4vqD
Today, we’re introducing [schema]: a harness reaching 99% RHAE with Opus 4.8 + Fable 5 and 95.35% with GPT-5.6 Sol on ARC-AGI-3 Public set.
[schema] makes an LLM think like a physicist. 🧵
I am excited to announce that we are officially writing a new version of Postgres. In Rust - and creating the LLVM of databases in the process.
In the span of a year, we have rewritten SQLite. Keeping the compatibility, increasing its feature set. MVCC, Types, (Live) Materialized Views, among other things. In the process of doing that, we have realized: At the end of the day, what makes SQLite special is that it compiles SQL to a database-specific bytecode. So why can't we compile *Postgres* to the same bytecode?
Turns out we can. I ran an experiment called pgmicro as a way to prove this hypothesis, and it works very well. It is time to make this official, and put the weight of Turso behind it. We shall give the world a modern take on Postgres. Wire compatible, but built on a new architecture.
We have already heard of others wanting to extend this. MySQL? Redis? the sky is the limit. What can we do if we do for databases what LLVM did for compilers? To prove how powerful the SQLite bytecode is, we are actually running DOOM compiled to the unmodified SQLite instruction set. And because Turso runs natively in the browser, you can play the game in your browser. With the database executing it.
Read the full story below! 👇
I built a variant of @mattpocockuk's grilling skill dedicated to frontend and it has improved how I build new apps and components.
The general idea:
1. Use /grilling and /prototype as a base
2. Tell Claude to build 5 WILDLY different prototypes
3. Tell Claude to include a picker that lets you switch between each variant live
4. Each round you select your favorite(s) + leave feedback, and Claude will walk down each branch of the design tree, helping you zoom in on your desired design
And THEN, I went and added it to /wayfinder, so whenever I make a new map and there's novel frontend work, a ticket is created specifically referencing that /grilling-frontend-prototyping needs to be invoked.
This will not be the last time I build a cool skill and add it to Wayfinder; this is a very powerful pattern for planning work.
You can find my skill here: https://t.co/4M4QPlfnp1
Kimi K3 is out, and it's beautiful. Go try it now.
Also, a (very) late life update: I joined @Kimi_Moonshot a few months ago to build open frontier intelligence. Honored to ship K3 alongside an incredible team.
Only the beginning. Scaling never stops.
(Btw, please don't sleep on the chip design demo
Big news: Kimi-K3 by @Kimi_Moonshot is now #1 in the Frontend Code Arena with 1679 pts, surpassing Claude Fable 5.
This is a 17-place jump from Kimi-k2.6 (#18 -> #1).
In Frontend, Kimi-K3 ranked #1 in 6 of 7 domains: Brand & Marketing, Reference-Based Design, Data & Analytics, Consumer Product, Simulations, and Content Creation Tools, landing #2 only in Gaming behind Fable 5.
The full model weights will be released by July 27.
Congrats to the @Kimi_Moonshot team on this major milestone!
after a few more days of using gpt 5.6 sol, i started noticing some issues - if you have good solutions, please share!
1. it uses technical jargons a lot. it's almost speaking its own language that looks like English but you can't understand it until you ask "what do you really mean by this"
2. it can over-engineer and spiral out of control. something that can be done with a few lines of changes can often result in a massive diff fixing everything in the codebase
3. it's overly conservative in terms of touching live environment, so much so that it overly relied mocks for development and validation and build things that don't really work in production
these things can likely get tweaked in system prompts, but so far gpt 5.6 is the only model family that don't get these things right out of the box, and it's a bit annoying
i love overall how intelligent and fast the model is though! just curious if anyone's run into similar challenges with the model and has good solutions
"if i can interface with everything through my agent, why would i go to the dashboard?"
i sat down with @sarahfim, mts at @composio, at the @browserbase@aiDotEngineer booth. fresh off her AIE talk "dashboards are dead," we got into:
- why agent experience is the next wave and how to design for agents
- personal agents as the main consumer of the internet
- building and open-sourcing TrustClaw, a production-ready personal agents
listen to our full conversation here:
🆕This Year In Claude
https://t.co/y3nAq7wjL1
@simonw chats with @_catwu and @trq212 about the state of:
- @claudeai Code
- Claude Fable
- @anthropicai culture & product strategy
- Claude Tag & multiplayer collaboration
- The surprising succcess of Remote control
- HTML artifacts for code review
- Why Anthropic uses Auto Mode as the standard for long-running tasks at Anthropic, not --dangerously-skip-permissions
- using Claude for Video editing
- how to be more ambitious as a developer: refusing to "negotiate against oneself"
Timestamps
0:00 Introductions and Claude Code overview
1:22 How coding agents have changed daily workflows
3:51 Shifting focus: Product sense over manual implementation
5:09 Why modern rewrites are now beneficial
6:37 Introducing Claude Tag and team collaboration
11:38 Prioritization and internal "dog-fooding" culture
13:06 The surprise success of remote control features
14:17 Evolving code review processes and automation
17:16 Building trust in new model generations
19:18 Optimizing for capability and user experience
21:23 Reducing system prompts for frontier models
28:05 The philosophy of tool design
30:57 Safety, security, and using Auto Mode
37:53 The human element and developer ambition
41:50 Surprising use cases for Claude (e.g., video editing)
43:35 Limitations and future design aspirations
45:09 Cultural hacks for productivity
46:42 Absurd, fun projects built with Claude
49:03 Audience Q&A