<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>🧾 Templates: Don't Start From a Blank Page on eval ( code )</title><link>https://evalcode.com/handbook/templates/</link><description>Recent content in 🧾 Templates: Don't Start From a Blank Page on eval ( code )</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copy, _right?_ :thinking_face:. All thoughts and opinions are my own. They do not represent my employer.</copyright><atom:link href="https://evalcode.com/handbook/templates/index.xml" rel="self" type="application/rss+xml"/><item><title>🐛 Bug Reports: Make It Reproducible</title><link>https://evalcode.com/handbook/templates/bug-report/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://evalcode.com/handbook/templates/bug-report/</guid><description>A bug report has one job: give someone enough info to reproduce the problem without asking follow-up questions.</description></item><item><title>🔀 Pull Requests: Tell Reviewers What to Look For</title><link>https://evalcode.com/handbook/templates/pull-requests/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://evalcode.com/handbook/templates/pull-requests/</guid><description>A PR description isn&amp;rsquo;t for you. It&amp;rsquo;s for the person reviewing your code. Make their job easy.</description></item><item><title>💡 Feature Proposals: Start With the Problem</title><link>https://evalcode.com/handbook/templates/feature-proposal/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://evalcode.com/handbook/templates/feature-proposal/</guid><description>Force yourself to articulate the problem before jumping to a solution. The proposal starts with the problem.</description></item><item><title>📋 Stories: The Building Block of Delivery</title><link>https://evalcode.com/handbook/templates/story/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://evalcode.com/handbook/templates/story/</guid><description>The fundamental unit of work on the board. What the team is building, why it matters, and how to verify it&amp;rsquo;s done.</description></item></channel></rss>