Loading video...

Video Failed to Load

Go Home

Most people lump prompt engineering, context engineering, and graph engineering together. Here's the simple breakdown: - Prompt engineering: how you ask the AI a better question. - Context engineering: how you give the AI better information. - Graph engineering: how you design the work around the AI so it...

startupideaspod's profile picture

The Startup Ideas Podcast (SIP) 🧃

45,135 subscribers

17,562 views • 8 days ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

context engineering vs graph engineering. every few months the list gets a new word and everyone treats it as a replacement for the last one. these two are not on the same list. one decides what the model sees this turn, the other decides what exists at all. the cleanest way to tell them apart is to ask what a single unit of work looks like. > context engineering is the window the window opens empty, every single time. you assemble what goes in it. the prompt, the docs, the history, the tool results. the assembling is the work. the window only grows. it never shrinks on its own, so eventually something gets dropped. usually from the middle. usually without telling you. then the turn ends and the window is thrown away. not archived, thrown away. the next turn opens empty again and you re-explain what you already explained. good context engineering is knowing what to leave out, not what to pack in. the unit of work is one window. > graph engineering is the structure the same material arrives from the same sources. instead of packing it into a window, you pull entities out of it, resolve the duplicates into one node, and write typed edges between them. nothing here is stored as text you hope to find again. it is stored as a thing with a name and its connections to other things. when the turn ends, the graph is still there. the next turn does not start from zero. it starts by querying what already exists, and the query walks edges instead of guessing at similarity. good graph engineering is deciding what counts as the same thing twice. the unit of work is one relationship. > they are not alternatives the graph is what refills the window. context engineering decides what fits. graph engineering decides what there is to choose from. remove the graph and every session starts blind. remove the context work and the best structure in the world arrives as an unreadable dump. that also tells you which one broke. the answer drifted from what you actually said, or forgot something from this same session. that is the window. the answer is coherent but invents a connection that does not exist, or cannot join two facts it has clearly seen. that is the structure. people debug the prompt because the prompt is the easiest thing to edit. it keeps taking the blame for failures that live a layer down. save this - then read the full breakdown below
0:40

context engineering vs graph engineering. every few months the list gets a new word and everyone treats it as a replacement for the last one. these two are not on the same list. one decides what the model sees this turn, the other decides what exists at all. the cleanest way to tell them apart is to ask what a single unit of work looks like. > context engineering is the window the window opens empty, every single time. you assemble what goes in it. the prompt, the docs, the history, the tool results. the assembling is the work. the window only grows. it never shrinks on its own, so eventually something gets dropped. usually from the middle. usually without telling you. then the turn ends and the window is thrown away. not archived, thrown away. the next turn opens empty again and you re-explain what you already explained. good context engineering is knowing what to leave out, not what to pack in. the unit of work is one window. > graph engineering is the structure the same material arrives from the same sources. instead of packing it into a window, you pull entities out of it, resolve the duplicates into one node, and write typed edges between them. nothing here is stored as text you hope to find again. it is stored as a thing with a name and its connections to other things. when the turn ends, the graph is still there. the next turn does not start from zero. it starts by querying what already exists, and the query walks edges instead of guessing at similarity. good graph engineering is deciding what counts as the same thing twice. the unit of work is one relationship. > they are not alternatives the graph is what refills the window. context engineering decides what fits. graph engineering decides what there is to choose from. remove the graph and every session starts blind. remove the context work and the best structure in the world arrives as an unreadable dump. that also tells you which one broke. the answer drifted from what you actually said, or forgot something from this same session. that is the window. the answer is coherent but invents a connection that does not exist, or cannot join two facts it has clearly seen. that is the structure. people debug the prompt because the prompt is the easiest thing to edit. it keeps taking the blame for failures that live a layer down. save this - then read the full breakdown below

Hanako

19,089 views • 13 days ago

