<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>0xDECAFBAD - Tag: style</title>
    <link href="http://decafbad.com/blog/atom.xml" rel="self"/>
    <link href="http://decafbad.com/blog"/>
    <updated>2011-11-16T16:29:50+00:00</updated>
    <id></id>
    <author>
        <name></name>
        <email>l.m.orchard@pobox.com</email>
    </author>
    

    <entry>
        <title>Beautiful Code</title>
        <link href="http://decafbad.com/blog/2007/10/10/beautiful-code"/>
        <updated>2007-10-10T03:59:02+00:00</updated>
        <id>http://decafbad.com/blog/2007/10/10/beautiful-code</id>
        <content type="html">&lt;p&gt;&lt;a href=&quot;http://michael-mccracken.net/wp/2007/10/09/the-editing-pass/&quot;&gt;Michael McCracken&lt;/a&gt;: &quot;&lt;i&gt;Once you get a piece of code to the point where you believe it works - it's passing its tests - go back over it and edit it. That is, go back and edit it for clarity, flow, and style. Just as if it were an essay.&lt;/i&gt;&quot;&lt;/p&gt;


&lt;p&gt;This is something I just don't hear enough of - code as writing, code as communication.  While I don't always make time to polish as much as I'd like, I'm always thinking about things like narrative and flow of a file of source code as well as the aesthetic shape and form of the code.  Code is fiction, code is poetry.&lt;/p&gt;


&lt;p&gt;Compilation free of syntax and parse errors is baseline competence - and sometimes just good luck.  Apparent correct operation is not good enough: Moving on before the code has beauty is a poverty.  Ugly code kills motivation and comprehension - which attracts bugs and induces a downward spiral in morale.&lt;/p&gt;


&lt;p&gt;Unit tests clear the way for courage and bravery; beauty yields living code worth fighting for.&lt;/p&gt;

</content>
    </entry>
    
    
</feed>

