Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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

DataChaz's profile picture

Charly Wargnier ♨️

180,455 subscribers

29,622 Aufrufe • vor 1 Tag •via X (Twitter)

Nachrichten & PolitikWissenschaft & Technologie
LIVE

Anya Rossi• Live Now

Private livecam show

10 Kommentare

Profilbild von Charly Wargnier ♨️
Charly Wargnier ♨️vor 1 Tag

Appreciate @Atlassian giving me an early look at this one and partnering with me on the launch 🫶 There’s a lot more in the full announcement here: >

Profilbild von E_genius
E_geniusvor 1 Tag

@Atlassian @Jira the 6% stat is the real story, most teams add copilots before fixing context and evals

Profilbild von Charly Wargnier ♨️
Charly Wargnier ♨️vor 1 Tag

@Atlassian @Jira so true @yevloop!

Profilbild von John
Johnvor 1 Tag

@Atlassian @Jira The Jira agent-loop piece is the interesting bit. Most agentic rollouts stall from no audit trail when something breaks, not bad models. Does the governance layer block merges or just log after the fact?

Profilbild von kartik bhardwaj
kartik bhardwajvor 1 Tag

@Atlassian @Jira The 64 percent has a selection problem in it. Teams that can hand an agent rich context are the ones with clean boundaries and current docs already, and those teams were shipping faster before any of this arrived.

Profilbild von Jules SEO Whisperer
Jules SEO Whisperervor 1 Tag

@Atlassian @Jira Context is the real bottleneck. Too many teams jump straight to tools without grounding agents in their actual codebase, then wonder why the output is noise. That 64% stat doesn't surprise me.

Profilbild von L 🍂
L 🍂vor 1 Tag

@Atlassian @Jira Looking to expand your reach and visibility? Let’s connect

Profilbild von Charly Wargnier ♨️
Charly Wargnier ♨️vor 1 Tag

@Atlassian @Jira Why not! just followed and DM' ya :)

Profilbild von BitFuturist
BitFuturistvor 1 Tag

@Atlassian @Jira 😎

Profilbild von Ali AlphaQ
Ali AlphaQvor 1 Tag

@Atlassian @Jira Fascinating signal. I think context and governance are the real unlock here. What guardrails keep agent loops reliable at scale?

Ähnliche Videos

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 Aufrufe • vor 2 Monaten

The best way to learn AI is to build with agents. To help with that, we've launched hands-on labs and a new series on Agentic Engineering. First topic: Agent Skills. Next in the pipeline: planning, context engineering, multi-agent systems, long-running agents,.. Go build!
9:09

The best way to learn AI is to build with agents. To help with that, we've launched hands-on labs and a new series on Agentic Engineering. First topic: Agent Skills. Next in the pipeline: planning, context engineering, multi-agent systems, long-running agents,.. Go build!

elvis

31,802 Aufrufe • vor 3 Monaten

Your engineering team is about to snap. And your AI coding agent is making it worse. Introducing CodeRabbit Agent for Slack 🎉 A second brain for engineering teams. Because your tribal knowledge lives in Slack threads nobody can find. At CodeRabbit, we review millions of PRs every week and know how ace engineering teams operate on the planet. The same three things slow every team we see: - Context and decisions that live elsewhere. - Lack of a team-level durable knowledge base - And a trust layer that gives a safety net to your teams Built for Agentic SDLC workflows, CodeRabbit Agent for Slack solves all three problems in one shot while enabling teams to collaborate in real-time with the Agent. CodeRabbit Agent is Slack-native and builds your team’s operating context from every thread, every decision, every conversation your team has ever had. Make your team’s context compound!
1:37

