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.
youtube.com/watch?v=bSG9wUYa…
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.
AI Coding models & tools are commoditising. The context flywheel turns that into a moat.
One investment → four compounding returns: agent quality, deeper expertise, team learning, org alignment.
The teams that wins won't have the best AI. They'll have the best context.
tessl.io/blog/the-context-fl…
There is a lot of noise around that having a “Agent.md” hurts the agents results. The nuace is that it talks about autogenerated init (slop?)
The equivalent would be :
Do you stop writing tests because auto-generated test are bad ?
It's what the article implies for context. We think there is great value of improving the context and doing it in rigorous using evals. It's an artifact that has a lifecycle you need to work on.
See tessl.io/blog/your-agentsmd-…
Agentic Coding Meetup in Amsterdam - 25 March - week of #Kubecon - Come join us at Booking.com for a fun evening and chat about the future !
Place are limited and be quick ! Registrations closes 1 week before the event.
Got a good story to tell ? Recommend a speaker ? Send me DM and let's chat.
Register: luma.com/j8qomf3x
Tomorrow: Optimizing Agentic Coding context × Context Development Lifecycle webinar with Dru Knox and me.
We'll share the:
- the lifecycle concepts and why they matter
- the lessons learned while building out the solution atTessl
- and practical tips on how you can start right away
Come with your questions, your concerns, your experience.
We want the *real* talk !
luma.com/jb4mk5fg
Intentional overuse of AI as my learning strategy. Use it for everything — especially what it's bad at. You don't learn the edges of the map by staying in the center.
jedi.be/blog/2026/intentiona…