Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

DevOps Paradox

DevOps Paradox artwork

DOP 350: Context Is the New Bottleneck, Not Code

May 13, 202649 minAudio
ShareXLinkedInFacebookWhatsAppEmail

#350: The bottleneck used to be writing the code. Now it is feeding the agent enough context to write the right code. That is Patrick Debois' argument, and given that Patrick coined the term DevOps, it is worth paying attention when he says the discipline is shifting again. The model does not matter. The IDE does not matter. What matters is whether your team can capture the way you actually work and hand it to an agent that does not know any of it. The promise was that AI would let us ship without writing specs. The reality is the opposite. If you want decent output, you need richer specs, more docs, and a way to feed the agent what is unique about your team and your codebase. Viktor admits he stopped writing specs himself. He talks to the agent until he is satisfied, then says write it down. The work did not go away. It moved. A second agent that validates your work tends to take the original spec too seriously and miss what is not there. The interesting validation is not whether the code matches the spec. It is whether the spec matches reality. Patrick's response is harness engineering -- combining verifier agents with deterministic tooling like linters and tests, and mining conversation logs for the moments a user says this is wrong so the missing context can be saved and reused. Memory, hooks, skills, registries -- all just delivery mechanisms for the same underlying thing. Patrick's number one piece of advice if you are starting today is brutal in its simplicity. When the agent does the wrong thing, write it down in your AGENTS.md or claude.md. Do not just re-prompt and move on. Build the context file. That is the new job. Code moved to context. Context, eventually, moves to knowledge -- the way your organization actually works, captured somewhere an agent can use it. Whoever owns that layer wins. The model does not. Patrick's contact information: LinkedIn: https://www.linkedin.com/in/patrickdebois/ X: https://x.com/patrickdebois YouTube channel: https://youtube.com/devopsparadox Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/ Slack: https://www.devopsparadox.com/slack/ Connect with us at: https://www.devopsparadox.com/contact/

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. DOP 377: KubeCon North America 2026 Review

    Nov 18, 202637 minAudio

    #377: Every software company that ever thought about sponsoring KubeCon already sponsors KubeCon. So where does it grow from here? Ask what on the expo floor wasn't AI, and you get two answers: the coffee and the puppy...

    Credit the people on this episode

  2. DOP 376: Secrets Management for AI Agents

    Nov 11, 202641 minAudio

    #376: How many secrets can your coding agent reach right now? You gave it a token so it could get work done. It might have passed that token to every agent it spun up. Somewhere along the way, you stopped reading the...

    Credit the people on this episode

  3. DOP 375: AI Writes the Code. Who Understands It?

    Nov 4, 202649 minAudio

    #375: An agent can crank out 200 or 300 lines of code a minute. You can maybe review 40. So who's actually supposed to understand what just got merged? Maybe nobody ever did. Did you really read every line of every PR...

    Credit the people on this episode

  4. DOP 374: Does AI Make Companies More Productive?

    Oct 28, 202656 minAudio

    #374: Your company is paying for the AI licenses, and now there's a number attached. Two to three times the output, every day, or else. Can you hit it? If they're counting lines of code, sure. But you aren't the...

    Credit the people on this episode

  5. DOP 373: Are Layoffs Really Because of AI?

    Oct 21, 202645 minAudio

    #373: A company lays off 4,000 people the same day it posts record revenue, and the stock jumps. Is that really because of AI? Or just a really good press release? Layoffs used to mean a company was bleeding cash. Now...

    Credit the people on this episode