<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Development Practices on Pocket Dev</title><link>/tags/development-practices/</link><description>Recent content in Development Practices on Pocket Dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 31 May 2025 20:14:24 +0000</lastBuildDate><atom:link href="/tags/development-practices/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Arent Developers Writing Tests?</title><link>/posts/why-arent-developers-writing-unit-tests/</link><pubDate>Sat, 31 May 2025 20:14:24 +0000</pubDate><guid>/posts/why-arent-developers-writing-unit-tests/</guid><description>&lt;h3 id="why-arent-developers-writing-tests-and-how-ai-can-change-that"&gt;Why Aren&amp;rsquo;t Developers Writing Tests? (And How AI Can Change That)&lt;/h3&gt;
&lt;p&gt;After countless refinement sessions, hours of discussions, and collaborative back-and-forth, the PBI lands on your plate. You&amp;rsquo;re eager to dive in. You skim the title, glance at the Acceptance Criteria (AC), and jump straight into the code. The lines flow effortlessly, and by the end of the day, the feature is done. You push it to QA, and the cycle of questions begins:&lt;/p&gt;</description></item></channel></rss>