<?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: Book review: Getting Real</title>
	<atom:link href="http://blog.global-roam.com/index.php/2009/08/book-review-getting-real/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.global-roam.com/index.php/2009/08/book-review-getting-real/</link>
	<description>Lessons we're learning about business, life &#38; art in our software development company</description>
	<pubDate>Tue, 07 Feb 2012 11:51:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul McArdle</title>
		<link>http://blog.global-roam.com/index.php/2009/08/book-review-getting-real/comment-page-1/#comment-195</link>
		<dc:creator>Paul McArdle</dc:creator>
		<pubDate>Fri, 04 Sep 2009 01:44:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.global-roam.com/?p=555#comment-195</guid>
		<description>See this commentary here about &lt;a href="http://onstartups.com/tabid/3339/bid/10386/7-Things-Your-Startup-SHOULD-Copy-From-37signals.aspx" target="_blank" rel="nofollow"&gt;7 Things You SHOULD Copy from 37signals&lt;/a&gt; for further discussions.

In simple terms, my view is that you can only get to "average" by copying people - though in some cases (e.g. where we are below average) that will certainly be a start. The really &lt;a href="http://blog.global-roam.com/index.php/2009/08/hello-my-name-is-adam/" rel="nofollow"&gt;remarkable&lt;/a&gt; companies are ones that create new ways of doing things (or repurpose old methods).  
  
So "steal ideas shamelessly", wherever you find them, but make sure you constantly think about how it fits with your particular business.  </description>
		<content:encoded><![CDATA[<p>See this commentary here about <a href="http://onstartups.com/tabid/3339/bid/10386/7-Things-Your-Startup-SHOULD-Copy-From-37signals.aspx" target="_blank" rel="nofollow">7 Things You SHOULD Copy from 37signals</a> for further discussions.</p>
<p>In simple terms, my view is that you can only get to &#8220;average&#8221; by copying people - though in some cases (e.g. where we are below average) that will certainly be a start. The really <a href="http://blog.global-roam.com/index.php/2009/08/hello-my-name-is-adam/" rel="nofollow">remarkable</a> companies are ones that create new ways of doing things (or repurpose old methods).  </p>
<p>So &#8220;steal ideas shamelessly&#8221;, wherever you find them, but make sure you constantly think about how it fits with your particular business.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd Bowles</title>
		<link>http://blog.global-roam.com/index.php/2009/08/book-review-getting-real/comment-page-1/#comment-178</link>
		<dc:creator>Todd Bowles</dc:creator>
		<pubDate>Fri, 28 Aug 2009 04:16:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.global-roam.com/?p=555#comment-178</guid>
		<description>This book both excites and angers me. I finished it today.

Lots of small, bite sized ideas that will resonate with a specific type of person. Lots of things that are very useful for interface driven applications, but less useful for the behind the scenes work (which is understandable, being that the book is on web development).

It slots in quite nicely with the Pragmatic Programmer way of thinking, doing only what is necessary, when it's necessary, and not overloading yourself with too much of anything. Automating or skipping tasks when possible and so on.

Some points I liked:
Don't let the customer force you into adding features that aren't necessary, control your own development, and control your features. Say "no" or "not now" when you have to.
Develop simple software that focuses on being good at what it does, not being everything to everyone.
Simplify by making decisions and assumptions for your customers.
Alone time, where people aren't allowed to talk or communicate or email or anything, just work.
Make your company and your software stand for something, have a vision that people can get involved in.

Some points I didn't like:
Don't write functional specifications.
No mention of documentation or maintenance by people who aren't the original developers.
Toxic meetings. Meetings have a value when used efficiently and effectively.

Anyway, at least it was a quick read.</description>
		<content:encoded><![CDATA[<p>This book both excites and angers me. I finished it today.</p>
<p>Lots of small, bite sized ideas that will resonate with a specific type of person. Lots of things that are very useful for interface driven applications, but less useful for the behind the scenes work (which is understandable, being that the book is on web development).</p>
<p>It slots in quite nicely with the Pragmatic Programmer way of thinking, doing only what is necessary, when it&#8217;s necessary, and not overloading yourself with too much of anything. Automating or skipping tasks when possible and so on.</p>
<p>Some points I liked:<br />
Don&#8217;t let the customer force you into adding features that aren&#8217;t necessary, control your own development, and control your features. Say &#8220;no&#8221; or &#8220;not now&#8221; when you have to.<br />
Develop simple software that focuses on being good at what it does, not being everything to everyone.<br />
Simplify by making decisions and assumptions for your customers.<br />
Alone time, where people aren&#8217;t allowed to talk or communicate or email or anything, just work.<br />
Make your company and your software stand for something, have a vision that people can get involved in.</p>
<p>Some points I didn&#8217;t like:<br />
Don&#8217;t write functional specifications.<br />
No mention of documentation or maintenance by people who aren&#8217;t the original developers.<br />
Toxic meetings. Meetings have a value when used efficiently and effectively.</p>
<p>Anyway, at least it was a quick read.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Book Review: A complaint is a gift &#124; Behind the Scenes at Global-Roam</title>
		<link>http://blog.global-roam.com/index.php/2009/08/book-review-getting-real/comment-page-1/#comment-136</link>
		<dc:creator>Book Review: A complaint is a gift &#124; Behind the Scenes at Global-Roam</dc:creator>
		<pubDate>Tue, 18 Aug 2009 01:18:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.global-roam.com/?p=555#comment-136</guid>
		<description>[...] posts you might like: Book review: Getting Real How to kill the golden [...]</description>
		<content:encoded><![CDATA[<p>[...] posts you might like: Book review: Getting Real How to kill the golden [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

