<?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: Why is programming so hard?</title>
	<atom:link href="http://priscimon.com/blog/2007/10/18/why-is-programming-so-hard/feed/" rel="self" type="application/rss+xml" />
	<link>http://priscimon.com/blog/2007/10/18/why-is-programming-so-hard/</link>
	<description>Blogs killed the e-mail star.</description>
	<pubDate>Wed, 20 Aug 2008 10:36:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Eddy</title>
		<link>http://priscimon.com/blog/2007/10/18/why-is-programming-so-hard/#comment-116187</link>
		<dc:creator>Eddy</dc:creator>
		<pubDate>Sun, 21 Oct 2007 08:08:30 +0000</pubDate>
		<guid isPermaLink="false">http://priscimon.com/blog/2007/10/18/why-is-programming-so-hard/#comment-116187</guid>
		<description>Interesting, indeed.

The "double-hump distribution" blows away the theory that there are only those who get it and those who don't.

--Eddy</description>
		<content:encoded><![CDATA[<p>Interesting, indeed.</p>
<p>The &#8220;double-hump distribution&#8221; blows away the theory that there are only those who get it and those who don&#8217;t.</p>
<p>&#8211;Eddy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Avinash Meetoo</title>
		<link>http://priscimon.com/blog/2007/10/18/why-is-programming-so-hard/#comment-115917</link>
		<dc:creator>Avinash Meetoo</dc:creator>
		<pubDate>Sat, 20 Oct 2007 22:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://priscimon.com/blog/2007/10/18/why-is-programming-so-hard/#comment-115917</guid>
		<description>Hi Eddy,

Mark Guzdial writes:

"At our CS Ed Research seminar last week, Brian Dorn suggested another one. It's the specificity of a program, the need for exactness when our natural world allows for ambiguity. Natural language did not evolve to specify video games or algorithms.  Natural language evolved to allow interaction between thinking beings.  Programming languages are about specifying a process to a machine.  Dorn's hypothesis would say that the problem of Commonsense Computing Researchers and John Pane is that what we describe in natural language is necessarily ambiguous, and the process of getting it exactly right for the machine is the hard part."

Now that I've read that, I also believe this is the main reason why programming is hard for most people: programmers have to be 100% precise!

100% precision is something that most people cannot attain. Only those who really think precisely (i.e. like a programmer) find programming easy. The rest struggle.

Incidentally, &lt;a href="http://www.cs.mdx.ac.uk/research/PhDArea/saeed/paper1.pdf" rel="nofollow"&gt;this paper&lt;/a&gt; by Saeed Dehnadi and Richard Bornat, seems to prove that there is a 'double hump' distribution instead of a normal distribution among students learning to program. This seems to imply that some students will never ever learn programming whatever effort the teacher does.</description>
		<content:encoded><![CDATA[<p>Hi Eddy,</p>
<p>Mark Guzdial writes:</p>
<p>&#8220;At our CS Ed Research seminar last week, Brian Dorn suggested another one. It&#8217;s the specificity of a program, the need for exactness when our natural world allows for ambiguity. Natural language did not evolve to specify video games or algorithms.  Natural language evolved to allow interaction between thinking beings.  Programming languages are about specifying a process to a machine.  Dorn&#8217;s hypothesis would say that the problem of Commonsense Computing Researchers and John Pane is that what we describe in natural language is necessarily ambiguous, and the process of getting it exactly right for the machine is the hard part.&#8221;</p>
<p>Now that I&#8217;ve read that, I also believe this is the main reason why programming is hard for most people: programmers have to be 100% precise!</p>
<p>100% precision is something that most people cannot attain. Only those who really think precisely (i.e. like a programmer) find programming easy. The rest struggle.</p>
<p>Incidentally, <a href="http://www.cs.mdx.ac.uk/research/PhDArea/saeed/paper1.pdf" rel="nofollow">this paper</a> by Saeed Dehnadi and Richard Bornat, seems to prove that there is a &#8216;double hump&#8217; distribution instead of a normal distribution among students learning to program. This seems to imply that some students will never ever learn programming whatever effort the teacher does.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Ng</title>
		<link>http://priscimon.com/blog/2007/10/18/why-is-programming-so-hard/#comment-115386</link>
		<dc:creator>Patrick Ng</dc:creator>
		<pubDate>Sat, 20 Oct 2007 01:29:18 +0000</pubDate>
		<guid isPermaLink="false">http://priscimon.com/blog/2007/10/18/why-is-programming-so-hard/#comment-115386</guid>
		<description>This is a very good question. 

Personally, I had a hard time at the beginning when I was learning programming. But, once I "got it" things started to become easier. The programming language definitely played a very important role. 

Some studies (Psychology field) have shown that bilingual people think differently depending in what language they are thinking. For example, Chinese students think in a certain way when they think in English and in a different way when they think in Chinese. I believe this might explain why someone who has not yet mastered a new (programming) language is having difficulties thinking in this same language. 

My belief was strengthened even more when I watched how different users use Crystal Reports, one of the most popular report writing software. Those how have good programming knowledge tend to use Crystal Reports (and Crystal syntax) more efficiently than those who don't, because they cannot think in "Crystal Reports" language. 

Spoken language to programming language is similar to translating from one language to another. Those who know both languages will do a better job than those who don't. 

That being said, I may well be totally wrong, but this has been my observation so far.</description>
		<content:encoded><![CDATA[<p>This is a very good question. </p>
<p>Personally, I had a hard time at the beginning when I was learning programming. But, once I &#8220;got it&#8221; things started to become easier. The programming language definitely played a very important role. </p>
<p>Some studies (Psychology field) have shown that bilingual people think differently depending in what language they are thinking. For example, Chinese students think in a certain way when they think in English and in a different way when they think in Chinese. I believe this might explain why someone who has not yet mastered a new (programming) language is having difficulties thinking in this same language. </p>
<p>My belief was strengthened even more when I watched how different users use Crystal Reports, one of the most popular report writing software. Those how have good programming knowledge tend to use Crystal Reports (and Crystal syntax) more efficiently than those who don&#8217;t, because they cannot think in &#8220;Crystal Reports&#8221; language. </p>
<p>Spoken language to programming language is similar to translating from one language to another. Those who know both languages will do a better job than those who don&#8217;t. </p>
<p>That being said, I may well be totally wrong, but this has been my observation so far.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
