Understand this story
In an interview, Claude engineering lead Felix Rieseberg proposed giving crash data, business tools, and computers to the model, letting the model decide for itself what to fix, rather than having a human act as a relay and pass along each item one by one. He suggested opening multiple threads aimed at the same output to specifically prove it wrong, then opening another thread to act as a judge and filter out the criticisms that hold up; rather than slicing off a small piece of data for each agent, it is better to give a panoramic view of the business and tools with clear documentation. He also mentioned that the half-life of Skills is extremely short, that both the official team and individuals recommend using them with caution, and that self-evaluation within the same session is still unreliable, so external signals should be sought as much as possible.
AI-generated from public reports
Developments
1 confirmed developments
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Oct 24
Shao Meng
Claude engineering lead Felix on how to use Claude: fewer role-based Agents, use adversarial review to constrain output
In an interview, Claude engineering lead Felix Rieseberg said he barely writes code anymore; his core approach is to hand crash data, business tools, and a computer to the model and let it decide what to fix itself, rather than having a human act as a relay repeating things item by item. He suggests opening multiple threads on the same output dedicated to proving it wrong, then opening another as a judge to filter which criticisms hold up; rather than giving each Agent a tiny slice of data, it is better to give a panoramic business view and well-documented tools. He also mentioned that the half-life of Skills is extremely short, that both official guidance and his own advice are to use them cautiously, and that self-evaluation within the same session remains unreliable, so external signals should be sought as much as possible.