<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Code Organization: In the eye of the beholder?</title>
	<link>http://tottinge.blogsome.com/2005/11/18/code-organization-in-the-eye-of-the-beholder/</link>
	<description>Tim Ottinger on Christianity, freedom, software, podcasts, and really hot-looking guitars.</description>
	<pubDate>Thu, 28 Aug 2008 16:31:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: Tim</title>
		<link>http://tottinge.blogsome.com/2005/11/18/code-organization-in-the-eye-of-the-beholder/#comment-158</link>
		<pubDate>Sun, 20 Nov 2005 02:16:16 +0000</pubDate>
		<guid>http://tottinge.blogsome.com/2005/11/18/code-organization-in-the-eye-of-the-beholder/#comment-158</guid>
					<description>Well, of course. It's always hard to get traction in an ongoing project, but I hoped that the point was that there can be better values than being easy for a new guy.  

Like vi, which is hard to learn, was one of the best things I ever bothered to learn.  Well, OO was kinda new and took time at first, and so was C++.  A lot of worthwhile stuff is not novice-friendly.

I tend to put down guis which are novice-friendly but expert-hostile.  I think that it may be good that it's organized as it is, even though that's not convenient for Tim-the-new-guy.  It might be excellent later on for Tim-the-expert. 

So I'm trying to get from new guy to expert as fast as I can.  The interesting thing is trying to figure out if there are any tricks or shortcuts to get there quickly.

</description>
		<content:encoded><![CDATA[	<p>Well, of course. It&#8217;s always hard to get traction in an ongoing project, but I hoped that the point was that there can be better values than being easy for a new guy.  </p>
	<p>Like vi, which is hard to learn, was one of the best things I ever bothered to learn.  Well, OO was kinda new and took time at first, and so was C++.  A lot of worthwhile stuff is not novice-friendly.</p>
	<p>I tend to put down guis which are novice-friendly but expert-hostile.  I think that it may be good that it&#8217;s organized as it is, even though that&#8217;s not convenient for Tim-the-new-guy.  It might be excellent later on for Tim-the-expert. </p>
	<p>So I&#8217;m trying to get from new guy to expert as fast as I can.  The interesting thing is trying to figure out if there are any tricks or shortcuts to get there quickly.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Steve</title>
		<link>http://tottinge.blogsome.com/2005/11/18/code-organization-in-the-eye-of-the-beholder/#comment-157</link>
		<pubDate>Fri, 18 Nov 2005 17:04:29 +0000</pubDate>
		<guid>http://tottinge.blogsome.com/2005/11/18/code-organization-in-the-eye-of-the-beholder/#comment-157</guid>
					<description>Sounds like youre having some issues getting familiar with the code.  You are open to learn so dont sweat it.  Youll be up to speed in no time.

Also, look at it another way.  It sounds like you are going over all of there code to figure things out.  This not only allows you to get familiar with the code, but it lets you see how they write.  You may be able to go back later and augment there code to a better way.  They are getting great code coverage from you by you reviewing it.  Kinda like peer code reveiws.</description>
		<content:encoded><![CDATA[	<p>Sounds like youre having some issues getting familiar with the code.  You are open to learn so dont sweat it.  Youll be up to speed in no time.</p>
	<p>Also, look at it another way.  It sounds like you are going over all of there code to figure things out.  This not only allows you to get familiar with the code, but it lets you see how they write.  You may be able to go back later and augment there code to a better way.  They are getting great code coverage from you by you reviewing it.  Kinda like peer code reveiws.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