CONTEXT ENGINEERING > PROMPT ENGINEERING Everyone is obsessed with writing better prompts. The next generation of AI builders is focused on context engineering instead. • Prompt engineering shapes the question. Context engineering shapes everything the AI sees. • Great prompts can't save an agent missing critical context, memory, or tools. • AI failures often come from missing information, not weak models. • Context engineering combines prompts, memory, RAG, state management, and tool access into one system. What powers effective AI agents? → Memory: Remembers preferences, past interactions, and ongoing tasks. → State Management: Tracks progress across multi-step workflows. → RAG: Retrieves only the most relevant information when needed. → Tools: Connects AI to APIs, databases, code execution, and real-world actions. → Dynamic Prompts: Enriches instructions with live context at runtime. The key insight: Prompt Engineering = Better Questions Context Engineering = Better Systems The future of AI isn't building smarter prompts. It's building smarter environments for AI to think, remember, retrieve, and act.
7:51

CONTEXT ENGINEERING > PROMPT ENGINEERING Everyone is obsessed with writing better prompts. The next generation of AI builders is focused on context engineering instead. • Prompt engineering shapes the question. Context engineering shapes everything the AI sees. • Great prompts can't save an agent missing critical context, memory, or tools. • AI failures often come from missing information, not weak models. • Context engineering combines prompts, memory, RAG, state management, and tool access into one system. What powers effective AI agents? → Memory: Remembers preferences, past interactions, and ongoing tasks. → State Management: Tracks progress across multi-step workflows. → RAG: Retrieves only the most relevant information when needed. → Tools: Connects AI to APIs, databases, code execution, and real-world actions. → Dynamic Prompts: Enriches instructions with live context at runtime. The key insight: Prompt Engineering = Better Questions Context Engineering = Better Systems The future of AI isn't building smarter prompts. It's building smarter environments for AI to think, remember, retrieve, and act.

Dami-Defi

10,127 views • 1 month ago

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to an agent graph that builds itself: 10:16 - Build your first AI agent 41:05 - Master prompt engineering 54:45 - Turn agents into graphs 1:20:10 - Run loops inside agent graphs 1:43:33 - Build a graph that builds itself Most people ship one agent and stop there. Google is teaching everything after: Prompt → Agents → Graphs → Loops → Self-Building Systems Single agents are the old workflow. Graphs that evolve themselves are the new one. This 2-hour watch is worth more than most paid agent engineering courses. Bookmark and watch it today Then read how to run 1,000 agents from one prompt below ↓
1:54:59

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to an agent graph that builds itself: 10:16 - Build your first AI agent 41:05 - Master prompt engineering 54:45 - Turn agents into graphs 1:20:10 - Run loops inside agent graphs 1:43:33 - Build a graph that builds itself Most people ship one agent and stop there. Google is teaching everything after: Prompt → Agents → Graphs → Loops → Self-Building Systems Single agents are the old workflow. Graphs that evolve themselves are the new one. This 2-hour watch is worth more than most paid agent engineering courses. Bookmark and watch it today Then read how to run 1,000 agents from one prompt below ↓

Lunar

49,332 views • 4 days ago

Head of Google AI: "75% of our engineers are running dozens or hundreds of agents. The way you do it is Graph Engineering." in 50-minutes, he shows how one engineer can do a whole team’s work, how far this has gone at Google, and what’s next. this is something you can't skip if you don't want to be left behind. watch it, then read the full guide on graph engineering below.
56:58

Head of Google AI: "75% of our engineers are running dozens or hundreds of agents. The way you do it is Graph Engineering." in 50-minutes, he shows how one engineer can do a whole team’s work, how far this has gone at Google, and what’s next. this is something you can't skip if you don't want to be left behind. watch it, then read the full guide on graph engineering below.

Codez

76,425 views • 11 days ago