Your engineering team is about to snap. And your AI coding agent is making it worse. Introducing CodeRabbit Agent for Slack 🎉 A second brain for engineering teams. Because your tribal knowledge lives in Slack threads nobody can find. At CodeRabbit, we review millions of PRs every week and know how ace engineering teams operate on the planet. The same three things slow every team we see: - Context and decisions that live elsewhere. - Lack of a team-level durable knowledge base - And a trust layer that gives a safety net to your teams Built for Agentic SDLC workflows, CodeRabbit Agent for Slack solves all three problems in one shot while enabling teams to collaborate in real-time with the Agent. CodeRabbit Agent is Slack-native and builds your team’s operating context from every thread, every decision, every conversation your team has ever had. Make your team’s context compound!

Harjot Gill

4,777,289 Aufrufe • vor 4 Monaten

Google just dropped a 1-hour course on full AI engineering: from 1 agent to Loops and Graphs 7:02 - Build your first agent 13:34 - What agents can do 23:08 - Context engineering 32:56 - Graph engineering 54:11 - Full autonomous system One agent saves you an hour. A thousand replaces the team. Watch it, then read the full guide on loops and graphs below
1:05:30

Google just dropped a 1-hour course on full AI engineering: from 1 agent to Loops and Graphs 7:02 - Build your first agent 13:34 - What agents can do 23:08 - Context engineering 32:56 - Graph engineering 54:11 - Full autonomous system One agent saves you an hour. A thousand replaces the team. Watch it, then read the full guide on loops and graphs below

Mahax

40,205 Aufrufe • vor 23 Tagen

Google Engineers just showed how their AI engineers are building Context Graphs from 0% to 100%: 10% → 4:01 - how to build a Context Graph 30% → 15:00 - Graph Engineering explanation 55% → 30:00 - Agentic search Engineering 80% → 35:48 - Graph Engineering practice 100% → 47:06 - self-improving agents in graphs 54-minute Google workshop, and it’s one of the clearest hands-on examples of the shift from. Watch it today, then read the full Context Graphs Playbook below.
55:07

Google Engineers just showed how their AI engineers are building Context Graphs from 0% to 100%: 10% → 4:01 - how to build a Context Graph 30% → 15:00 - Graph Engineering explanation 55% → 30:00 - Agentic search Engineering 80% → 35:48 - Graph Engineering practice 100% → 47:06 - self-improving agents in graphs 54-minute Google workshop, and it’s one of the clearest hands-on examples of the shift from. Watch it today, then read the full Context Graphs Playbook below.

Morty

10,451 Aufrufe • vor 7 Tagen

.Aaron Levie says AI agents may take years to diffuse from engineering into the rest of knowledge work. "The models are really good at code, and the work is verifiable." "You have 5 or 10 things that make agents work in an enterprise context for engineering." "The users are less technical, the data is much more fragmented, the systems are much more legacy." "That's why it's going to be a number of years for this diffusion to roll from what we're seeing in Silicon Valley, into the rest of knowledge work."
1:27

.Aaron Levie says AI agents may take years to diffuse from engineering into the rest of knowledge work. "The models are really good at code, and the work is verifiable." "You have 5 or 10 things that make agents work in an enterprise context for engineering." "The users are less technical, the data is much more fragmented, the systems are much more legacy." "That's why it's going to be a number of years for this diffusion to roll from what we're seeing in Silicon Valley, into the rest of knowledge work."

MTS

13,046 Aufrufe • vor 4 Monaten

Anthropic engineer: “80% of our engineers are using Loops. Now everyone is exploring how to build right Context for agents.” in 3-6 months, we’ll all become context engineers. Context is the most important part of agents.” in this 1-hour talk, Anthropic engineer shows how to build a self-improving agents from sratch. It’s worth more than a $500 agentic course. Watch this video, then read the article below on how to become a context architect.
1:01:51

Anthropic engineer: “80% of our engineers are using Loops. Now everyone is exploring how to build right Context for agents.” in 3-6 months, we’ll all become context engineers. Context is the most important part of agents.” in this 1-hour talk, Anthropic engineer shows how to build a self-improving agents from sratch. It’s worth more than a $500 agentic course. Watch this video, then read the article below on how to become a context architect.

