<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Intro to Programming</title>
	<atom:link href="http://www.designbycandlelight.com/intro-programming/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designbycandlelight.com/intro-programming/</link>
	<description>User Experience Design, even in the wee hours!</description>
	<lastBuildDate>Tue, 27 Jul 2010 03:19:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adam</title>
		<link>http://www.designbycandlelight.com/intro-programming/comment-page-1/#comment-494</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Fri, 05 Feb 2010 11:58:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.designbycandlelight.com/?p=208#comment-494</guid>
		<description>Learning how to program basically requires the user to bend their brain around something totally new. This isn&#039;t a trivial action. The hardest thing to wrap your brain around isn&#039;t really the latter stuff, but your first few weeks/months of coding. 

The way I got over that barrier to entry was to consider each line of code as conversation. That is, I treated each line of code as a specific line in a conversation. 

A lot of languages have a lot of bloat involved that only makes sense after you&#039;re a beginner. That&#039;s unfortunate, because it only makes it harder. 

As such, I found that talking out what I want the program to do made it much easier for me to conceptualize what I needed to do. 

if (something) then do thisThing; 
else doSomethingElse;

while(thisThingIsTrue) doSomething; 

Function/Method calls are a little tricky at first, but really they are short hand for a bunch of code. So, you could have: 

boolean someFunction() {
    if (something) return true;
    else return false;
}

if (someFunction()) doSomething; 
else doSomethingElse;

Method calls within objects are just an extension of that. Let&#039;s say we have a Pirate class that has the function someFunction(). 

Pirate{
    boolean someFunction() {
        if(something) return true;
        else return false;
    }
}

Then we could say something like: 
Pirate p = new Pirate(); //I just created a new Pirate. 

if (p.someFunction()) doSomething;
else doSomethingElse;
}</description>
		<content:encoded><![CDATA[<p>Learning how to program basically requires the user to bend their brain around something totally new. This isn&#8217;t a trivial action. The hardest thing to wrap your brain around isn&#8217;t really the latter stuff, but your first few weeks/months of coding. </p>
<p>The way I got over that barrier to entry was to consider each line of code as conversation. That is, I treated each line of code as a specific line in a conversation. </p>
<p>A lot of languages have a lot of bloat involved that only makes sense after you&#8217;re a beginner. That&#8217;s unfortunate, because it only makes it harder. </p>
<p>As such, I found that talking out what I want the program to do made it much easier for me to conceptualize what I needed to do. </p>
<p>if (something) then do thisThing;<br />
else doSomethingElse;</p>
<p>while(thisThingIsTrue) doSomething; </p>
<p>Function/Method calls are a little tricky at first, but really they are short hand for a bunch of code. So, you could have: </p>
<p>boolean someFunction() {<br />
    if (something) return true;<br />
    else return false;<br />
}</p>
<p>if (someFunction()) doSomething;<br />
else doSomethingElse;</p>
<p>Method calls within objects are just an extension of that. Let&#8217;s say we have a Pirate class that has the function someFunction(). </p>
<p>Pirate{<br />
    boolean someFunction() {<br />
        if(something) return true;<br />
        else return false;<br />
    }<br />
}</p>
<p>Then we could say something like:<br />
Pirate p = new Pirate(); //I just created a new Pirate. </p>
<p>if (p.someFunction()) doSomething;<br />
else doSomethingElse;<br />
}</p>
]]></content:encoded>
	</item>
</channel>
</rss>
