A diagram showcasing the evolution from LLM to Agents and beyond - Does this align with your journey ? #aiengineer

In the Agentic AI race, everyone’s picking a winner. Before you pick yours, ask @patrickdebois. The “Godfather of DevOps” and founder of DevOpsDays joins @mitchellashley, VP & Practice Lead, Software Lifecycle Engineering at @TheFuturumGroup, for a live Ask Me Anything at DevOps Experience 2026. No slides. No scripted presentation. Just a live conversation and your questions on Agentic AI, DevOps and where the industry is headed next. 📅 September 24, 2026 ⏰ 11:30 AM ET 💻 Free and virtual Save your spot: buff.ly/47Xhgnq #DevOps #DevOpsExperience2026 #AgenticAI #AMA #Techstrong

Hey my @Devoxx peeps! I am sitting down with the one, the only @patrickdebois to discuss the agentic software factory and the agentic SDLC in Antwerp on October 6th! Don't miss it (we'll also feed you, thanks to @tweetsbyport!). Register here: luma.com/p4lv4ct5?tk=dfF5KI

Trying to clarify different AI software factory loops: (blogpost pending) - production loops: these act on the code - maintenance loops: keeps the line running within the factory rules - feedback loops: changes the rules what the factory decides Thoughts are welcome!

Secret new Location of AIE Europe ? - cc @swyx

Agent: should I do A or B Me: yes

Incredible proud to be presenting again at AIE SF. We continue the story from the Context Development Lifecycle and Harnesses and go scaling it out into the org. Big thanks @aiDotEngineer for this first class event! Really looking forward to it. ai.engineer/worldsfair/sched…

llm= road, coding agent = car, pilot = coder, context = fuel . What else would you add to the metaphor?

So I hear Claude Code will charge extra for "-p". Here's a simple gist to do a headless call without it. gist.github.com/jedi4ever/75…

The best AI coding conference is coming to London 🎉 and I have a 50% discount code for you (PATRICK50). AI Native DevCon, June 1-2. As content curator, proudly biased, I genuinely think we've built the best program on AI coding out , see you there ! - ainativedevcon.io - luma.com/aidevcon-ldn26?coup…

Context may be the most under-engineered layer in AI coding today. In this keynote, @patrickdebois, argues that if agents are driven by prompts, rules, and memory, then context deserves the same rigor we already give code. piped.video/watch?v=bSG9wUYa…

Background Agents Summit schedule looking 🔥 The first event of it's kind to explore what agents throughout the SDLC look like. Presented by the companies actually doing it today. @patrickdebois @pelikhan @colemurray @leodido @csweichel @MattJamesBoyle @suhailpatel @casualzach_

The Human Harness engineer = The person that enables the Agentic Coder

Wonder if anyone created a website where agents do all the writing and you just feed/curate relevant articles as context.

I created 'Self driving Repo' (. com) - let's you spawn recurring agents with budget control - agents have full FS access and sources like other repos, issues, and the web - agent outputs are pushed to your preferred repo/branch This makes it super easy to setup durable knowledge-base automations in the cloud reply 'yes' for early access

Context Coders & Agentic Coders: I see two distinct coder types emerge: the Context coders manage the context development lifecycle and use the agentic pipelines the Agentic coder maintain: a platform provided to other coders. So some will keep building the thing and others build the thing that builds the thing. The latter might be the new CI/CD emerging.

Great read from @patrickdebois. Clear gap in the market for a 'context hub' to replace GitHub for coding teams. Code storage is a small part of it. CI/CD needs re-tooling. DevOps need retooling. Agent session history needs analyzing, etc etc etc

Context maturity for coding agents. Not agent maturity. Context maturity. Three dimensions: 1/your tools, 2/your context, 3/your org. Most teams are advancing one and ignoring the other two. He're the full article - tessl.co/ggm

If context==code now , can we test it in CI/CD ? I tried to answer that in my article highlighting the challenges with it . tessl.io/blog/cicd-for-conte…

Context Development Lifecycle (as @patrickdebois nicely named it) should starts with accountable commits. This AI agent links every commit to a signed diary entry — capturing why, not just what. Both signed. Both verifiable. Code is accountable. Context should be too.