Загрузка видео...

Не удалось загрузить видео

На главную

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...

DamiDefi's profile picture

Dami-Defi

98,407 subscribers

10,127 просмотров • 3 месяцев назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Ex-Google engineer just compressed the shift from AI agents to "graphs" and "loops" into one 2h47m lecture: • 00:00 - understanding the different layers of AI memory • 30:00 - moving from simple LLM calls to AI agents • 50:00 - why agent systems are becoming a graph engineering problem • 1:12:00 - connecting context, tools and agent state • 1:24:00 - building a minimal agent harness from scratch • 1:46:00 - breaking down the architecture behind Hermes Agent • 2:08:00 - turning agent concepts into working systems 167-minute deep dive, and one of the clearest ways to understand how AI engineering is moving beyond prompts The progression: Prompt → Context → Memory → Agent → Loop → Graph → Agent Harness Watch it today, then read the full roadmap below
2:47:42

Ex-Google engineer just compressed the shift from AI agents to "graphs" and "loops" into one 2h47m lecture: • 00:00 - understanding the different layers of AI memory • 30:00 - moving from simple LLM calls to AI agents • 50:00 - why agent systems are becoming a graph engineering problem • 1:12:00 - connecting context, tools and agent state • 1:24:00 - building a minimal agent harness from scratch • 1:46:00 - breaking down the architecture behind Hermes Agent • 2:08:00 - turning agent concepts into working systems 167-minute deep dive, and one of the clearest ways to understand how AI engineering is moving beyond prompts The progression: Prompt → Context → Memory → Agent → Loop → Graph → Agent Harness Watch it today, then read the full roadmap below

Morlex

51,558 просмотров • 1 месяц назад

He is 19, already built an AI system making $2.3M a year - and now teaches how to do it at Stanford 01:03 - he lost his job at Anthropic because of prompt engineering 09:34 - Context Engineering gives 10x to coding speed 28:47 - Opus 5 builds an AI system making $2.3M a year from scratch after watching I deleted all my prompts and switched to Context Engineering - first $20k+ in a month. Save & watch - the article below is a step by step guide to build an AI system
35:59

He is 19, already built an AI system making $2.3M a year - and now teaches how to do it at Stanford 01:03 - he lost his job at Anthropic because of prompt engineering 09:34 - Context Engineering gives 10x to coding speed 28:47 - Opus 5 builds an AI system making $2.3M a year from scratch after watching I deleted all my prompts and switched to Context Engineering - first $20k+ in a month. Save & watch - the article below is a step by step guide to build an AI system

Noisy

67,995 просмотров • 1 месяц назад

94% OF ENGINEERING ORGS USE AI. ONLY 6% SCALE IT The missing link is context and governance. That’s exactly what Atlassian is going after with its new agentic engineering stack: Code Context + governed agent loops in Atlassian Jira + DX measurement. The idea is simple: make agents a native part of your engineering system instead of a side quest in a terminal. > Code Context grounds them in your architecture > Governed loops take work from backlog to pull request > DX measures the impact And the data backs up the context thesis: DX found context-rich AI teams shipped ~64% more per developer 👊 A pretty strong signal that context is becoming one of the biggest leverage points in agentic engineering.
1:00

94% OF ENGINEERING ORGS USE AI. ONLY 6% SCALE IT The missing link is context and governance. That’s exactly what Atlassian is going after with its new agentic engineering stack: Code Context + governed agent loops in Atlassian Jira + DX measurement. The idea is simple: make agents a native part of your engineering system instead of a side quest in a terminal. > Code Context grounds them in your architecture > Governed loops take work from backlog to pull request > DX measures the impact And the data backs up the context thesis: DX found context-rich AI teams shipped ~64% more per developer 👊 A pretty strong signal that context is becoming one of the biggest leverage points in agentic engineering.

Charly Wargnier ♨️

