<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>schristoph.online</title><link>https://schristoph.online/tags/devops/</link><description>Personal homepage and blog of Stefan Christoph</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>Stefan Christoph. All rights reserved.</copyright><lastBuildDate>Fri, 29 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://schristoph.online/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Context Engineering: The Skill That Replaced Prompt Engineering</title><link>https://schristoph.online/blog/context-engineering-replaced-prompt-engineering/?utm=rss-feed</link><pubDate>Fri, 29 May 2026 00:00:00 +0000</pubDate><guid>https://schristoph.online/blog/context-engineering-replaced-prompt-engineering/</guid><description>&lt;blockquote>
&lt;p>&lt;strong>TL;DR:&lt;/strong> Patrick Debois coined DevOps in 2009 by naming what practitioners were already doing. In 2026, he&amp;rsquo;s doing it again with &amp;ldquo;Context Engineering&amp;rdquo; and the CDLC (Context Development Lifecycle): Generate, Evaluate, Distribute, Observe. The core insight: as coding agents get more capable, the bottleneck shifts from writing code to assembling the right context. More context isn&amp;rsquo;t better — more &lt;em>precise&lt;/em> context is. Teams that treat context as a versioned, tested, governed engineering artifact will compound an advantage that&amp;rsquo;s hard to replicate.&lt;/p></description></item></channel></rss>