The Era of Compound Engineering — Kieran Klaassen, Every/Cora
Summary
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
-
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).
-
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.
-
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.
-
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.
Technical details
-
Cora (Product)
252s
A complete AI email inbox and agent-native product built by the speaker, demonstrating the methodology in action. It runs on desktop, phone, CLI, etc.
-
CE ID (Command)
1045s
A plugin command used to analyze open tickets across multiple sources (GitHub, Slack, Intercom) and generate structured arguments on what is best to work on versus what should be deprioritized.
-
C do review (Command)
1160s
A utility that provides sharp questions when reviewing documents like PRDs, forcing the user to consider blind spots and generating knowledge for compounding.
-
LFG (Automation Loop)
1200s
The automated loop function that handles planning, working, reviewing, testing, opening a PR, and even performing before/after video screenshots in the pull request.
Mentioned resources
- Cora
- Every
Channel & topics
Watch on YouTube · Back to latest
This independent, AI-assisted summary is provided for commentary and informational purposes. It may contain errors or omit important context. Please watch the original video for the creator's complete presentation. Video, thumbnail, and related copyrights belong to their respective owners.