29,622 просмотров • 17 дней назад

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 stops living inside one giant chat. Example: researching a startup idea. The chat way: - One model, one pass. - It decides what matters - Researches the market - Interprets the evidence - Writes the recommendation - Grades its own confidence. The graph way: - A planner breaks the question into angles - 5 researchers split up: customer, competitors, distribution, pricing, risks - A skeptic tries to kill the weak findings - A merger turns what survives into a one-page recommendation - You approve before you act Same written report. Completely different work behind it. Think: - Prompt = the question - Context = the information - Graph = the workflow Design the workflow. That's where it clicks.
2:11

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 stops living inside one giant chat. Example: researching a startup idea. The chat way: - One model, one pass. - It decides what matters - Researches the market - Interprets the evidence - Writes the recommendation - Grades its own confidence. The graph way: - A planner breaks the question into angles - 5 researchers split up: customer, competitors, distribution, pricing, risks - A skeptic tries to kill the weak findings - A merger turns what survives into a one-page recommendation - You approve before you act Same written report. Completely different work behind it. Think: - Prompt = the question - Context = the information - Graph = the workflow Design the workflow. That's where it clicks.

The Startup Ideas Podcast (SIP) 🧃

19,232 просмотров • 1 месяц назад

🎨 Introducing Prompt Canvas — a novel UX for prompt engineering Building LLM applications requires new and dedicated tools for prompt engineering. With Prompt Canvas in LangSmith, you can: • Collaborate with an AI agent to draft, refine, and edit your prompts • Define custom quick actions to standardize prompting strategies used across the org ✍️ Learn more: ➡️ Try it out:
4:12

🎨 Introducing Prompt Canvas — a novel UX for prompt engineering Building LLM applications requires new and dedicated tools for prompt engineering. With Prompt Canvas in LangSmith, you can: • Collaborate with an AI agent to draft, refine, and edit your prompts • Define custom quick actions to standardize prompting strategies used across the org ✍️ Learn more: ➡️ Try it out:

LangChain

43,733 просмотров • 1 год назад

Anthropic just changed how they think about Claude 5. Not with a new model. Not with a benchmark. With a completely different philosophy for building AI systems. Most people will miss it. They're still trying to write better prompts. Anthropic is optimizing something else entirely: Context. Here's what every AI builder should learn from it: 1. Stop telling AI exactly what to do. Start telling it what success looks like. Older models needed rigid instructions. Newer models perform better when you define the objective and let them make the decisions. The goal is no longer more control. It's more clarity. 2. Context is a budget, not a storage unit. Every extra sentence competes for the model's attention. A massive context file doesn't make AI smarter. It often makes reasoning worse. The best systems don't load everything. They load only what's relevant. 3. Great tools beat great prompts. Most people spend hours tweaking prompt wording. Anthropic is investing in better interfaces instead. Clear parameters. Structured inputs. Well-designed tools. If the interface removes ambiguity, the model makes better decisions before it even starts reasoning. 4. Show reality instead of describing it. Want a specific coding style? Provide the codebase. Want a certain design language? Share the mockup. Want consistent outputs? Give it tests to satisfy. Concrete references consistently outperform long written instructions. 5. Deliver information when it's needed. Not everything belongs in the initial context. Documentation. Style guides. Verification. Reviews. Load them only when they're relevant. Think of context like RAM, not a hard drive. 6. The real advantage is system design. Prompt engineering isn't disappearing. It's becoming one small part of a much bigger stack. Memory. Retrieval. Context architecture. Tool design. Evaluation. Every improvement compounds. The biggest takeaway from Anthropic's update? The next generation of AI won't be won by the people writing the longest prompts. It'll be won by the people building the smartest systems. Same models. Completely different results.
0:30

