Patrick Debois

43.5K posts

Patrick Debois banner
Patrick Debois

Patrick Debois

@patrickdebois

Generative AI and DevOps specialist - co-author Devops Handbook - https://t.co/PZlox9jwoq

Ghent, Flanders, Belgium Katılım Temmuz 2008
8.5K Takip Edilen30.7K Takipçiler
Sabitlenmiş Tweet
Patrick Debois
Patrick Debois@patrickdebois·
A diagram showcasing the evolution from LLM to Agents and beyond - Does this align with your journey ? #aiengineer
Patrick Debois tweet media
English
11
13
57
5.2K
Matt Pocock
Matt Pocock@mattpocockuk·
@MoizIbnYousaf No QMD for now, just agentic search No obsidian, but obsidian-compatible
English
4
0
12
5.3K
Matt Pocock
Matt Pocock@mattpocockuk·
Doing my first ever experiments with a personal, entirely agent-managed Karpathy-style wiki X, Discord, Gmail are all being ingested into it every few hours This is the knowledge base that will serve as the environment for all of my future loops
English
121
34
1.6K
401.2K
Patrick Debois
Patrick Debois@patrickdebois·
Secret new Location of AIE Europe ? - cc @swyx
Patrick Debois tweet media
Français
1
0
3
897
Basil Chatha
Basil Chatha@realbasilchatha·
@patrickdebois It requires people who understand the nuances of how to implement AI for organizations in a way that works around the rough edges of the tech/business needs!
English
1
0
0
52
Basil Chatha
Basil Chatha@realbasilchatha·
Forward Deployed Engineering is the most critical ingredient for Enterprise AI adoption. It’s why the most important companies on the planet are investing so heavily into it. That’s why we put together the Forward Deployed track at this year’s AI Engineer World’s Fair on Tuesday, June 30. Learn about the current state of the industry and where its headed from the people and companies leading the charge. Everything it REALLY takes to deploy agents in production and transition our economy to the new world order Don’t miss it :) (more details and link in comments) ↓
Basil Chatha tweet media
English
10
5
50
32K
Patrick Debois
Patrick Debois@patrickdebois·
Agent: should I do A or B Me: yes
English
1
0
5
915
Patrick Debois
Patrick Debois@patrickdebois·
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/sch…
Patrick Debois tweet media
English
0
0
4
576
Patrick Debois
Patrick Debois@patrickdebois·
llm= road, coding agent = car, pilot = coder, context = fuel . What else would you add to the metaphor?
Patrick Debois tweet media
English
1
0
5
956
Patrick Debois
Patrick Debois@patrickdebois·
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…
GIF
English
0
0
2
364
swyx
swyx@swyx·
this one is doing v well btw if you want the popular vote filter on the firehose of all the things @patrickdebois was one of the track keynotes i gave a "blank check" to based on his sincere support since our very earliest days + when in europe we must feature the DevOps guy. he didnt disappoint!
swyx tweet media
AI Engineer@aiDotEngineer

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=bSG9wU…

English
7
2
52
8.7K
Veselin Dimitrov
Veselin Dimitrov@vidimitrov·
it’s not that they want to write docs, we both know that docs drift fast… what they really want is to: - stop repeating themselves (reconstruct intent each new session) - talk to an agent that is fluent in their context and recalls historical decisions - get consistent results that belong with their codebase (conventions) - trust the outcome (verification procedures) - keep only persistent context that cannot be recreated from reading the code - share the same experience with their team the packages approach is good but it doesn’t cover the full spectrum of context types
English
1
0
1
33
Veselin Dimitrov
Veselin Dimitrov@vidimitrov·
agree on the "rigor", but "context is the new code" isn't quite right what @patrickdebois describes was always part of code creation - lived in our heads and scattered docs, just never captured its not new - we need the right taxonomy to define it and a way to materialise it reliably
AI Engineer@aiDotEngineer

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=bSG9wU…

English
1
0
1
226
Patrick Debois
Patrick Debois@patrickdebois·
@buildsafter5 @swyx agree on the tdd. But the non-determism makes it feel more like error-budget and risk mitigation vs full testing
English
1
0
0
43
Jonas Vetterle
Jonas Vetterle@jvetterle·
@aiDotEngineer @patrickdebois basically context is the only AI dev artifact that compounds. Models commoditize, workflows shift, frameworks rot but the context graph (rules, examples, constraints, learned-from-failure) gets more valuable over time.. everything else is rented.
English
2
0
2
56
Patrick Debois retweetledi
AI Engineer
AI Engineer@aiDotEngineer·
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=bSG9wU…
YouTube video
YouTube
AI Engineer tweet media
English
14
34
283
22.4K
Alex Carmichael
Alex Carmichael@ai_carmichael·
@aiDotEngineer @patrickdebois Agreed. the gap I keep hitting is that context has no ownership model: no versioning, no diff, no rollback when an agent starts drifting because something upstream changed silently.
English
1
0
1
27
Fatih Aydin, MSc.
Fatih Aydin, MSc.@fatihaydindev·
thoughts on context management. Better knowledge = better context management. I'm calling this the triadic hermeneutic loop, building on the classical hermeneutic circle from philosophy (Schleiermacher, Gadamer) and extending it with a third actor: the AI. The main problem isn't model capability; it's informatics. We need structured know-how, shared context, and a maintainable lifecycle [@patrickdebois 's CDLC]. Humans in the loop, i mean, the actual agent (in the philosophical sense) is the human: the one who learns new things, reflects them back into the context, and externalizes knowledge into shared structure. The AI agent executes; the human agent understands.
Fatih Aydin, MSc. tweet media
English
1
0
0
316
Patrick Debois
Patrick Debois@patrickdebois·
@swyx Appreciate the trust you put in me. Keep pushing the industry!
English
0
0
2
240