Google just released a free 1-hour lecture from Chief Scientist Jeff Dean on full AI Engineering. How to go from one LLM to coordinating 100 AI agents: 01:45 - Build an LLM from scratch 17:22 - Learn how to actually use AI models 30:03 - Master prompt engineering 52:35 - Coordinate 100 agents as one human Most people are still learning how to prompt one model. Jeff Dean is showing the full stack: LLMs → Prompts → Agents → Agent Teams → Graphs Prompting is the old workflow. Coordinating agent systems is the new one. This is 27 years of Google AI compressed into one hour. Bookmark and watch it today Then read the full Graph Engineering guide below ↓
1:06:12

Google just released a free 1-hour lecture from Chief Scientist Jeff Dean on full AI Engineering. How to go from one LLM to coordinating 100 AI agents: 01:45 - Build an LLM from scratch 17:22 - Learn how to actually use AI models 30:03 - Master prompt engineering 52:35 - Coordinate 100 agents as one human Most people are still learning how to prompt one model. Jeff Dean is showing the full stack: LLMs → Prompts → Agents → Agent Teams → Graphs Prompting is the old workflow. Coordinating agent systems is the new one. This is 27 years of Google AI compressed into one hour. Bookmark and watch it today Then read the full Graph Engineering guide below ↓

Lunar

99,204 views • 4 days ago

Head of Claude Code: "85% of our engineers are running dozens or hundreds of agents. The way you do it is graph engineering." In 40 minutes he explains how a single engineer now does the work of a whole team, how far this has gone inside Anthropic and where it goes next. This is something you can't skip if you don't want to be left behind. Watch it, then read the full guide on graph engineering below.
35:35

Head of Claude Code: "85% of our engineers are running dozens or hundreds of agents. The way you do it is graph engineering." In 40 minutes he explains how a single engineer now does the work of a whole team, how far this has gone inside Anthropic and where it goes next. This is something you can't skip if you don't want to be left behind. Watch it, then read the full guide on graph engineering below.

Anatoli Kopadze

1,708,475 views • 12 days ago

Google just released free 2-hour course on full Graph engineering: 1 prompt → 100 agents → loops → graphs from 0% to 100%: 10% → 17:44 - build your first agent 30% → 39:30 - Loop engineering: iterate, check, break 60% → 1:12:38 - Graph engineering 75% → 1:34:26 - agents that throttle themselves 100% → 1:55:05 - full graph for multi-agentic systems everyone builds one agent and calls it done - this is the full system where agents wire themselves into a graph watch the course, build the graph - then read the full architecture below ↓
2:03:00

Google just released free 2-hour course on full Graph engineering: 1 prompt → 100 agents → loops → graphs from 0% to 100%: 10% → 17:44 - build your first agent 30% → 39:30 - Loop engineering: iterate, check, break 60% → 1:12:38 - Graph engineering 75% → 1:34:26 - agents that throttle themselves 100% → 1:55:05 - full graph for multi-agentic systems everyone builds one agent and calls it done - this is the full system where agents wire themselves into a graph watch the course, build the graph - then read the full architecture below ↓

codila

458,865 views • 10 days ago

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside one graph: 17:44 - Build your first AI agent 39:30 - Run agents with loop engineering 1:12:38 - Turn agent loops into graphs 1:34:26 - Build agents that throttle themselves 1:55:05 - Orchestrate the full multi-agent system Most people build one agent and stop there. Google is teaching the full stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the new one. This 2-hour watch is worth more than most paid agent engineering courses. Bookmark and watch it today Then read the full architecture below ↓
2:05:53

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside one graph: 17:44 - Build your first AI agent 39:30 - Run agents with loop engineering 1:12:38 - Turn agent loops into graphs 1:34:26 - Build agents that throttle themselves 1:55:05 - Orchestrate the full multi-agent system Most people build one agent and stop there. Google is teaching the full stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the new one. This 2-hour watch is worth more than most paid agent engineering courses. Bookmark and watch it today Then read the full architecture below ↓