Anthropic just changed how they think about Claude 5. Not with a new model. Not with a benchmark. With a completely different philosophy for building AI systems. Most people will miss it. They're still trying to write better prompts. Anthropic is optimizing something else entirely: Context. Here's what every AI builder should learn from it: 1. Stop telling AI exactly what to do. Start telling it what success looks like. Older models needed rigid instructions. Newer models perform better when you define the objective and let them make the decisions. The goal is no longer more control. It's more clarity. 2. Context is a budget, not a storage unit. Every extra sentence competes for the model's attention. A massive context file doesn't make AI smarter. It often makes reasoning worse. The best systems don't load everything. They load only what's relevant. 3. Great tools beat great prompts. Most people spend hours tweaking prompt wording. Anthropic is investing in better interfaces instead. Clear parameters. Structured inputs. Well-designed tools. If the interface removes ambiguity, the model makes better decisions before it even starts reasoning. 4. Show reality instead of describing it. Want a specific coding style? Provide the codebase. Want a certain design language? Share the mockup. Want consistent outputs? Give it tests to satisfy. Concrete references consistently outperform long written instructions. 5. Deliver information when it's needed. Not everything belongs in the initial context. Documentation. Style guides. Verification. Reviews. Load them only when they're relevant. Think of context like RAM, not a hard drive. 6. The real advantage is system design. Prompt engineering isn't disappearing. It's becoming one small part of a much bigger stack. Memory. Retrieval. Context architecture. Tool design. Evaluation. Every improvement compounds. The biggest takeaway from Anthropic's update? The next generation of AI won't be won by the people writing the longest prompts. It'll be won by the people building the smartest systems. Same models. Completely different results.

Evan Luthra

38,751 просмотров • 2 месяцев назад

🎯 Introducing AI Prompts If you find yourself rewriting the same requests to AI over and over, save them as AI Prompts instead. Start with Evernote's Prompt Library for inspiration, then create your own reusable prompts that understand your context. Find AI Prompts when starting a new note, in the toolbar when selecting text, or from an audio recording. What AI Prompt would save you the most time? We'd love to hear your ideas in the comments. 👇
1:53

🎯 Introducing AI Prompts If you find yourself rewriting the same requests to AI over and over, save them as AI Prompts instead. Start with Evernote's Prompt Library for inspiration, then create your own reusable prompts that understand your context. Find AI Prompts when starting a new note, in the toolbar when selecting text, or from an audio recording. What AI Prompt would save you the most time? We'd love to hear your ideas in the comments. 👇

Evernote

10,601 просмотров • 2 месяцев назад

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

102,835 просмотров • 1 месяц назад

EVERYONE HAS BEEN TALKING ABOUT AI AGENTS. BUT THE REAL UNLOCK ISN'T BETTER PROMPTS: IT'S BETTER LOOPS. Everyone is chasing the perfect prompt. The top AI engineers are chasing something else: loops. Instead of chatting back and forth with AI, they give it one goal and let it continuously improve its own work until the objective is met. Here's the framework: • Define the goal once • AI discovers the work required • Specialized agents tackle tasks in parallel • A verification agent checks the results • If the goal isn't met: loop again. If it is: deliver. The key ingredient is memory. Each cycle remembers what was completed, what failed, and what still needs work, so every iteration gets smarter instead of starting from scratch. There are two approaches: • Open loops: Maximum autonomy, but higher token costs as AI explores freely. • Closed loops: Clear boundaries, defined success metrics, lower costs, and far more practical for everyday workflows. Don't ask AI to complete a task. Build a system where AI can plan, execute, verify, remember, and repeat until the task is actually finished. Prompt engineering got us here. Loop engineering is what takes AI from assistant to autonomous teammate.
19:17

EVERYONE HAS BEEN TALKING ABOUT AI AGENTS. BUT THE REAL UNLOCK ISN'T BETTER PROMPTS: IT'S BETTER LOOPS. Everyone is chasing the perfect prompt. The top AI engineers are chasing something else: loops. Instead of chatting back and forth with AI, they give it one goal and let it continuously improve its own work until the objective is met. Here's the framework: • Define the goal once • AI discovers the work required • Specialized agents tackle tasks in parallel • A verification agent checks the results • If the goal isn't met: loop again. If it is: deliver. The key ingredient is memory. Each cycle remembers what was completed, what failed, and what still needs work, so every iteration gets smarter instead of starting from scratch. There are two approaches: • Open loops: Maximum autonomy, but higher token costs as AI explores freely. • Closed loops: Clear boundaries, defined success metrics, lower costs, and far more practical for everyday workflows. Don't ask AI to complete a task. Build a system where AI can plan, execute, verify, remember, and repeat until the task is actually finished. Prompt engineering got us here. Loop engineering is what takes AI from assistant to autonomous teammate.

Dami-Defi

13,363 просмотров • 2 месяцев назад

