<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tdd on pavsaund.com</title><link>https://www.pavsaund.com/tags/tdd/</link><description>Recent content in Tdd on pavsaund.com</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 04 Feb 2016 00:29:09 +0000</lastBuildDate><atom:link href="https://www.pavsaund.com/tags/tdd/index.xml" rel="self" type="application/rss+xml"/><item><title>Making the right thing work before making it work right</title><link>https://www.pavsaund.com/2016/02/04/making-the-right-thing-work-before-making-it-work-right/</link><pubDate>Thu, 04 Feb 2016 00:29:09 +0000</pubDate><guid>https://www.pavsaund.com/2016/02/04/making-the-right-thing-work-before-making-it-work-right/</guid><description>&lt;p&gt;I&amp;rsquo;ve been a SOLID&lt;sup&gt;&lt;a href=&#34;#reference-1&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; fan of TDD over many years and have spent a lot of time drilling myself in writing tests first to drive applications forward. I truly believe I have been at a place where my &lt;a href=&#34;http://blog.8thlight.com/uncle-bob/2012/01/11/Flipping-the-Bit.html&#34; target=&#34;_blank&#34;&gt;BIT has been FLIPPED&lt;/a&gt;. There are occasions though when attempting to write tests first have just been hard and completing a feature with test-first has been a record in will power and what felt like an eternity to deliver a feature. But if it was easy then everyone would be doing it.&lt;/p&gt;</description></item><item><title>The boy scout rule</title><link>https://www.pavsaund.com/2014/10/26/the-boy-scout-rule/</link><pubDate>Sun, 26 Oct 2014 18:00:21 +0000</pubDate><guid>https://www.pavsaund.com/2014/10/26/the-boy-scout-rule/</guid><description>&lt;p&gt;Recently I had the discussion with a colleague on how new code was being added to a code-base without maintainability in mind. The discussion was sparked by a code-review that had been ping-ponging between the reviewer and the developer where readability and ( as a result ) maintainability was an issue.&lt;/p&gt;</description></item><item><title>Acceptance driven bugfixing</title><link>https://www.pavsaund.com/2014/10/26/acceptance-driven-bugfixing/</link><pubDate>Sun, 26 Oct 2014 16:56:31 +0000</pubDate><guid>https://www.pavsaund.com/2014/10/26/acceptance-driven-bugfixing/</guid><description>&lt;p&gt;&lt;em&gt;I originally posted this on &lt;a title=&#34;Acceptance driven bugfixing&#34; href=&#34;http://blog.dolittle.com/2013/06/04/acceptance-driven-bugfixing/&#34;&gt;the dolittle blog&lt;/a&gt;&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;There&amp;rsquo;s a new task waiting for you in your inbox&amp;hellip; a &lt;strong&gt;bug&lt;/strong&gt; in production! Maybe the bug is completely unrelated to  code, you&amp;rsquo;ve created, but the report is there waiting for you. It&amp;rsquo;s critical, and has to be fixed &amp;ldquo;today&amp;rdquo; or &amp;ldquo;ASAP&amp;rdquo;! And with a number of consequences, like &amp;ldquo;this feature is vital!&amp;rdquo;, &amp;ldquo;support center is being called down by angry customers&amp;rdquo;, &amp;ldquo;we&amp;rsquo;re losing millions!&amp;rdquo;.&lt;/p&gt;</description></item></channel></rss>