<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Hackers, Legible Code, Typing, and the Zone</title>
	<link>http://blog.go4teams.com/archives/hackers-legible-code-typing-and-the-zone/28</link>
	<description>What I Read; What I Have Read; and stuff I pick up and drag along</description>
	<pubDate>Fri, 30 Jul 2010 18:30:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: Dave Jellison</title>
		<link>http://blog.go4teams.com/archives/hackers-legible-code-typing-and-the-zone/28#comment-36897</link>
		<pubDate>Sat, 07 Jul 2007 16:56:12 +0000</pubDate>
		<guid>http://blog.go4teams.com/archives/hackers-legible-code-typing-and-the-zone/28#comment-36897</guid>
					<description>Hello Daniel,

I'm doing research for an article I am writing for CodeProject and possibly other software development websites. The article is titled &quot;Writing Legible Code&quot;. 

I came across your blog while researching ideas and references and would like to quote you and, of course, reference your blog as said reference. What I would like to reference is your quote about your colleague because I think it embodies the type of mentality I am trying to rebut in my article. (very funny by the way). The other strong point is writing code for humans vs. machines.

I've been writing the article for about a week or so now. Not so much because it's time consuming but to analyze my own code writing and add to the article ideas that come through my practice. I take it for granted (rarely anymore) that people write code for people not machines. 

If you have the time or inclination I would be willing to submit the content of the article to you for review. All ideas are welcome. 

The purpose of the article is to make developers aware that they can utilize the tools provided to create code that reads like a book. Even someone without software development skills should be able to be given a printout of a small method and be able to, through common sense, give you an idea of what the code is supposed to do.

Great blog and article.

Thanks,
Dave Jellison</description>
		<content:encoded><![CDATA[<p>Hello Daniel,</p>
<p>I&#8217;m doing research for an article I am writing for CodeProject and possibly other software development websites. The article is titled &#8220;Writing Legible Code&#8221;. </p>
<p>I came across your blog while researching ideas and references and would like to quote you and, of course, reference your blog as said reference. What I would like to reference is your quote about your colleague because I think it embodies the type of mentality I am trying to rebut in my article. (very funny by the way). The other strong point is writing code for humans vs. machines.</p>
<p>I&#8217;ve been writing the article for about a week or so now. Not so much because it&#8217;s time consuming but to analyze my own code writing and add to the article ideas that come through my practice. I take it for granted (rarely anymore) that people write code for people not machines. </p>
<p>If you have the time or inclination I would be willing to submit the content of the article to you for review. All ideas are welcome. </p>
<p>The purpose of the article is to make developers aware that they can utilize the tools provided to create code that reads like a book. Even someone without software development skills should be able to be given a printout of a small method and be able to, through common sense, give you an idea of what the code is supposed to do.</p>
<p>Great blog and article.</p>
<p>Thanks,<br />
Dave Jellison
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: DRM - Daniel&#8217;s Random Mutterings &#187; &#187; Paul Graham - LISP fanboy extraordinaire</title>
		<link>http://blog.go4teams.com/archives/hackers-legible-code-typing-and-the-zone/28#comment-25</link>
		<pubDate>Sun, 28 May 2006 16:15:32 +0000</pubDate>
		<guid>http://blog.go4teams.com/archives/hackers-legible-code-typing-and-the-zone/28#comment-25</guid>
					<description>[...] Anyway, I finally managed to finish Paul Graham&amp;#8217;s &amp;#8220;Hackers and Painters&amp;#8220;. After really enjoying the first two or three chapters (see my previous post), I found finishing this book quite a chore and on the whole found it quite a let-down. At the end, I&amp;#8217;m not sure what I&amp;#8217;ve learned. Except that Paul enjoys LISP. That&amp;#8217;s what I found the most painful and booooooringgggg: Advanced LISP fanboy-hood (is that a word? If not, I&amp;#8217;ve got copyright). [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Anyway, I finally managed to finish Paul Graham&#8217;s &#8220;Hackers and Painters&#8220;. After really enjoying the first two or three chapters (see my previous post), I found finishing this book quite a chore and on the whole found it quite a let-down. At the end, I&#8217;m not sure what I&#8217;ve learned. Except that Paul enjoys LISP. That&#8217;s what I found the most painful and booooooringgggg: Advanced LISP fanboy-hood (is that a word? If not, I&#8217;ve got copyright). [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
