<?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: What is it like to write a technical book?</title>
	<atom:link href="http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/</link>
	<description>Stay curious!</description>
	<lastBuildDate>Wed, 10 Mar 2010 17:56:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The &#34;Invent with Python&#34; Blog &#8212; Lessons Learned from Writing a Technical Book to Teach Programming</title>
		<link>http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/#comment-17209</link>
		<dc:creator>The &#34;Invent with Python&#34; Blog &#8212; Lessons Learned from Writing a Technical Book to Teach Programming</dc:creator>
		<pubDate>Tue, 03 Nov 2009 03:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/#comment-17209</guid>
		<description>[...] What is it like to write a technical book? (Xaprb blog) http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/ [...]</description>
		<content:encoded><![CDATA[<p>[...] What is it like to write a technical book? (Xaprb blog) <a href="http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/" rel="nofollow">http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What it is like to write a technical book &#171; Linux and Friends</title>
		<link>http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/#comment-16758</link>
		<dc:creator>What it is like to write a technical book &#171; Linux and Friends</dc:creator>
		<pubDate>Mon, 17 Aug 2009 00:36:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/#comment-16758</guid>
		<description>[...] detailed overview of what it is to write a book. The following  is a small portion of his thoughts from the article. If you’re thinking about writing a book, I’d suggest you spend some time visualizing how much [...]</description>
		<content:encoded><![CDATA[<p>[...] detailed overview of what it is to write a book. The following  is a small portion of his thoughts from the article. If you’re thinking about writing a book, I’d suggest you spend some time visualizing how much [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/#comment-16144</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 01 Apr 2009 08:01:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/#comment-16144</guid>
		<description>A major problem that you nonfiction authors face is that most interested consumers will not even discover that your book exists before making a purchasing decision. And they can&#039;t buy your book if they don&#039;t know it exists! This is because Amazon search results are so garbled and unfocused. For example, if you search on &quot;mysql&quot; at Amazon you will get 416 results, scattered over a zillion pages. 

Let&#039;s say you have just authored the greatest book ever written on the general topic of MySQL (competing with Paul DuBois&#039; tome). The chances are your book will end up on the nether pages of the Amazon results, making it virtually impossible for interested consumers to discover it (hell, hardly anyone looks at page 2 of search results, let alone pages 3, 4, 5, ..., infinity). 

So you went to all the trouble and pain of writing a great book, but nobody knows it exists, and thus sales are dismal. Result: it goes out of print before you can blink. All of that effort and sweat down the drain.

That&#039;s why I went to the trouble of creating www.zercle.com, to solve this problem. Basically, all of you nonfiction authors should go on Zercle and create groups for your books (if one doesn&#039;t already exist), and put your book in the group. And put competing books in the groups too. And then tell everyone about it. Result: Consumers will (for the first time ever) have a simple way to discover your book, and you will have a way to guarantee that your book is discoverable. 

Once everyone does this, then Amazon or Google will want to incorporate the Zercle book groups into their search results, making your book even more discoverable. 

In short, the Stone Age for nonfiction authors and book consumers will be over. A new era of Light will begin.</description>
		<content:encoded><![CDATA[<p>A major problem that you nonfiction authors face is that most interested consumers will not even discover that your book exists before making a purchasing decision. And they can&#8217;t buy your book if they don&#8217;t know it exists! This is because Amazon search results are so garbled and unfocused. For example, if you search on &#8220;mysql&#8221; at Amazon you will get 416 results, scattered over a zillion pages. </p>
<p>Let&#8217;s say you have just authored the greatest book ever written on the general topic of MySQL (competing with Paul DuBois&#8217; tome). The chances are your book will end up on the nether pages of the Amazon results, making it virtually impossible for interested consumers to discover it (hell, hardly anyone looks at page 2 of search results, let alone pages 3, 4, 5, &#8230;, infinity). </p>
<p>So you went to all the trouble and pain of writing a great book, but nobody knows it exists, and thus sales are dismal. Result: it goes out of print before you can blink. All of that effort and sweat down the drain.</p>
<p>That&#8217;s why I went to the trouble of creating <a href="http://www.zercle.com" rel="nofollow">http://www.zercle.com</a>, to solve this problem. Basically, all of you nonfiction authors should go on Zercle and create groups for your books (if one doesn&#8217;t already exist), and put your book in the group. And put competing books in the groups too. And then tell everyone about it. Result: Consumers will (for the first time ever) have a simple way to discover your book, and you will have a way to guarantee that your book is discoverable. </p>
<p>Once everyone does this, then Amazon or Google will want to incorporate the Zercle book groups into their search results, making your book even more discoverable. </p>
<p>In short, the Stone Age for nonfiction authors and book consumers will be over. A new era of Light will begin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xaprb</title>
		<link>http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/#comment-16038</link>
		<dc:creator>Xaprb</dc:creator>
		<pubDate>Tue, 17 Mar 2009 22:15:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/#comment-16038</guid>
		<description>A friend and fellow open-source author wrote about his experience writing a book on PostgreSQL:

http://www.postgresql.org/docs/books/awbook/bookoneyear</description>
		<content:encoded><![CDATA[<p>A friend and fellow open-source author wrote about his experience writing a book on PostgreSQL:</p>
<p><a href="http://www.postgresql.org/docs/books/awbook/bookoneyear" rel="nofollow">http://www.postgresql.org/docs/books/awbook/bookoneyear</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dimebrain &#171; Books vs. blogs: the value of technical books and ideas to improve them</title>
		<link>http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/#comment-15585</link>
		<dc:creator>dimebrain &#171; Books vs. blogs: the value of technical books and ideas to improve them</dc:creator>
		<pubDate>Tue, 23 Dec 2008 13:31:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2008/06/15/what-is-it-like-to-write-a-technical-book/#comment-15585</guid>
		<description>[...] simply don&#8217;t need to write a successful technical blog (though it helps). Here is a good blog post on one author&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[...] simply don&#8217;t need to write a successful technical blog (though it helps). Here is a good blog post on one author&#8217;s [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