Codez

35,798 Aufrufe • vor 1 Monat

Anthropic engineer: “80% of our engineers are using self-improving loops. Now everyone is exploring how to build the right Context for agents.” in 3-6 months, we’ll all become context engineers. Context is the most important part of building agents.” In this 40-minute lecture, an Anthropic engineer shows how to build a self-improving agentic workflow from scratch. It’s worth more than a $500 agentic course. Watch this video, then read the article below on how to become a context architect.
39:27

Anthropic engineer: “80% of our engineers are using self-improving loops. Now everyone is exploring how to build the right Context for agents.” in 3-6 months, we’ll all become context engineers. Context is the most important part of building agents.” In this 40-minute lecture, an Anthropic engineer shows how to build a self-improving agentic workflow from scratch. It’s worth more than a $500 agentic course. Watch this video, then read the article below on how to become a context architect.

Movez

21,136 Aufrufe • vor 1 Monat

you might've heard about context engineering, but nobody has explained what it really is... that's why I made a full practical walkthrough on how to use it to make your AI outputs personalized and consistent in this walkthrough, I go over: – what context engineering actually is (without the jargon) – how to train AI on your own data and preferences – how to get outputs that sound like you wrote them (not generic AI) reply "context" and I'll DM it to you (must be following)
0:36

you might've heard about context engineering, but nobody has explained what it really is... that's why I made a full practical walkthrough on how to use it to make your AI outputs personalized and consistent in this walkthrough, I go over: – what context engineering actually is (without the jargon) – how to train AI on your own data and preferences – how to get outputs that sound like you wrote them (not generic AI) reply "context" and I'll DM it to you (must be following)

Tyler

20,018 Aufrufe • vor 1 Jahr

🚀 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,689,573 Aufrufe • vor 1 Monat

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 Aufrufe • vor 3 Monaten

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 Aufrufe • vor 26 Tagen

Google just dropped a 1-hour course on how to become an AI engineer in 2026: • 00:00 - Context engineering • 10:00 - How to build, deploy, and run AI agents • 31:52 - Agentic loops, long-running AI agents • 43:22 - Building MCP from scratch • 51:20 - Prompt engineering • 59:10 - AI development trends This 1-hour watch will replace a $500 AI engineering course. Watch it today, then read the full pipeline in the article below.
1:07:47

Google just dropped a 1-hour course on how to become an AI engineer in 2026: • 00:00 - Context engineering • 10:00 - How to build, deploy, and run AI agents • 31:52 - Agentic loops, long-running AI agents • 43:22 - Building MCP from scratch • 51:20 - Prompt engineering • 59:10 - AI development trends This 1-hour watch will replace a $500 AI engineering course. Watch it today, then read the full pipeline in the article below.

Codez

187,716 Aufrufe • vor 1 Monat

Creator of Claude Code: “I’m not prompting my agents anymore. I’m building "graphs" and "loops" - they’re building my agent. in 3-6 months, we’ll all be doing graph engineering for our agentic systems.” in 10-minute talk, Boris Cherny revealed what the future of agentic engineering will look like. worth more than a $500 agentic AI course. Watch it today, then read the full roadmap in the article below.
11:18

Creator of Claude Code: “I’m not prompting my agents anymore. I’m building "graphs" and "loops" - they’re building my agent. in 3-6 months, we’ll all be doing graph engineering for our agentic systems.” in 10-minute talk, Boris Cherny revealed what the future of agentic engineering will look like. worth more than a $500 agentic AI course. Watch it today, then read the full roadmap in the article below.

Codez

549,424 Aufrufe • vor 1 Monat