Everything Context Engineering & Cookoff between dex, co-founder and CEO of humanlayer, and allen. 0:12 - Meet Dex Horthy (Humanlayer) + Cooking Challenge 1:15 - Tasting Dan Dan Noodles 1:25 - How Dex Got a NASA Internship at 17 3:36 - The Origin of “Context Engineering” 6:24 - What AI “Slop” Actually Means 8:06 - From Engineer to Founder 12:54 - How Context Engineering Is Changing 15:23 - The “Dumb Zone” of Context Windows 18:59 - Will AI Replace Software Engineers? 21:27 - Chaotic Final Plating 22:00 - Taste Test: Who Cooked It Better? 24:24 - Judges Decide the Winner Look up Latent Space on Youtube, Spotify, Apple Podcasts, etc.
24:58

Everything Context Engineering & Cookoff between dex, co-founder and CEO of humanlayer, and allen. 0:12 - Meet Dex Horthy (Humanlayer) + Cooking Challenge 1:15 - Tasting Dan Dan Noodles 1:25 - How Dex Got a NASA Internship at 17 3:36 - The Origin of “Context Engineering” 6:24 - What AI “Slop” Actually Means 8:06 - From Engineer to Founder 12:54 - How Context Engineering Is Changing 15:23 - The “Dumb Zone” of Context Windows 18:59 - Will AI Replace Software Engineers? 21:27 - Chaotic Final Plating 22:00 - Taste Test: Who Cooked It Better? 24:24 - Judges Decide the Winner Look up Latent Space on Youtube, Spotify, Apple Podcasts, etc.

Latent.Space

14,971 просмотров • 6 месяцев назад

Happy to properly launch Anna, the proactive AI agent for parents! Uncovering a bit of the technology behind the scenes! Building Anna is where I learned: 💾 Memory as plain text sucks. You need structured memory. Like a full-blown PostgreSQL DB that stores your tasks and calendar in a structured manner. Most harnesses are good at coding-related stuff. Let it do the query. Don't let it vibe-search the memory. Let it vibe your SQL query 💭 Dreaming is a useful concept for enhancing memory to feed the LLM context. But DO NOT vibe your dream. Asking your agent to "hey, just dream and keep the relevant memory around" is a recipe for deleting a bunch of important information and keeping trash around. Your dream needs to have some Taxonomy (or better, Ontology). What information is important? For who? With what object? What can they do? And again, these are impossible to describe and act well without a proper schema 🔄 Loop Engineering is important for smoothing out rough edges in the system we build. But even expensive loop engineering with a state-of-the-art model can't out-engineer bad system design. The highest leverage an AI Engineer can do is actually building the right system design, and having an eye on both product delight and engineering scalability There are several more insights that I plan to cover in a dedicated video about Agentic AI Engineering. But it's actually a huge relief that the future of software engineering... is still software engineering
2:10

Happy to properly launch Anna, the proactive AI agent for parents! Uncovering a bit of the technology behind the scenes! Building Anna is where I learned: 💾 Memory as plain text sucks. You need structured memory. Like a full-blown PostgreSQL DB that stores your tasks and calendar in a structured manner. Most harnesses are good at coding-related stuff. Let it do the query. Don't let it vibe-search the memory. Let it vibe your SQL query 💭 Dreaming is a useful concept for enhancing memory to feed the LLM context. But DO NOT vibe your dream. Asking your agent to "hey, just dream and keep the relevant memory around" is a recipe for deleting a bunch of important information and keeping trash around. Your dream needs to have some Taxonomy (or better, Ontology). What information is important? For who? With what object? What can they do? And again, these are impossible to describe and act well without a proper schema 🔄 Loop Engineering is important for smoothing out rough edges in the system we build. But even expensive loop engineering with a state-of-the-art model can't out-engineer bad system design. The highest leverage an AI Engineer can do is actually building the right system design, and having an eye on both product delight and engineering scalability There are several more insights that I plan to cover in a dedicated video about Agentic AI Engineering. But it's actually a huge relief that the future of software engineering... is still software engineering

Gogo | Dota for Toxicity

