@jerryjliu0: From playing around with /goal It feels like there's less and less of a need to build any type of workflow manually (wh…
Summary
Jerry Liu observes that AI development is shifting from manually building workflows to specifying goals, and from prompt engineering to goal and eval engineering.
View Cached Full Text
Cached at: 06/29/26, 06:30 AM
From playing around with /goal
It feels like there’s less and less of a need to build any type of workflow manually (whether through code, drag and drop, or a prompt). Instead, specify the goal, let the model intelligence figure out the underlying steps.
If the task is repeatable, then you can gather a dataset with ground-truth, and hillclimb it for increased cost / lower accuracy. To some extent this is what every non-frontier lab is optimizing for.
The world is moving from prompt engineering -> goal and eval engineering.
Similar Articles
@jerryjliu0: 3 years ago I gave a talk at the first @aiDotEngineer conference on "Advanced RAG" techniques in order to work around t…
Jerry Liu reflects on the evolution of RAG techniques over three years, noting a shift from naive RAG to agent-based abstractions and from code-defined to goal-defined agents.
@jerryjliu0: This is a nice article (not sure how I stumbled upon it a month later) I directionally agree with it in that: I have a …
Jerry Liu shares his hiring philosophy favoring candidates with slope, grit, and scrappiness over experience, arguing that AI reduces the time for routine tasks and accelerates learning, while warning against using AI to produce slop without true understanding.
@Av1dlive: Garry Tan (CEO of Y-Combinator): "when someone asks how I 'prompt' my AI, the answer is: I don't. the skills are the pr…
Garry Tan advocates shifting from manual AI prompting to skill-based automation, presenting open-source tools like GBrain and GStack to capture and reuse workflows permanently.
@ThisisHan1_: Recently built a development pipeline and wanted to share the thinking behind it. I was inspired by loop/goal engineering and auto-goal (letting the agent write its own goals and spawn subtasks). But what really clicked for me was...
This development pipeline first creates a rough prototype to elicit user feedback, turning every 'that's not right' reaction into a checkable rule. Then AI agents independently develop and validate against those rules, catching issues early and avoiding self-deception.
Everyone builds AI workflows. Almost no one sticks with them. Here’s why.
A founder shares his experience with AI tool adoption, noting that most people collect tools without achieving real results. He advocates focusing on one critical business problem and iterating until the workflow genuinely works, citing his own success reducing client reporting time from 4-5 hours to under 45 minutes.