<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Planning &amp; Design on 💻✨ AI for Coding</title><link>https://kjetiljd.github.io/ai-for-coding/categories/planning--design/</link><description>Recent content in Planning &amp; Design on 💻✨ AI for Coding</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kjetiljd.github.io/ai-for-coding/categories/planning--design/index.xml" rel="self" type="application/rss+xml"/><item><title>Tip #36: Get grilled by the inverse rubber duck</title><link>https://kjetiljd.github.io/ai-for-coding/tips/036-get-grilled-by-the-inverse-rubber-duck/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/036-get-grilled-by-the-inverse-rubber-duck/</guid><description>Before coding, have the agent interview you about the plan. The inverse rubber duck asks the hard questions — surfacing gaps and assumptions when they&amp;rsquo;re cheap to fix.</description></item></channel></rss>