Pinned Tweet
1/ Been trying out more AI coding Agents - here's a quick breakdown of my experience with the AI coding agent space and what I use each agent for
btw this is why you need an internal eval benchmark flywheel - not just a one and done set of tasks
evals will become a core skillet (still early) for every company that wants to use AI and the more “up to date” they are, the higher impact new models will have on that business.
OpenAI, Anthropic and other leading AI labs face a growing challenge: Better models aren't necessarily attracting more usage. A 10-point intelligence advantage now earns just 20% more developer traffic, down from nearly 69% in late 2025.
Full story: thein.fo/4hGJ9jY
Aman Khan retweeted
We are hosting our first "Bench Summit" to bring together people excited about pushing the frontier of benchmarking, model evals, and more.
Great benchmarks are a gating function for model progress, lots to do here!
Join us in SF: rsvp.withgoogle.com/events/b…
token based pricing is honestly very strange
- maps roughly to compute time pricing, except because LLMs are non deterministic this is basically unpredictable
- no direct hop to value or capacity
- incentives don’t exist to lower token spend w/o competition (see: billable hours)
extreme outcome distributions are seemingly becoming the norm even more
- in using AI products (and how to get value from them)
- in fraud, abuse and unexpected outcomes (below)
- in perception of AI systems (they will cure everything vs kill us all)
This quoted post is unavailable.
the most stressful part of the job
now handled by agents
curious what friends at @datadoghq @cleric_io @sentry @pagerduty @arizeai @resolveai think!
Aman Khan retweeted
very clear that harnesses across the industry will become specialized boxes optimized for a given task -> some bundling tooling like Jev!
Model-Harness-Task fit
some of it “just-in-time”, most prob not
the best vertical agents today have already been doing this for a while -> unbundle all prompts/tools/skills/models and rebundle them for your Task domain
everyone will calibrate via evals, secret sauce is still in the data layer











