<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Three Lessons on Writing Code, From a Graphic Designer</title>
	<atom:link href="http://www.myintervals.com/blog/2008/03/14/three-lessons-on-writing-code-from-a-graphic-designer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.myintervals.com/blog/2008/03/14/three-lessons-on-writing-code-from-a-graphic-designer/</link>
	<image>
		<link>http://www.myintervals.com</link>
		<url>http://stats.indextools.com/p.pl?a=1000681782912&amp;x=11</url>
	</image>
	<description>Development updates for Web based task, time and project management</description>
	<pubDate>Tue, 07 Oct 2008 04:23:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Three Lessons on Writing Code, From a Graphic Designer / Design Float</title>
		<link>http://www.myintervals.com/blog/2008/03/14/three-lessons-on-writing-code-from-a-graphic-designer/#comment-3893</link>
		<dc:creator>Three Lessons on Writing Code, From a Graphic Designer / Design Float</dc:creator>
		<pubDate>Mon, 21 Jul 2008 23:20:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.myintervals.com/blog/2008/03/14/three-lessons-on-writing-code-from-a-graphic-designer/#comment-3893</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] Three Lessons on Writing Code, From a Graphic Designer   Posted by   johnjreeve  &#124;&#160;Profile &#124;   129 Days Ago  &#124; Category: Programming       When writing code â€” HTML, CSS, PHP, Javascript, or whatever â€” it is important to remember that yourself and others will read and interpret that code again at some point. In addition to being free of syntax errors and bugs, your code needs to be human readable. Here are three fundamental graphic design principals that we can apply to writing code for web sites.        Discuss&#160;&#160;&#124;&#160;   &#160;Share   &#160;&#124;&#160;&#160;Sink      Comments Who Floated Related Links     var cb = Math.random(); var d = document; d.write(''); d.write(''); [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://dev.wp-plugins.org/wiki/Kramer"><img src="http://www.myintervals.com/blog/wp-content/plugins/kramer.php?kramer=gif-icon" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" /></a>[...] Three Lessons on Writing Code, From a Graphic Designer   Posted by   johnjreeve  |&nbsp;Profile |   129 Days Ago  | Category: Programming       When writing code â€” HTML, CSS, PHP, Javascript, or whatever â€” it is important to remember that yourself and others will read and interpret that code again at some point. In addition to being free of syntax errors and bugs, your code needs to be human readable. Here are three fundamental graphic design principals that we can apply to writing code for web sites.        Discuss&nbsp;&nbsp;|&nbsp;   &nbsp;Share   &nbsp;|&nbsp;&nbsp;Sink      Comments Who Floated Related Links     var cb = Math.random(); var d = document; d.write(&#8221;); d.write(&#8221;); [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Reeve</title>
		<link>http://www.myintervals.com/blog/2008/03/14/three-lessons-on-writing-code-from-a-graphic-designer/#comment-3214</link>
		<dc:creator>John Reeve</dc:creator>
		<pubDate>Sat, 15 Mar 2008 20:30:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.myintervals.com/blog/2008/03/14/three-lessons-on-writing-code-from-a-graphic-designer/#comment-3214</guid>
		<description>Good point on the indents. I thought I'd caught that. Wordpress isn't very good at code formatting. 

I have a minor in computer science and a bachelors in graphic design, but work primarily as a programmer now. So yeah, I am trying to tell developers how to do their jobs. You'd be surprised how many developers don't pay attention to the style of their code. Lift the hood on a few open source web apps and you'll see what I mean.

Vim is okay for minor edits and has saved me a few times when I needed to edit files quickly. Most of the web apps we build are not complex enough to warrant viewports, placemarks, or folding. We do rely heavily on regular expressions, but i'm still convinced they are voodoo.</description>
		<content:encoded><![CDATA[<p>Good point on the indents. I thought I&#8217;d caught that. Wordpress isn&#8217;t very good at code formatting. </p>
<p>I have a minor in computer science and a bachelors in graphic design, but work primarily as a programmer now. So yeah, I am trying to tell developers how to do their jobs. You&#8217;d be surprised how many developers don&#8217;t pay attention to the style of their code. Lift the hood on a few open source web apps and you&#8217;ll see what I mean.</p>
<p>Vim is okay for minor edits and has saved me a few times when I needed to edit files quickly. Most of the web apps we build are not complex enough to warrant viewports, placemarks, or folding. We do rely heavily on regular expressions, but i&#8217;m still convinced they are voodoo.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Cornelius</title>
		<link>http://www.myintervals.com/blog/2008/03/14/three-lessons-on-writing-code-from-a-graphic-designer/#comment-3213</link>
		<dc:creator>Rob Cornelius</dc:creator>
		<pubDate>Sat, 15 Mar 2008 17:45:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.myintervals.com/blog/2008/03/14/three-lessons-on-writing-code-from-a-graphic-designer/#comment-3213</guid>
		<description>I know a few developers write code that no one can follow but these tips are kinda useless.

If your a designer thats trying to tell developers how to do their job really its not necessary. Nearly all developers care a great deal about the style of their code. Your not a developer if you haven't been in an argument on whether to but the { on the next line or the same one.

In your first example you don't indent the lines of code within the if { } else {} blocks. Practically every developers style guide for writing code ever says this is one of the key things to do.

Most developers have moved beyond using vi or emacs. In any case both of them can do all you suggest here and more things that you probably have never dreamed of like viewports, placemarks, folding and regular expressions. Emacs and vi make most "modern" editors look sparse. The lack of pretty buttons to point and click mean most people will never see these features and sadly never use them.


PS. I still use vi (well vim) its the best editor bar none and the years I have invested in learning it pay off every day.</description>
		<content:encoded><![CDATA[<p>I know a few developers write code that no one can follow but these tips are kinda useless.</p>
<p>If your a designer thats trying to tell developers how to do their job really its not necessary. Nearly all developers care a great deal about the style of their code. Your not a developer if you haven&#8217;t been in an argument on whether to but the { on the next line or the same one.</p>
<p>In your first example you don&#8217;t indent the lines of code within the if { } else {} blocks. Practically every developers style guide for writing code ever says this is one of the key things to do.</p>
<p>Most developers have moved beyond using vi or emacs. In any case both of them can do all you suggest here and more things that you probably have never dreamed of like viewports, placemarks, folding and regular expressions. Emacs and vi make most &#8220;modern&#8221; editors look sparse. The lack of pretty buttons to point and click mean most people will never see these features and sadly never use them.</p>
<p>PS. I still use vi (well vim) its the best editor bar none and the years I have invested in learning it pay off every day.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