Lunar

390,986 views • 5 days ago

OpenAI engineer: "At OpenAI, 85% of our engineers are running hundreds of agents with Codex. The way you do it is graph engineering." In 30-minutes lecture, he explains how a single engineer can now do the work of an entire team, how far this has already gone inside OpenAI, and where it goes next. This is something you can't skip if you don't want to be left behind. Watch it, then read the full guide on graph engineering below.
24:33

OpenAI engineer: "At OpenAI, 85% of our engineers are running hundreds of agents with Codex. The way you do it is graph engineering." In 30-minutes lecture, he explains how a single engineer can now do the work of an entire team, how far this has already gone inside OpenAI, and where it goes next. This is something you can't skip if you don't want to be left behind. Watch it, then read the full guide on graph engineering below.

Movez

198,004 views • 2 days ago

Anthropic engineer: "You're not supposed to prompt Claude. You're supposed to build a graph that runs itself." In 30 minutes she breaks down how Anthropic builds graphs that remember, learn from their mistakes, and get smarter with every run. The difference between an agent and a graph: one runs once, the other gets better every time. Watch it, then read the full guide on graph engineering below.
31:27

Anthropic engineer: "You're not supposed to prompt Claude. You're supposed to build a graph that runs itself." In 30 minutes she breaks down how Anthropic builds graphs that remember, learn from their mistakes, and get smarter with every run. The difference between an agent and a graph: one runs once, the other gets better every time. Watch it, then read the full guide on graph engineering below.

Mahax

285,553 views • 11 days ago

the loop is not the whole agent it is only one layer of the system LOOP vs GRAPH vs HARNESS ENGINEERING LOOP ENGINEERING controls iteration turns retries budgets stop conditions success checks stalled progress use durable execution when the run must survive crashes → GRAPH ENGINEERING controls structure nodes edges state branches checkpoints routing handoffs build stateful agents as explicit graphs → inspect the topology without putting a model in the loop → HARNESS ENGINEERING controls exposure tools permissions memory sandboxes evals traces humans isolate generated code from the host machine → test behavior before users ever see it → preserve one trace across every model step and tool call → without loop control it keeps running without graph structure the path stays invisible without harness control it can reach anything the loop runs inside the graph the graph runs inside the harness the model is only one component debug the layer that actually owns the failure save this then read the article below
0:20

the loop is not the whole agent it is only one layer of the system LOOP vs GRAPH vs HARNESS ENGINEERING LOOP ENGINEERING controls iteration turns retries budgets stop conditions success checks stalled progress use durable execution when the run must survive crashes → GRAPH ENGINEERING controls structure nodes edges state branches checkpoints routing handoffs build stateful agents as explicit graphs → inspect the topology without putting a model in the loop → HARNESS ENGINEERING controls exposure tools permissions memory sandboxes evals traces humans isolate generated code from the host machine → test behavior before users ever see it → preserve one trace across every model step and tool call → without loop control it keeps running without graph structure the path stays invisible without harness control it can reach anything the loop runs inside the graph the graph runs inside the harness the model is only one component debug the layer that actually owns the failure save this then read the article below

rari

20,934 views • 7 days ago

Cross-context Personal Knowledge Base with Social Graph🧠 Introducing Cross-context Personal Knowledge Base with Social Graph. Your Memory, Across Every Conversation Most AI forgets you the moment a chat ends. Teamily's Personal Knowledge Base remembers — across every group, every agent, and every context. Powered by your social graph, it connects the dots between your work, relationships, and ideas, so your AI always knows who you are, what you care about, and what happened before. No setup. No tagging. Just intelligence that grows with you. 🙌Try the prompt today: “visualize my knowledge base with social graph” #teamily #AI #Agent #KnowledgeBase #Social #SocialGraph
0:24

