Videos ZD9-4fW2HhM
Build Systems, Not Code - Angie Jones, Agentic AI Foundation
Scene timeline
53 shot(s).
keyframes kept every frame deduplicated
What was stored
- cues
- 224
- whisperx 224
- chunks
- 35
- from 224 cues
- keyframes
- 41
- kept of 53 captured
- frames with text
- 41
- 451 lines read
- chapters
- 0
- from the source metadata
- keyframe bytes
- 4.0 MB
- word timings on 224 cues
Provenance
| stage | state | model | started | took |
|---|---|---|---|---|
fetch |
done | — | 2026-08-11 10:13 | 1m 21s |
stt |
done | — | 2026-08-11 10:14 | 21s |
chunk |
done | — | 2026-08-11 10:14 | 0s |
text_embed |
done | — | 2026-08-11 10:14 | 0s |
keyframe |
done | — | 2026-08-11 10:14 | 1m 52s |
ocr |
done | — | 2026-08-11 10:16 | 13s |
frame_embed |
done | — | 2026-08-11 10:16 | 8s |
Frames, and what the machine read
-
- Build Systems,0.99
- not Code0.98
- Angie Jones · VP of DX, Agentic AI Foundation0.97
- angiejones.tech1.00
-
- we gave the agents the code.. and the thrill went with it.0.97
- Angie Jones · VP of DX, Agentic AI Foundation0.98
- angiejones.tech1.00
-
- Go up a layer0.98
- architecting systems1.00
- writing code1.00
- Angie Jones · VP of DX, Agentic AI Foundation0.97
- angiejones.tech1.00
-
- Different building blocks.0.98
- Same discipline.1.00
- Angie Jones · VP of DX, Agentic AI Foundation0.97
- angiejones.tech0.99
-
- Relocation Scout1.00
- a house hunting agent0.98
- listings1.00
- prompt1.00
- rank1.00
- no memory0.99
- Angie Jones · VP of DX, Agentic AI Foundation0.97
- angiejones.tech1.00
-
- Principle 10.99
- Systems Thinking1.00
- What larger system is this part of, and what role1.00
- should it play?1.00
- Angie Jones · VP of DX, Agentic AI Foundation0.97
- angiejones.tech1.00
-
- listing feeds1.00
- ranked shortlist1.00
- neighborhood data1.00
- agent1.00
- Relocation Scout1.00
- hand off to you1.00
- your criteria1.00
- what happens if it fails?1.00
-
- listing feeds1.00
- Principle 10.98
- ranked shortlist1.00
- Systems Thinking1.00
- neighborhood data1.00
- agent1.00
- Relocation Scout1.00
- What larger system is this part of, and what role0.99
- hand off to you1.00
- should it play?1.00
- your criteria1.00
- what happens if it fails?0.98
- Angie Jones · VP of DX, Agentic AI Foundation0.97
- angiejones.tech1.00
-
- new listing1.00
- trigger0.99
- gather context1.00
- evaluate1.00
- decide1.00
- act1.00
- record1.00
- Principle 21.00
- Workflow Design1.00
- How does work move from1.00
- stop1.00
- retry1.00
- escalate1.00
- trigger to completion?1.00
- Angie Jones · VP of DX, Agentic AI Foundation0.97
- angiejones.tech1.00
-
- Principle 31.00
- Decomposition1.00
- Have I broken the system into0.99
- clear responsibilities?1.00
- Angie Jones · VP of DX, Agentic AI Foundation0.98
- angiejones.tech1.00
-
- the giant prompt1.00
- · normalize listing0.94
- ·format shortlist0.97
- Principle 30.99
- calculate commute1.00
- research neighborhood0.98
- Decomposition1.00
- Have I broken the system into0.99
- clear responsibilities?1.00
- Angie Jones · VP of DX, Agentic AI Foundation0.97
- angiejones.tech1.00
-
- the giant prompt1.00
- normalize listing1.00
- · format shortlist0.94
- · calculate commute0.94
- research neighborhood0.97
- normalize listing1.00
- format shortlist0.98
- calculate commute1.00
- research neighborhood0.97
-
- the giant prompt1.00
- · normalize listing0.93
- format shortlist1.00
- Principle 31.00
- calculate commute1.00
- research neighborhood0.99
- Decomposition1.00
- Have I broken the system into0.99
- clear responsibilities?1.00
- normalize listing1.00
- format shortlist1.00
- calculate commute0.98
- research neighborhood1.00
- Angie Jones · VP of DX, Agentic AI Foundation0.97
- angiejones.tech1.00
-
- normalize listing1.00
- format shortlist1.00
- calculate commute1.00
- research neighborhood1.00
- skill1.00
- schema1.00
- script1.00
- subagent1.00
-
- normalize listing1.00
- format shortlist1.00
- calculate commute1.00
- research neighborhood1.00
- Principle 41.00
- Separation of1.00
- Concerns1.00
- Does each layer own the right0.99
- responsibility?1.00
- skill1.00
- schema1.00
- script1.00
- subagent1.00
- Angie Jones · VP of DX, Agentic AI Foundation0.97
- angiejones.tech1.00
-
- skill1.00
- normalize-listing1.00
- Austin1.00
- Denver1.00
- Raleigh1.00
-
- skill1.00
- sub-agent1.00
- normalize-listing1.00
- neighborhood research1.00
- Austin1.00
- Denver1.00
- Raleigh1.00
Transcript
224 cues· 2,954 words· 16,016 chars
- 0:00 Lately, I've been building agents a lot for operational tasks.
- 0:04 And while I was working one Friday night, I saw the sunset.
- 0:10 And then dinner time came and went.
- 0:13 And it hit me.
- 0:14 I was in that familiar death flow.
- 0:17 And the thrill of building was back.
- 0:21 Many of us who are coding with agents, we feel like this quiet sense of dread.
- 0:26 Like they're kind of taking all of the fun parts of building and leaving us with the unglamorous work.
- 0:31 But let me give you a little advice.
- 0:34 Let them have it.
- 0:35 Because if you go up just one layer, you'll find that the thrill is still there.
- 0:42 When you're building agents, not just using them to write code, you start getting into architecting agentic systems.
- 0:50 And you realize that the building blocks are different, but the discipline is the same.
- 0:56 So I find myself now flexing the same engineering muscles that I did pre-gen AI.
- 1:03 And I'm having a blast with it.
- 1:06 So I'm going to walk through the flow of designing an agent.
- 1:08 I'm going to show you where engineering skills still come into play.
- 1:15 So the agent is Relocation Scout, which is a house hunting agent.
- 1:21 And if you did this as just a one-time prompt that points the agent to some listings and asked it to rank them, I mean, that'll work, but you're likely not going to find a house in a day, right?
- 1:33 So you want to build this as an agentic system that you can reuse, one that can persist knowledge outside of the session.
- 1:42 It could reload or query that knowledge later to make decisions, even within a fresh context.
- 1:48 So when thinking about how to design an agent, the first engineering skill that I exercise is systems thinking.
- 1:56 So an agent is not the system, right?
- 1:59 It's part of the system.
- 2:01 And that system has files and tools, humans, even other agents.
- 2:07 So Relocation Scout sits inside of something bigger and it pulls in listings and signals about the neighborhoods, it weighs them against what I care about, and then it hands me back a ranked short list.
- 2:22 So I often hear people say, just let your coding agent build it, right?
- 2:27 And I think that's a mistake.
- 2:29 Like, yes, my coding agent can build it, but before allowing it to do so, I need to think about the whole environment, the entire system, right?
- 2:40 I want to think about what's this agent's job?
- 2:43 What does it depend on?
- 2:45 What happens if it breaks?
- 2:47 And I want to treat it like any other component where it has boundaries and responsibilities, has dependencies, and ways that it can fail.
- 2:57 And that whole thought process, that's engineering.
- 3:02 The second skill is workflow design.
- 3:05 So traditional software is full of workflows.
- 3:08 We got CICD pipelines, right?
- 3:11 We got like ticket life cycles, you name it.
- 3:15 Agentsic systems, they need that same kind of design.
- 3:19 As much as we all love the slash goal command, an agent needs more than a goal.
- 3:24 It needs a path.
- 3:26 When we say review this listing, that's a goal.
- 3:29 But the workflow is what defines what actually has to happen, right?
- 3:33 For example, the agent has to gather what it needs.
- 3:37 It needs to weigh the listing against my criteria and then act.
- 3:41 And every run ends one of three ways.
- 3:44 Either it's going to stop, it's going to retry, or it's going to escalate.
- 3:48 So that path is what shapes the rest of the architecture.
- 3:53 Once I see how work moves through the system, I can make better calls about what context the agent needs, what parts I want the agent to handle directly, and when a tool or a person should take over.
- 4:07 We all know the danger of one giant thing that does everything, right?
loading