<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Live &#38; Code &#187; The Human Computer</title>
	<atom:link href="http://www.liveandcode.com/tag/the-human-computer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.liveandcode.com</link>
	<description>Enrico on programming, living, and everything in between</description>
	<lastBuildDate>Fri, 07 May 2010 13:00:17 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Writing is Human Persistence</title>
		<link>http://www.liveandcode.com/2010/01/29/writing-is-human-persistence/</link>
		<comments>http://www.liveandcode.com/2010/01/29/writing-is-human-persistence/#comments</comments>
		<pubDate>Sat, 30 Jan 2010 00:51:07 +0000</pubDate>
		<dc:creator>Enrico</dc:creator>
				<category><![CDATA[Personal Development]]></category>
		<category><![CDATA[creativity]]></category>
		<category><![CDATA[memory]]></category>
		<category><![CDATA[The Human Computer]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.liveandcode.com/?p=358</guid>
		<description><![CDATA[One of many tips for improving one&#8217;s creativity is to keep a notebook available to write down ideas as you get them. The rationale behind this is that if you don&#8217;t have something to record your idea in the moment you get it, you might forget it by the time you do have something to [...]]]></description>
			<content:encoded><![CDATA[<p>One of many tips for improving one&#8217;s creativity is to keep a notebook available to write down ideas as you get them. The rationale behind this is that if you don&#8217;t have something to record your idea in the moment you get it, you might forget it by the time you do have something to write it down on. It occurs to me that this might be another sense in which we are similar to computers.</p>
<p><span id="more-358"></span><br />
<a href="http://en.wikipedia.org/wiki/Random-access_memory" title="Random-access memory - Wikipedia">RAM</a> holds the current information that a program is working with, but it doesn&#8217;t hold on to it forever. Once the program has exited, the RAM it was using is (ideally) reclaimed by the operating system for use by other programs. If a program needs to keep information for the next time it executes, it will get written to the hard drive or to another form of <em><a href="http://en.wikipedia.org/wiki/Persistence_(computer_science)" title="Persistence (computer science) - Wikipedia">persistence</a></em>.</p>
<p>I imagine short-term memory as being very similar to RAM. The thoughts are in your head, but they aren&#8217;t going to stay there forever. Even long-term memory is not entirely reliable; <a href="http://www.telegraph.co.uk/technology/3778272/The-perils-of-relying-on-memory-in-court.html" title="The perils of relying on memory in court - Telegraph.co.uk">the act of recalling something changes it slightly</a>. So if our memory isn&#8217;t the best place to keep ideas for later, where should we keep them? <strong>In writing.</strong></p>
<p>The act of reading words doesn&#8217;t change them. The letters which were printed may become illegible but they will never change. The information that those written words encode persists, and is the same every time you read it. The written word is how we have aggregated the collective information of our entire species with the accuracy and efficiency that we needed to make our social and technological advances.</p>
<p>One of my goals for 2010 is to write more things down and stop trying to keep so much in my head.</p>
<p>I&#8217;ll close this brief thought by quoting a <a href="http://www.petermichaud.com/essays/the-secret-about-writing-that-no-one-has-the-balls-to-tell-you/" title="The secret about writing that no one has the balls to tell you - Pete Michaud">blog post</a> I read recently about writing:</p>
<blockquote><p>
The amount of information our brains can fit into our short term memory at once isn’t a lot. If you never have thoughts that require notes, then all your thoughts are small or unoriginal enough to fit into your tiny short term memory.</p>
<p>Writing allows you to record your short term memory into a format that you can examine and reflect upon, so you can suss out what makes sense, and how it makes sense, and then expand on the original seed. When you expand your thought all the way into a piece of coherent writing, it becomes complete. It would have been impossible for you to have that size of a thought without writing–your brain just isn’t powerful enough.
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.liveandcode.com/2010/01/29/writing-is-human-persistence/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Context Switching</title>
		<link>http://www.liveandcode.com/2010/01/11/context-switching/</link>
		<comments>http://www.liveandcode.com/2010/01/11/context-switching/#comments</comments>
		<pubDate>Tue, 12 Jan 2010 02:57:37 +0000</pubDate>
		<dc:creator>Enrico</dc:creator>
				<category><![CDATA[Miscellaneous]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[The Human Computer]]></category>

		<guid isPermaLink="false">http://www.liveandcode.com/?p=337</guid>
		<description><![CDATA[One of the reasons this blog is called &#8220;Live &#38; Code&#8221; is because Computer Science (and by extension programming) is one of the lenses through which I view the world. There are often parallels between the way we think and the way computers work. I don&#8217;t think that this is an accident; the term &#8220;computer&#8221; [...]]]></description>
			<content:encoded><![CDATA[<p>One of the reasons this blog is called &#8220;Live &amp; Code&#8221; is because Computer Science (and by extension programming) is one of the lenses through which I view the world. There are often parallels between the way we think and the way computers work. I don&#8217;t think that this is an accident; the term &#8220;computer&#8221; used to refer to a human being whose profession was computing values. These people would sit and work through algorithms to calculate values that would be used in scientific research.</p>
<p>One of these parallels between humans and computers is the way that we multitask. Computers only <em>seem</em> to multitask by switching between tasks rapidly, with the exception of new multi-core and multi-processor systems, which can run as many tasks in parallel as there are cores or processors. So it was interesting to read recently that <a title="Human multitasking - Wikipedia" href="http://en.wikipedia.org/wiki/Human_multitasking">the prevailing theory is that humans multitask in precisely the same way</a>!</p>
<p><span id="more-337"></span></p>
<p>Analogous to a multitasking CPU, current experimental psychology research shows that <a title="Dual-Task Interference in Simple Tasks: Data and Theory - Harold Pashler [PDF]" href="http://www.pashler.com/Articles/Pashler_PB1994.pdf">interference occurs</a> when we attempt to perform even simple tasks simultaneously. There are certain exceptions to this, particularly when one of the two tasks is stored in &#8220;muscle memory&#8221;, but this is because we can perform such tasks without even thinking about them. In many other cases, the effectiveness with which we perform the tasks is diminished when we are doing more than one task at the same time.</p>
<p>It is also common wisdom in IT that when somebody is deep in his/her work (commonly referred to as <em><a title="Flow (psychology) - Wikipedia" href="http://en.wikipedia.org/wiki/Flow_(psychology)">flow</a></em>), an interruption of even a few seconds can result in <em>15 minutes</em> of lost productivity. While I&#8217;ve never verified the actual number, I have often had trouble putting myself back on a task after being jolted out of it by a short interruption.</p>
<p>When a CPU switches tasks, it must perform a <em><a title="Context Switch - Wikipedia" href="http://en.wikipedia.org/wiki/Context_switch">context switch</a></em>. The current state of the program that is running on the computer, including the values stored in the registers, a reference to the next instruction to execute, and other housekeeping information are stored in memory (RAM). When the program comes back, the stored information is put back into its proper places so that the CPU can pick up where it left off. This is a fairly costly operation as the CPU cannot access RAM even a fraction as fast as it can access its registers. Of course, this means that when a CPU runs two programs simultaneously, it is less efficient at each than if it were concentrating entirely on one program or the other. Determining when to switch to a different program is therefore an incredibly important concern in the design of modern operating systems.</p>
<p>I&#8217;ve witnessed human &#8220;context switching&#8221; in a co-worker of mine. When I knock on her door to ask her a quick question about work that I&#8217;m doing for her, she asks me to give her a moment and looks to be deep in thought. She then asks me to repeat my question and answers it with surprising conciseness and accuracy. She has told me that she needs to switch from the mindset of what she&#8217;s currently working on to the mindset of what I&#8217;m asking her or she can&#8217;t answer properly.</p>
<p>This isn&#8217;t to say that multitasking is <em>bad</em>, but I am acutely aware that when I do multitask, I am not going to be able to perform each task as effectively as if I were focused entirely on one. Also, there are certain points at which it is easier or more natural to switch from doing one thing to doing another, particularly where I&#8217;ve accomplished a sub-goal in the task or where I&#8217;ve written down detailed notes on the current state of what I&#8217;m doing, which makes it easier to switch back to it later.</p>
<p>What do you think?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.liveandcode.com/2010/01/11/context-switching/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