Cross-context Personal Knowledge Base with Social Graph🧠 Introducing Cross-context Personal Knowledge Base with Social Graph. Your Memory, Across Every Conversation Most AI forgets you the moment a chat ends. Teamily's Personal Knowledge Base remembers — across every group, every agent, and every context. Powered by your social graph, it connects the dots between your work, relationships, and ideas, so your AI always knows who you are, what you care about, and what happened before. No setup. No tagging. Just intelligence that grows with you. 🙌Try the prompt today: “visualize my knowledge base with social graph” #teamily #AI #Agent #KnowledgeBase #Social #SocialGraph

Teamily AI

13,287 views • 3 months ago

Anthropic engineer: "You don't need better prompts. You need graph engineering: memory that stays, so your agent never forgets anything." In 28 minutes he shows what Anthropic does differently, how to build and structure work with agents. This beats any paid agent course I've seen. Watch it, then read the graph engineering guide below 👇
28:26

Anthropic engineer: "You don't need better prompts. You need graph engineering: memory that stays, so your agent never forgets anything." In 28 minutes he shows what Anthropic does differently, how to build and structure work with agents. This beats any paid agent course I've seen. Watch it, then read the graph engineering guide below 👇

darkzodchi

457,925 views • 15 days ago

Google just released a free 2-hour+ course on full agent engineering. How to go from one prompt to a system that runs while you sleep: 38:46 - Build your first AI agent 54:46 - Connect MCP tools 1:12:43 - Run agents with four loop patterns 1:20:57 - Turn agent loops into graphs 2:22:31 - Build the complete autonomous system Most people are still building one agent and stopping there. Google is already teaching the full stack: Agents → Tools → Loops → Graphs → Autonomous Systems Single agents are the old workflow. Systems that run without you are the new one. This course is worth more than most paid agent engineering bootcamps. Bookmark and watch it today Then read the full graph engineering playbook below
2:14:04

Google just released a free 2-hour+ course on full agent engineering. How to go from one prompt to a system that runs while you sleep: 38:46 - Build your first AI agent 54:46 - Connect MCP tools 1:12:43 - Run agents with four loop patterns 1:20:57 - Turn agent loops into graphs 2:22:31 - Build the complete autonomous system Most people are still building one agent and stopping there. Google is already teaching the full stack: Agents → Tools → Loops → Graphs → Autonomous Systems Single agents are the old workflow. Systems that run without you are the new one. This course is worth more than most paid agent engineering bootcamps. Bookmark and watch it today Then read the full graph engineering playbook below

Lunar

195,292 views • 12 days ago

Anthropic engineer: "You don't need better prompts. You need graph engineering that makes agents remember everything." In 25 minutes he shows how engineers at Anthropic wire agents into a graph where each has a job, they run in parallel, verify each other, and share a memory that never resets. This beats any paid course on building agents I've seen. Watch it, then read the full guide on graph engineering below.
28:23

Anthropic engineer: "You don't need better prompts. You need graph engineering that makes agents remember everything." In 25 minutes he shows how engineers at Anthropic wire agents into a graph where each has a job, they run in parallel, verify each other, and share a memory that never resets. This beats any paid course on building agents I've seen. Watch it, then read the full guide on graph engineering below.

Anatoli Kopadze

487,910 views • 13 days ago

Google just released free 2-hour course on full agent engineering: 1 prompt → agent teams → loops → graphs from 0% to 100%: 10% → 38:46 - build your first agent 30% → 54:46 - connect MCP tools 55% → 1:12:43 - Loop engineering: 4 ways to run agents 70% → 1:20:57 - Graph engineering 100% → 2:22:31 - the full system that works while you sleep most people build one agent and stop there - this is the full path to a system that runs without you from scratch watch it today - then read the full graph engineering playbook below ↓
2:10:34

