<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Creativity Craftsmanship Orthodoxy on mugsy.io</title><link>https://mugsy.io/tags/creativity-craftsmanship-orthodoxy/</link><description>Recent content in Creativity Craftsmanship Orthodoxy on mugsy.io</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright Jason Musgrave 2013-2026</copyright><lastBuildDate>Sun, 15 Dec 2013 17:04:59 +0000</lastBuildDate><atom:link href="https://mugsy.io/tags/creativity-craftsmanship-orthodoxy/index.xml" rel="self" type="application/rss+xml"/><item><title>Craftsmanship and Contempt</title><link>https://mugsy.io/2013/12/15/2013-12-15-craftsmanship-and-contempt/</link><pubDate>Sun, 15 Dec 2013 17:04:59 +0000</pubDate><guid>https://mugsy.io/2013/12/15/2013-12-15-craftsmanship-and-contempt/</guid><description>&lt;p&gt;I came across &lt;a href="http://jeffnolan.com/wp/2013/11/27/silicon-valley-doesnt-want-dcs-system/"&gt;Jeff Nolan’s post about Silicon Valley and DC&lt;/a&gt;. I loved it for a lot of reasons. It captures what’s wrong. While the valley values marketing, DC values marketing without anything to back it up. In the valley, the narrative is how you make the sale, but things have to work. In DC, only the narritive is important and the solution/engineering doesn’t just come last, it is something contemptuous that the “leadership” doesn’t want to get on them.&#10;I’m not saying something partisan here. Read the &lt;a href="http://www.shirky.com/weblog/2013/11/healthcare-gov-and-the-gulf-between-planning-and-reality/"&gt;Clay Shirky post&lt;/a&gt; Jeff references. &lt;a href="#fn:1" title="see footnote"&gt;[1]&lt;/a&gt; This is the section that caught my eye, because I’ve seen it many times.&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;The thing that made this meeting unusual was that one of their programmers had been invited to attend, so management could outline their web strategy to him. After the executives thanked me for explaining what I’d learned from log files given me by their own employees just days before, the programmer leaned forward and said “You know, we have all that information downstairs, but nobody’s ever asked us for it.”&lt;/p&gt;&#10;&lt;p&gt;I remember thinking “Oh, finally!” I figured the executives would be relieved this information was in-house, delighted that their own people were on it, maybe even mad at me for charging an exorbitant markup on local knowledge. Then I saw the look on their faces as they considered the programmer’s offer. The look wasn’t delight, or even relief, but contempt. The situation suddenly came clear: I was getting paid to save management from the distasteful act of listening to their own employees.&#10;– &lt;cite&gt;Clay Shirky&lt;/cite&gt;&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;While at &lt;a href="http://newrelic.com/"&gt;New Relic&lt;/a&gt;, it’s &lt;a href="http://blog.newrelic.com/2013/11/06/lew-on-dan-benjamins-quit/"&gt;common&lt;/a&gt; that &lt;a href="https://twitter.com/sweetlew"&gt;Ceo Lew Cirne &lt;/a&gt; &lt;a href="https://twitter.com/sweetlew/status/240198481527054336"&gt;pair programs with his employees.&lt;/a&gt; So, in one kind of organization, the organization’s leadership has contempt for its day to day employees. The other embraces their values and tries to learn from them. Guess which one is more agile, produces better results, and has any grasp on reality.&lt;/p&gt;</description></item></channel></rss>