Graph Engineering
topic on 1 show · 5 statements across 1 episodes
5 statements about Graph Engineering, every show
Isenberg: AI graph engineering builds compounding organizational memory over time
“The real compounding value of graph engineering isn't just that one task gets better. It's that your work starts producing memory. What do I mean by that? I mean that every customer research graph creates better customer notes. Every content graph creates bett…”
Isenberg: The goal is to build the smallest effective AI graph
“The goal is actually to make the smallest graph that improves the quality of work, and that's a really important distinction, because a good graph should remove fake waiting, and it should separate workers from checkers, and really it should put human approval…”
Isenberg: Graph engineering makes AI quality less dependent on perfect prompts
“Like, a big reason why graph engineering matters is it makes quality less dependent on someone remembering a perfect prompt to ask their LLM. It makes reviews way more consistent. It makes delegation in general way cleaner. It makes approval way more explicit.…”
Isenberg: AI coding tools are moving toward multi-step graph workflows
“And that's basically where all these AI coding tools are going. The model writing the code is only one part of the workflow, and there's leverage in all the planning and testing and reviewing and inspecting and deciding what is actually safe to ship.”
Isenberg: Graph engineering moves AI out of single messy chat interfaces
“Prompt engineering is how you ask the AI for a better question. And context engineering is how you give AI better information. But graph engineering is how you design the work around the AI so the whole thing stops living inside one messy giant AI chat.”