Google just released free 2-hour course on full agent engineering: 1 prompt → agent teams → loops → graphs from 0% to 100%: 10% → 38:46 - build your first agent 30% → 54:46 - connect MCP tools 55% → 1:12:43 - Loop engineering: 4 ways to run agents 70% → 1:20:57 - Graph engineering 100% → 2:22:31 - the full system that works while you sleep most people build one agent and stop there - this is the full path to a system that runs without you from scratch watch it today - then read the full graph engineering playbook below ↓

codila

526,621 views • 13 days ago

Head of Claude Code, Boris Cherny: "You're not supposed to write code anymore. You're supposed to build a graph that writes itself." In 30 minutes he breaks down how engineers at Anthropic build graphs that write the code, catch the bugs, and ships. The missing piece most developers skip: how to wire those agents into a graph that runs, verifies, and improves without you. Watch it, then read the full guide on graph engineering below.
31:23

Head of Claude Code, Boris Cherny: "You're not supposed to write code anymore. You're supposed to build a graph that writes itself." In 30 minutes he breaks down how engineers at Anthropic build graphs that write the code, catch the bugs, and ships. The missing piece most developers skip: how to wire those agents into a graph that runs, verifies, and improves without you. Watch it, then read the full guide on graph engineering below.

Mahax

412,955 views • 10 days ago

Andrew Ng built agentic knowledge graph that runs agents loops from scratch: his agents searched thousands of tools through the graph, found the "right" one by meaning, and called it agent efficiency increased by 90% here's how: step 1 → embed every tool, search by meaning - not just keywords step 2 → but "similar" ≠ "correct" - it grabs the wrong one, skips the step before it step 3 → map tools as a graph - nodes are tools, edges are what runs before what step 4 → retrieve the path, not one tool - every tool the task needs, in order step 5 → bake the process into the graph - the sequence becomes data, not a guess most agents fail here and no one knows why - 1-hour brilliant course about it watch & bookmark - then read full course about graph engineering ↓
1:04:49

Andrew Ng built agentic knowledge graph that runs agents loops from scratch: his agents searched thousands of tools through the graph, found the "right" one by meaning, and called it agent efficiency increased by 90% here's how: step 1 → embed every tool, search by meaning - not just keywords step 2 → but "similar" ≠ "correct" - it grabs the wrong one, skips the step before it step 3 → map tools as a graph - nodes are tools, edges are what runs before what step 4 → retrieve the path, not one tool - every tool the task needs, in order step 5 → bake the process into the graph - the sequence becomes data, not a guess most agents fail here and no one knows why - 1-hour brilliant course about it watch & bookmark - then read full course about graph engineering ↓

codila

16,276 views • 21 days ago

Had a bunch of fun chatting about design, engineering and the future, three of my favorite things, with Ridd 🤿! We chat a bunch about Opacity, the way design SHOULD work 😎, and the impact of AI on design. Give it a watch/listen!
1:11

Had a bunch of fun chatting about design, engineering and the future, three of my favorite things, with Ridd 🤿! We chat a bunch about Opacity, the way design SHOULD work 😎, and the impact of AI on design. Give it a watch/listen!

Drew Wilson

24,929 views • 9 months ago

Google Brain founder, Andrew Ng: "One of the most important skills of the future is the ability to tell a computer exactly what you want so it can do it for you." In this talk, he explains why the biggest opportunity isn't just using AI. It's learning how to turn work into agentic workflows, break tasks into steps, give agents the right tools and context, add evals, and make the whole system reliable. That's the difference between prompting an AI and engineering an agent that actually works. Watch it today, then read the full guide in the article below.
26:58

Google Brain founder, Andrew Ng: "One of the most important skills of the future is the ability to tell a computer exactly what you want so it can do it for you." In this talk, he explains why the biggest opportunity isn't just using AI. It's learning how to turn work into agentic workflows, break tasks into steps, give agents the right tools and context, add evals, and make the whole system reliable. That's the difference between prompting an AI and engineering an agent that actually works. Watch it today, then read the full guide in the article below.

Rahul

11,553 views • 2 days ago