<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Craftsmanship on pavsaund.com</title><link>https://www.pavsaund.com/tags/craftsmanship/</link><description>Recent content in Craftsmanship on pavsaund.com</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 14 Feb 2016 20:00:14 +0000</lastBuildDate><atom:link href="https://www.pavsaund.com/tags/craftsmanship/index.xml" rel="self" type="application/rss+xml"/><item><title>Starting an empathic journey</title><link>https://www.pavsaund.com/2016/02/14/starting-an-empathic-journey/</link><pubDate>Sun, 14 Feb 2016 20:00:14 +0000</pubDate><guid>https://www.pavsaund.com/2016/02/14/starting-an-empathic-journey/</guid><description>As part of my quest to be exceptional, I&amp;rsquo;ve been searching to discover what I&amp;rsquo;m passionate about as a software developer. I feel a pull in so many directions, but I guess that&amp;rsquo;s natural given our profession and the diversity we&amp;rsquo;re exposed to.
Some people have found their calling and are producing wonderful content that provides tremendous value to others. What I&amp;rsquo;ve been wanting to do is figure out what my special sauce is.</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>