Topic

AI Development Workflow

All digests tagged AI Development Workflow

The Era of Compound Engineering — Kieran Klaassen, Every/Cora thumbnail

· 20:38

The Era of Compound Engineering — Kieran Klaassen, Every/Cora

The talk introduces 'Compound Engineering,' a methodology for building complex software products using AI by shifting focus from writing code to optimizing the system's memory and knowledge base. The core principle is that development efficiency increases when time is spent teaching the AI what it got wrong (system refinement) rather than just generating new features. This process inverts complexity accumulation, aiming for each subsequent feature to be easier to build than the last.

Key takeaways

  1. The Compound Engineering Loop 10:25

    The development loop involves Brainstorming $\rightarrow$ Planning $\rightarrow$ Working $\rightarrow$ Reviewing $\rightarrow$ Polishing $\rightarrow$ Compounding. The human must be 'brain-on' at both the start (defining the problem) and the end (raising the bar/taste).

  2. The 50/50 Rule of Improvement 13:30

    Allocate 50% of time to building the feature and 50% to teaching the system what it did wrong or how it can learn. This knowledge extraction is crucial for long-term efficiency.

  3. Token Efficiency through Memory 15:03

    Storing solutions and learnings within a repository (compounding) makes future interactions more token-efficient because the AI does not need to perform deep research or correction passes; the solution is already embedded.

  4. Inverting Complexity 20:38

    The goal of Compound Engineering is that each shipped feature makes the next one easier, counteracting the typical accumulation of complexity in software development.

Watch on YouTube Full article

/goal: Building big features with dcode thumbnail

· 8:02

/goal: Building big features with dcode

The video introduces `dcode`, an open-source, model-agnostic coding agent, and its new `/goal` command. This feature enables long-running, persistent tasks by wrapping the standard agent loop in a 'goal loop.' Instead of relying on single-shot requests for large features (like meaty PRs), `/goal` establishes visible acceptance criteria that guide the agent's work over hours. The demonstration shows how to use this mechanism to add native browser control to `dcode`, allowing the user to steer, amend requirements, and inspect progress using tools like LangSmith tracing.

Key takeaways

  1. The /goal Command 2:50

    The `/goal` command provides a long-running, persistent objective for agents tackling large tasks. It shifts alignment work upfront, making it visible and allowing mid-run tailoring of requirements (3:46).

  2. Goal Loop Mechanism 0:35

    The goal loop wraps the agent's inner action loop. The outer loop continuously checks if actions satisfy the durable acceptance criteria; if not, the goal remains active until evidence satisfies all requirements (0:17).

  3. Steering and Amending Goals 4:40

    Users can inspect the current state with `/goal show` or update/correct requirements mid-run using `/goal amend`, which interprets the message within the context of the active goal (3:46).

Watch on YouTube Full article