<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tutorial on Patrick Dahlke</title><link>https://patrickdahlke.com/tags/tutorial/</link><description>Recent content in Tutorial on Patrick Dahlke</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 27 Apr 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://patrickdahlke.com/tags/tutorial/index.xml" rel="self" type="application/rss+xml"/><item><title>Spec-Driven Development, but the Specs Are a Graph</title><link>https://patrickdahlke.com/posts/agentclinic/</link><pubDate>Mon, 27 Apr 2026 10:00:00 +0200</pubDate><guid>https://patrickdahlke.com/posts/agentclinic/</guid><description>DeepLearning.AI and JetBrains run a good course on spec-driven development. Paul Everitt teaches it. You write a constitution, then a spec, then code. The discipline is the point, and the discipline travels.
What doesn&amp;rsquo;t travel is the substrate. The course uses markdown. Markdown is fine for a tutorial, but the second you put it in front of a real project — agents propagating changes across requirements, specs, code, tests, variants — you hit the wall I wrote about in The 6x Tax.</description></item></channel></rss>