<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Programming on Aaron West's technology blog</title><link>https://www.aaronwest.net/tags/programming/</link><description>Recent content in Programming on Aaron West's technology blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 14 Oct 2011 10:55:00 -0600</lastBuildDate><atom:link href="https://www.aaronwest.net/tags/programming/index.xml" rel="self" type="application/rss+xml"/><item><title>It's Working for Me</title><link>https://www.aaronwest.net/blog/its-working-for-me/</link><pubDate>Fri, 14 Oct 2011 10:55:00 -0600</pubDate><guid>https://www.aaronwest.net/blog/its-working-for-me/</guid><description>&lt;p&gt;One of the worst things you can ever say as a developer/programmer is &amp;ldquo;It&amp;rsquo;s working for me.&amp;rdquo; Unless of course that is immediately followed by &amp;ldquo;..but let&amp;rsquo;s dig in and figure out why it isn&amp;rsquo;t working for you.&amp;rdquo; This type of thinking is a cancer within development teams and certainly isn&amp;rsquo;t customer focused. Software breaks, apps don&amp;rsquo;t work properly, and if you&amp;rsquo;re a developer it&amp;rsquo;s your responsibility to do whatever it takes to resolve your customer issues. A few years ago one of my dev teams was having tremendous difficulty replicating a customer-reported issue. One of the developers started the whole &amp;ldquo;It&amp;rsquo;s working for me&amp;rdquo; thing and my manager heard it. He jumped in and quickly asked my developer if he was going to package up his computer and ship it to the customer. What a great response.&lt;/p&gt;</description></item></channel></rss>