30,766 просмотров • 2 месяцев назад

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: 0% → 01:45 - build an LLM from scratch 30% → 17:22 - learn how to actually use AI models 60% → 30:03 - master prompt engineering 100% → 52:35 - coordinate 100 agents as one human Most people are still learning how to prompt a single model. Jeff Dean is showing the entire stack: LLMs → Prompts → Agents → Agent Teams → Graphs Prompting is the old workflow. Coordinating entire agent systems is the next one. This is 27 years of Google AI compressed into a single hour. Bookmark it and watch today. Then read the full Graph Engineering guide below ↓
1:06:06

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: 0% → 01:45 - build an LLM from scratch 30% → 17:22 - learn how to actually use AI models 60% → 30:03 - master prompt engineering 100% → 52:35 - coordinate 100 agents as one human Most people are still learning how to prompt a single model. Jeff Dean is showing the entire stack: LLMs → Prompts → Agents → Agent Teams → Graphs Prompting is the old workflow. Coordinating entire agent systems is the next one. This is 27 years of Google AI compressed into a single hour. Bookmark it and watch today. Then read the full Graph Engineering guide below ↓

Lunar

25,192 просмотров • 26 дней назад

Use this ai workflow to get 1000s of followers/day (Steps and tools included) Step 1: Find 3 posts that went massive Step 2: Ask Claude to break down WHY they worked Step 3: Extract the psychological patterns Step 4: Build prompts that interview YOU for context Tools: Claude 4.1 extended thinking (not basic GPT) Cost: $20/month Time: 10 min setup → infinite personalized content The KEY: Context is KING You have to feed it YOUR voice parameters You have to give it audience psychology You're one prompt away from automating your content creation like a pro Stop using garbage prompts Start reverse-engineering what works Use this playbook
10:14

Use this ai workflow to get 1000s of followers/day (Steps and tools included) Step 1: Find 3 posts that went massive Step 2: Ask Claude to break down WHY they worked Step 3: Extract the psychological patterns Step 4: Build prompts that interview YOU for context Tools: Claude 4.1 extended thinking (not basic GPT) Cost: $20/month Time: 10 min setup → infinite personalized content The KEY: Context is KING You have to feed it YOUR voice parameters You have to give it audience psychology You're one prompt away from automating your content creation like a pro Stop using garbage prompts Start reverse-engineering what works Use this playbook

The Startup Ideas Podcast (SIP) 🧃

21,538 просмотров • 11 месяцев назад

INTRODUCING FACTORY Factory is the Command Center where developers and agentic AI collaborate to understand, plan, and build enterprise software. Our enterprise platform combines advanced engineering system indexing, state-of-the-art retrieval and search, and reliable agentic systems powered by frontier LLMs. In your Factory, • 🤖 Droid Mode unlocks cutting-edge agentic capabilities. Accelerate your development with AI that autonomously pulls in tickets, reads error logs, retrieves relevant context, executes code, and solves complex, long-running tasks. • 🪡 Threads let you jump into deep work with all relevant context dynamically surfaced in front of you. No more crawling through Github, Slack, Google Drive, Notion, Jira, Slack, or context-switching between them. • ⚡ Workflows transform and centralize your organization’s best practices into executable, AI-powered processes. Automate repetitive tasks like building integrations, bug-fixing, PRD creation, release notes, version updates, and more. We're working with some of the most innovative organizations in software — from AI-forward enterprises like MongoDB to high-growth organizations across the world. Our enterprise platform combines advanced engineering system indexing, state-of-the-art retrieval and search, and reliable agentic systems using frontier LLMs like o3 and Claude 3.7 Sonnet 1/7
0:57

INTRODUCING FACTORY Factory is the Command Center where developers and agentic AI collaborate to understand, plan, and build enterprise software. Our enterprise platform combines advanced engineering system indexing, state-of-the-art retrieval and search, and reliable agentic systems powered by frontier LLMs. In your Factory, • 🤖 Droid Mode unlocks cutting-edge agentic capabilities. Accelerate your development with AI that autonomously pulls in tickets, reads error logs, retrieves relevant context, executes code, and solves complex, long-running tasks. • 🪡 Threads let you jump into deep work with all relevant context dynamically surfaced in front of you. No more crawling through Github, Slack, Google Drive, Notion, Jira, Slack, or context-switching between them. • ⚡ Workflows transform and centralize your organization’s best practices into executable, AI-powered processes. Automate repetitive tasks like building integrations, bug-fixing, PRD creation, release notes, version updates, and more. We're working with some of the most innovative organizations in software — from AI-forward enterprises like MongoDB to high-growth organizations across the world. Our enterprise platform combines advanced engineering system indexing, state-of-the-art retrieval and search, and reliable agentic systems using frontier LLMs like o3 and Claude 3.7 Sonnet 1/7

