I hosted a session with Vitor from Zapier to discuss how they dramatically improved their feedback collection systems for AI products. This conversation reveals practical strategies for gathering, analyzing, and implementing user feedback to create a continuous improvement cycle for RAG systems and AI applications.
This is part of the Context Engineering Series. I'm focusing on agent frameworks because understanding form factors and complexity levels is essential before building any agentic system.
Field note from a conversation with my friend Nila, who helps companies navigate AI implementation decisions: nila.is. Nila focuses on implementations and workflows; I focus on writing down strategy and execution patterns on this blog.
When companies say they want to build agents, I focus on practical outcomes. What specific functionality do you need? What business value are you trying to create?
This is part of the Context Engineering Series. I'm focusing on rapid prototyping because testing agent viability quickly is essential for good context engineering decisions.
If your boss is asking you to "explore agents," start here. This methodology will give you evidence in days, not quarters.
Most teams waste months building agent frameworks before they know if their idea actually works. There's a faster way: use Claude Code as your testing harness to validate agent concepts without writing orchestration code.
Two core insights:
This is part of the Context Engineering series. I'm focusing on compaction because it's where theory meets practice—and where we desperately need empirical research.
The main idea: When AI tools do messy tasks, they can either stay focused or get confused by too much information.
This is part of the Context Engineering Series that shows how to build better AI tools based on what I've learned from coding assistants and business systems.
I've been helping companies build agentic RAG systems and studying coding agents from Cognition, Claude Code, Cursor, and others. These coding agents are likely creating a trillion-dollar industry—making them the most economically viable agents to date.
This series shares what I've learned from these teams and conversations with professional developers using these systems daily, exploring what we can apply to other industries.
If you want hands-on help, I recommend reaching out to my friend Nila: nila.is. Please mention you came from me.
Related Series
Coding Agents Speaker Series: Deep insights from the teams behind leading coding agents including Cognition (Devin), Sourcegraph (Amp), Cline, and Augment. While this Context Engineering series focuses on technical implementation patterns, the Speaker Series reveals strategic insights and architectural decisions.
RAG Master Series: Comprehensive guide to building and scaling retrieval-augmented generation systems. Context Engineering principles directly enhance RAG implementations—structured tool responses and faceted search are foundational RAG optimization techniques.
The core insight: In agentic systems, how we structure tool responses is as important as the information they contain.
This is the first post in a series on context engineering. I'm starting here because it's the lowest hanging fruit—something every company can audit and experiment with immediately.
These are example questions we tackled in office hours across previous cohorts. Office hours are not currently running.
This comprehensive FAQ is compiled from all office hours sessions across multiple cohorts.
Quick Navigation
Use your browser's search (Ctrl+F) to find specific terms or questions, or browse through the questions below.
I find this to be a pretty interesting topic because I personally believe that coding agents are probably executing at the frontier of agentic ray systems.
The world of autonomous coding agents is rapidly evolving, with fundamental disagreements emerging about the best approaches to building reliable, high-performance systems. This Lightning Series brings together the minds behind some of the most successful coding agents—from SWE-Bench champions to billion-dollar products—to debate the core architectural decisions shaping the future of AI-powered development.
If you just want to sign up, you're going to have to visit every single tab, open these links, and sign up to each one.
RAG in the Age of Agents: SWE-Bench as a Case Study from Colin Flaherty of Augment Code
Lessons on Retrieval for Autonomous Coding Agents from Nik Pash of Cline
Why Devin Does Not Use Multi-Agents from Walden Yan of Cognition AI