Have your agents aggressively and frequently prune your codebase for stale code/comments/"compatibility paths" and double-check that what they codify as ground truth is what you actually want. Gotta keep the slop levels low enough to make progress.
The biggest turn-off in agentic coding: self-poisoning.
Agent takes a wrong turn. No problem, you steer back.
But the wrong turn leaves residue: a stale comment, a dead code fragment, something that still encodes the abandoned decision.
The agent reads that residue as signal and pulls back toward the mistake you already corrected.
One wrong turn keeps reinfecting the work long after you steered away.
@clare_liguori Dont bother with letting an agent do things manually, define exactly what you want text-wise and give it to gpt-image-2 to generate in one go
Current state of the software market.
Our firm recently acquired a very small software startup as an acquihire.
It was decided they wouldn't bring the software from their company. They'll restart everything from scratch again.
Hard to make people understand exactly how much of a difference the harness in conjunction with test time scaling can make, if you build them well... task-specific harnesses are always going to outperform general ones.
Spent time today reading through one of Anthropic’s massive Claude prompts after sniffing the network traffic. A 1,500 line prompt!
What surprised me wasn’t the personality tuning. It was the amount of embedded operational logic. Large parts were more akin to a programming language. API doc outlines, code samples, tool routing rules, formatting protocols, javascript snippets with dos/donts.
I used to think prompting is about wording, but these models are now invisible runtime systems behind a chat UI.
When I was consulting for @HBO Silicon Valley, zero-loss compression was the holy grail Richard Hendricks chases that perfect middle-out algo could shrink everything w/out breaking a single bit.
Google just did something even more practical for the AI era: TurboQuant compresses LLM key-value caches down to 3 bits per value using random orthogonal rotation + PolarQuant scalar quantization & optional 1-bit QJL residual correction.
=>> 6× memory reduction, up to 8× faster attention (on H100), & 0 degradation on LongBench, Needle-in-a-Haystack, and RULER for models like Gemma. No retraining, no calibration needed.
Fiction just got out-engineered by reality. 😅💚💚