Factory

328,209 просмотров • 1 год назад

🚀 Global Launch: Jarvix, Your Context OS is now live! Meet the next generation of personalized AI built around your context, your taste, and your way of thinking. #JarvixOS transforms how you work with AI by understanding your patterns, carrying your context across agents, and helping you move from ideas to action. Step into a new era of AI collaboration: • Discover your AI-native archetype • Build your personal AI model from your evolving AI interactions • Never start from zero - your context moves with you across sessions • Coordinate Codex, Claude Code, Gemini, Hermes, OpenClaw, and more as one connected AI team. • Turn insights into your next move, with you always in control Instead of adapting yourself to every agent, Jarvix carries the context you choose, helps you understand what it reveals, and brings the right agents together when you decide to act. Your AI tools shouldn’t work like separate assistants. They should work like one team. That’s the future of AI: Not more agents. One shared context. One Jarvix.
1:34

🚀 Global Launch: Jarvix, Your Context OS is now live! Meet the next generation of personalized AI built around your context, your taste, and your way of thinking. #JarvixOS transforms how you work with AI by understanding your patterns, carrying your context across agents, and helping you move from ideas to action. Step into a new era of AI collaboration: • Discover your AI-native archetype • Build your personal AI model from your evolving AI interactions • Never start from zero - your context moves with you across sessions • Coordinate Codex, Claude Code, Gemini, Hermes, OpenClaw, and more as one connected AI team. • Turn insights into your next move, with you always in control Instead of adapting yourself to every agent, Jarvix carries the context you choose, helps you understand what it reveals, and brings the right agents together when you decide to act. Your AI tools shouldn’t work like separate assistants. They should work like one team. That’s the future of AI: Not more agents. One shared context. One Jarvix.

Jarvix

1,690,718 просмотров • 1 месяц назад

8 months ago we started explaining enterprise AI on YouTube. 2M views later, here are the 5 shifts that actually defined 2025. Timestamps 00:36 Prompt Engineering → Agent Engineering 00:51 Prompting best practices 01:19 How context engineering focuses on curating information 01:51 Evolution of assistants to agents 02:12 Agents handling complex tasks 02:58 How security became foundational 03:36 The correct security architecture for organizations 04:23 The emergence of model flexibility 05:26 The importance of governance and trust
7:40

8 months ago we started explaining enterprise AI on YouTube. 2M views later, here are the 5 shifts that actually defined 2025. Timestamps 00:36 Prompt Engineering → Agent Engineering 00:51 Prompting best practices 01:19 How context engineering focuses on curating information 01:51 Evolution of assistants to agents 02:12 Agents handling complex tasks 02:58 How security became foundational 03:36 The correct security architecture for organizations 04:23 The emergence of model flexibility 05:26 The importance of governance and trust

Box

460,406 просмотров • 9 месяцев назад

.Tensol turns OpenClaw into full-time AI employees for your company. They handle repetitive workflows across support, engineering, sales and more — running 24/7 in a secure environment, connected to your tools, with full context of your business. Congrats on the launch pratik and Oliviero Pinotti!
1:42

.Tensol turns OpenClaw into full-time AI employees for your company. They handle repetitive workflows across support, engineering, sales and more — running 24/7 in a secure environment, connected to your tools, with full context of your business. Congrats on the launch pratik and Oliviero Pinotti!

Y Combinator

283,511 просмотров • 7 месяцев назад