Google just dropped a 1-hour course on how to become an AI engineer in 2026: • 00:00 - Context engineering • 10:00 - How to build, deploy, and run AI agents • 31:52 - Agentic loops, long-running AI agents • 43:22 - Building MCP from scratch • 51:20 - Prompt engineering • 59:10 - AI development trends This 1-hour watch will replace a $500 AI engineering course. Watch it today, then read the article below.
1:07:47

Google just dropped a 1-hour course on how to become an AI engineer in 2026: • 00:00 - Context engineering • 10:00 - How to build, deploy, and run AI agents • 31:52 - Agentic loops, long-running AI agents • 43:22 - Building MCP from scratch • 51:20 - Prompt engineering • 59:10 - AI development trends This 1-hour watch will replace a $500 AI engineering course. Watch it today, then read the article below.

Aria Westcott

26,526 Aufrufe • vor 1 Monat

Anthropic engineer just released a 2-hour workshop on "Graph Engineering" for agentic systems: “80% of our engineers are using self-improving loops. Now everyone is building agentic graphs.” • 00:00 - Introduction to RAG & Graphs • 06:39 - Core of "Graph Engineering" (state, nodes) • 14:29 - 3 feedback loops of Graph agents • 23:06 - Agent evaluation with Graphs • 36:29 - Agent cycles in graphs • 1:15:22 - Agentic RAG & agent context • 1:41:20 - Evaluation datasets based on Graphs This 2-hour workshop will replace 10 paid courses on agentic engineering. Watch it today, then learn how to become a Graph Engineer in the article below.
2:20:59

Anthropic engineer just released a 2-hour workshop on "Graph Engineering" for agentic systems: “80% of our engineers are using self-improving loops. Now everyone is building agentic graphs.” • 00:00 - Introduction to RAG & Graphs • 06:39 - Core of "Graph Engineering" (state, nodes) • 14:29 - 3 feedback loops of Graph agents • 23:06 - Agent evaluation with Graphs • 36:29 - Agent cycles in graphs • 1:15:22 - Agentic RAG & agent context • 1:41:20 - Evaluation datasets based on Graphs This 2-hour workshop will replace 10 paid courses on agentic engineering. Watch it today, then learn how to become a Graph Engineer in the article below.

Codez

404,470 Aufrufe • vor 1 Monat

AI can write more code than any team can review by hand, and a pull request can look fine while hiding a security issue or missing a requirement. In our new short course, AI Code Review, built in collaboration with Qodo and taught by Nnenna 👩🏽‍💻✨, you'll learn the practices that make AI code review effective: review before you open a pull request, give the reviewer full context about your codebase, and triage findings by risk. Then you'll build your own review agent, from a context engine that finds the right code to a team of specialized reviewers. Enroll for free:
1:39

AI can write more code than any team can review by hand, and a pull request can look fine while hiding a security issue or missing a requirement. In our new short course, AI Code Review, built in collaboration with Qodo and taught by Nnenna 👩🏽‍💻✨, you'll learn the practices that make AI code review effective: review before you open a pull request, give the reviewer full context about your codebase, and triage findings by risk. Then you'll build your own review agent, from a context engine that finds the right code to a team of specialized reviewers. Enroll for free:

DeepLearning.AI

56,374 Aufrufe • vor 1 Monat

The new company brain. Context is the soul of your company, I learned today. Since I wrote a book, “Age of Context,” years ago I see that context is what we now call our private data. That data should be stored in a way to let AI agents and humans get more and more use out of it. This is precisely what PromptQL does and here Tanmai Gopal goes deep on how it now is a company brain, or, rather, a wiki that everyone updates and uses.
49:34

The new company brain. Context is the soul of your company, I learned today. Since I wrote a book, “Age of Context,” years ago I see that context is what we now call our private data. That data should be stored in a way to let AI agents and humans get more and more use out of it. This is precisely what PromptQL does and here Tanmai Gopal goes deep on how it now is a company brain, or, rather, a wiki that everyone updates and uses.

Robert Scoble

18,341 Aufrufe • vor 2 Monaten