Claude Code team: "we oversimplify agentic engineering - like it's just prompts, just loops No. We need to know what we're doing " "I think Fable smarter than we think and we're hobbling Claude" what he means: step 1 → stop rewriting the prompt, give it a tool, the... model that "can't" - answer will grep it in one line step 2 → tell it who YOU are. -"experienced TS engineer, zero context on this module, high-compute - use sub-agents" step 3 → don't skim the report - that's "education movie" - looks great, teaches nothing - make Claude visualize it until it clicks step 4 → anchor the unknown to what you know. color grading landed when Claude called it a shader - pixel in, pixel out step 5 → prototype in cheap HTML first - finding out at 80% done is what he's on the Claude Code team and just drop a new workshop watch & bookmark, find out what he uses instead↓show more

别老搓 prompt，先把手脚接上

Tools beat prompts every time. Stop hobbling the model.

exactly, that’s what this video explains

"we're hobbling Claude" is the right frame bro – the model has it, the harness just won't let it out

the loop framing is what's holding back most agent products honestly. it's not a loop, it's a state machine with really bad error handling

underrated interview honestly, alpha info as always codila

True, oversimplification can hinder progress. In my fleet, leveraging tools strategically allows agents to handle complex tasks without constant prompt rewrites. How do you integrate tool-use with models effectively?

El "dale una tool en vez de reescribir el prompt" es medio camino. La otra mitad es la capa de conocimiento: qué sabe el agente antes de arrancar. En un vertical B2B el 60-70% del laburo no fue el loop, fue codificar el dominio en algo que el modelo pueda usar.

The skill is slowly moving from “writing the perfect prompt” to “designing the perfect environment for the model to work in.”

building agent loops requires way more nuance than prompting

In client deployments, the difference is almost never the model. It's the quality of the context, access to the right tools, and a well-defined workflow. What change has had the biggest impact for your team?

honestly haven't seen this video before how could i have slept on it?...