FIVE LAYERS OF AGENT ENGINEERING, EACH ONE WRAPS THE ONE BELOW IT. IF YOU SKIP LAYER 2, YOUR LAYER 5 WILL LOOK BROKEN WHEN IT IS ACTUALLY JUST STANDING ON NOTHING. for weeks i debated harness vs loop vs graph like they were competing choices. then a stack diagram made the shape obvious. they are not choices. they are floors. 01 | prompt engineering. the message. unit of work: one input. inputs are role, instructions, examples, format. output is a single raw response. 02 | context engineering. the memory. unit of work: what stays in the window. a curator selects, compresses, and drops from query, docs, memory, prior turns, and tool outputs before the prompt runs. 03 | harness engineering. the machine. unit of work: the machine itself. gather (context + prompt) → LLM → tools or sub-agents → verifier → final response. the article calls this the operating environment. 04 | loop engineering. the system. unit of work: the run. goal + success criteria + max iterations + budget + completion check wrap around one harness pass. failed pass appends results to context and retries. 05 | graph engineering. the topology. unit of work: the graph run. goal + nodes + edges + state schema. graph routes to agent nodes, tool nodes, or human approval. a reviewer node with a different model and fresh context checks the final answer. the wrapping is the whole point. layer 5 assumes layer 4 works. layer 4 assumes layer 3 works. skip layer 2 and layer 3's verifier keeps failing without a clear reason. this is why swapping the model is a one-day project and swapping the stack is a quarter. the model is the commodity. the five layers around it are the engineering. full three-layer breakdown of the top of the stack (harness, loop, graph) in the post below.
0:20

FIVE LAYERS OF AGENT ENGINEERING, EACH ONE WRAPS THE ONE BELOW IT. IF YOU SKIP LAYER 2, YOUR LAYER 5 WILL LOOK BROKEN WHEN IT IS ACTUALLY JUST STANDING ON NOTHING. for weeks i debated harness vs loop vs graph like they were competing choices. then a stack diagram made the shape obvious. they are not choices. they are floors. 01 | prompt engineering. the message. unit of work: one input. inputs are role, instructions, examples, format. output is a single raw response. 02 | context engineering. the memory. unit of work: what stays in the window. a curator selects, compresses, and drops from query, docs, memory, prior turns, and tool outputs before the prompt runs. 03 | harness engineering. the machine. unit of work: the machine itself. gather (context + prompt) → LLM → tools or sub-agents → verifier → final response. the article calls this the operating environment. 04 | loop engineering. the system. unit of work: the run. goal + success criteria + max iterations + budget + completion check wrap around one harness pass. failed pass appends results to context and retries. 05 | graph engineering. the topology. unit of work: the graph run. goal + nodes + edges + state schema. graph routes to agent nodes, tool nodes, or human approval. a reviewer node with a different model and fresh context checks the final answer. the wrapping is the whole point. layer 5 assumes layer 4 works. layer 4 assumes layer 3 works. skip layer 2 and layer 3's verifier keeps failing without a clear reason. this is why swapping the model is a one-day project and swapping the stack is a quarter. the model is the commodity. the five layers around it are the engineering. full three-layer breakdown of the top of the stack (harness, loop, graph) in the post below.

kocer

31,162 просмотров • 28 дней назад

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.
0:22

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,180 просмотров • 4 месяцев назад

You do not need a CS degree to become an AI engineer. You need the map. Tokens. APIs. Python. Git. Context engineering. Structured outputs. RAG. Vector databases. Agents. Tool use. Evals. Cost control. Security. Shipping. That is the real curriculum. Not conference words. Not ML theory cosplay. Not pretending you need a PhD before building anything. The people getting hired are not the ones who memorised all 36 concepts. They are the ones who learned enough to ship 3 real projects and explain the tradeoffs. AI engineering in 2026 is not about knowing everything. It is about building systems that survive outside the demo. Bookmark this before you spend another year waiting for permission to start.
0:34

You do not need a CS degree to become an AI engineer. You need the map. Tokens. APIs. Python. Git. Context engineering. Structured outputs. RAG. Vector databases. Agents. Tool use. Evals. Cost control. Security. Shipping. That is the real curriculum. Not conference words. Not ML theory cosplay. Not pretending you need a PhD before building anything. The people getting hired are not the ones who memorised all 36 concepts. They are the ones who learned enough to ship 3 real projects and explain the tradeoffs. AI engineering in 2026 is not about knowing everything. It is about building systems that survive outside the demo. Bookmark this before you spend another year waiting for permission to start.

Fluixo

14,539 просмотров • 3 месяцев назад