<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>So, you want to write a computer book...</title><link>http://blogs.msdn.com/ericgu/pages/396328.aspx</link><description>As some of you know, in the early years of the 21st century, I wrote a book on C#. Since then, I've had a number of people who are interested in writing a book themselves ask me about my experience, so I thought I'd spend some time to write something</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>So you want to write a computer book?</title><link>http://blogs.msdn.com/ericgu/pages/396328.aspx#404301</link><pubDate>Thu, 31 Mar 2005 22:39:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:404301</guid><dc:creator>Eric Gunnerson's C# Compendium</dc:creator><description /></item><item><title>re: So, you want to write a computer book...</title><link>http://blogs.msdn.com/ericgu/pages/396328.aspx#404326</link><pubDate>Thu, 31 Mar 2005 21:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:404326</guid><dc:creator>Jim Beveridge</dc:creator><description>Great article.  I wrote Multithreading Application in Win32 many moons ago, and your experience mirrors mine.  One interesting discussion I heard on authoring technical books is that you need to be a beginner or an expert.  If you are a beginner, you can effectively document your learning experience.  I started out with a deep background in operating system design but minimal experience in Win32 multithreading, so I was both an expert and a beginner.  That combination worked very well for me.&lt;br&gt;&lt;br&gt;I would strongly encourage potential authors to get a couple articles published in magazines.  First, these pay pretty well  (often over $1000 per article.)  Second, you'll find out what it's like writing with a deadline, negotiating with acquisition editors and working with copy editors.  If you can't do a successful magazine article, it's unlikely you'll be successful writing a book.&lt;br&gt;&lt;br&gt;Good luck!&lt;br&gt;</description></item><item><title>re: So, you want to write a computer book...</title><link>http://blogs.msdn.com/ericgu/pages/396328.aspx#404327</link><pubDate>Thu, 31 Mar 2005 21:45:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:404327</guid><dc:creator>Alfred Thompson</dc:creator><description>10,000 copies is a really good run. I think a lot of books don't get half that. This is especially true if your book is very closely tied to a version of software that is going to have a major new version soon. In other words this is a poor time to write a Visual Studio 2003 based book but not a bad time for 2005. But really you want to decide that the non royalty reasons are enough for you to spend the time so you are not too disappointed if you don't sell well.</description></item><item><title>re: So, you want to write a computer book...</title><link>http://blogs.msdn.com/ericgu/pages/396328.aspx#404331</link><pubDate>Thu, 31 Mar 2005 22:04:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:404331</guid><dc:creator>Sebastien St-Laurent</dc:creator><description>Being a published author myself (Shaders for Game Programmers and Artists, &lt;a target="_new" href="http://www.amazon.com/exec/obidos/ASIN/1592000924"&gt;http://www.amazon.com/exec/obidos/ASIN/1592000924&lt;/a&gt;), i can share a few thoughts on the whole thing...&lt;br&gt;&lt;br&gt;Economics&lt;br&gt;---------&lt;br&gt;The standard wholesale discount expected by book wholesalers is 55% off retail. The bookstores generally get 40% off. But when you do ask the publisher about what the royalty is based from, they'll usually say &amp;quot;about 50%&amp;quot;.&lt;br&gt;&lt;br&gt;Money&lt;br&gt;-----&lt;br&gt;Most technical books don't even sell 10,000 copies. But i think that most publishers won't take a book idea unless they think it can break their &amp;quot;break even&amp;quot; mark which is usually somewhere between 5,000-10,000 copies. That being said, my first book gave me an advance of 9,000$ which sales have not managed to exceed yet. Not much for about 15-20h/week for 6 months...&lt;br&gt;&lt;br&gt;Marketing&lt;br&gt;---------&lt;br&gt;From my experience, the publisher will apply some basic boilerplate promotion plan. If your book doesn't become a bestseller, they will drop it and move on to their next title. As an author, you cannot count on the publisher to do all the promotional efforts and have to be ready to create as much exposure for your title by yourself.&lt;br&gt;&lt;br&gt;My Conclusion?&lt;br&gt;--------------&lt;br&gt;Well I was writing my second title and I've decided to follow the old saying &amp;quot;If you want to do it right, do it yourself!&amp;quot; I've founded my own little publishing company (www.ParadoxalPress.com) and will be self-publishing my next title. &lt;br&gt;&lt;br&gt;Will it be more profitable? Well i would effectively make about 4-5x the profit per unit sold. Of course, I did have to invest some money to get the title ready but managed to keep my costs reasonable and my break-even point is currently at about 500 copies.&lt;br&gt;&lt;br&gt;My next title (The COMPLETE Effect and HLSL Guide) is set for release in September, so we will soon enough see the results of my experiment :)&lt;br&gt;&lt;br&gt;</description></item><item><title>re: So, you want to write a computer book...</title><link>http://blogs.msdn.com/ericgu/pages/396328.aspx#404332</link><pubDate>Thu, 31 Mar 2005 22:09:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:404332</guid><dc:creator>Mujtaba Syed</dc:creator><description>Great article.&lt;br&gt;&lt;br&gt;Of every ten books I purchase, only one is worth reading. Alas, I get to know that only after I have gone through a chapter or two.&lt;br&gt;&lt;br&gt;I believe aspiring authors should follow Bruce Eckel's model: write online, seek feedback, and improve. Once the writing scales a particular goodness threshold (decided by the community), get a print version out. There are several benefits of this approace: any kind of writing can get published online but only great writings get published on paper; and the subject matter can be kept current online as the product goes through CTP, pre-alpha, and beta release.</description></item><item><title>Eric Gunnerson's Blog On Writing A Book</title><link>http://blogs.msdn.com/ericgu/pages/396328.aspx#404343</link><pubDate>Fri, 01 Apr 2005 00:42:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:404343</guid><dc:creator>Kingsley.Tagbo</dc:creator><description>What does it take to market a book and how much does&amp;amp;nbsp;it help&amp;amp;nbsp;your consulting practice? &lt;br&gt;Read&amp;amp;nbsp;a...</description></item><item><title>re: So, you want to write a computer book...</title><link>http://blogs.msdn.com/ericgu/pages/396328.aspx#404350</link><pubDate>Thu, 31 Mar 2005 23:20:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:404350</guid><dc:creator>Mike Gunderloy</dc:creator><description>I recommend that first-time authors base their hourly rate calculations on their advance, not on their royalty dreams. Most computer books never even prove out their advance.&lt;br&gt;&lt;br&gt;I babbled at length about this and other topics a while ago - &lt;a target="_new" href="http://www.larkware.com/adviceforwriters.html"&gt;http://www.larkware.com/adviceforwriters.html&lt;/a&gt;</description></item><item><title>re: Self publishing and insider secrets</title><link>http://blogs.msdn.com/ericgu/pages/396328.aspx#404787</link><pubDate>Fri, 01 Apr 2005 22:05:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:404787</guid><dc:creator>Brian Bischof</dc:creator><description>I self-published my book Crystal Reports .NET Programming and learned a lot from the experience. I posted ten pages of tips and info for anyone interested in seeing what it takes to be a publisher.&lt;br&gt;&lt;br&gt;&lt;a target="_new" href="http://www.crystalreportsbook.com/selfpublishing.asp"&gt;http://www.crystalreportsbook.com/selfpublishing.asp&lt;/a&gt;&lt;br&gt;&lt;br&gt;</description></item><item><title>Blog link of the week 13</title><link>http://blogs.msdn.com/ericgu/pages/396328.aspx#405065</link><pubDate>Mon, 04 Apr 2005 00:37:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:405065</guid><dc:creator>Daniel Moth</dc:creator><description>Blog link of the week 13</description></item><item><title>re: So, you want to write a computer book...</title><link>http://blogs.msdn.com/ericgu/pages/396328.aspx#405167</link><pubDate>Mon, 04 Apr 2005 11:11:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:405167</guid><dc:creator>Chris</dc:creator><description>&amp;quot;Just make sure never to point people to your book instead of answering their question - that's a sure way not to get a sale&amp;quot;&lt;br&gt;&lt;br&gt;This is not just detrimental to a single book sale, but can affect the sales of any future books, and even destroy your reputation.&lt;br&gt;&lt;br&gt;Mr &amp;quot;B.V.&amp;quot; knows that only too well from his days on the VB-DATA lists when he nearly always answered questions with just &amp;quot;Read Chapter 3 of my book where I explain that&amp;quot;</description></item><item><title>re: So, you want to write a computer book...</title><link>http://blogs.msdn.com/ericgu/pages/396328.aspx#405264</link><pubDate>Mon, 04 Apr 2005 20:07:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:405264</guid><dc:creator>Clinton Pierce</dc:creator><description>I've written two books (&amp;quot;SAMS Teach Yourself Perl in 24 Hours&amp;quot; and &amp;quot;Perl Developer's Dictionary&amp;quot;) and tech edited a few others, and I've gotta tell you, you're right on the money.&lt;br&gt;&lt;br&gt;Money:  The money from one was pretty good and then fell off after a couple of years.  About the point where a monthly royalty check could just barely buy a nice dinner, I did a new edition and it got new life.  The other book had the misfortune of debuting in the summer of 2001, right when the tech market crashed and actually lost money.  Ahh well.&lt;br&gt;&lt;br&gt;I wouldn't have done it for the money though, it's not worth it.  It's a *lot* of work.&lt;br&gt;&lt;br&gt;Fame: No tech-author groupies.  Looks really good on a resume though, and employers like the fact that they're getting a programmer and a proven tech writer in one package.&lt;br&gt;&lt;br&gt;Experience: There's nothing quite like opening a box of freshly printed books with your name on the cover.  Or walking by the tech section at a bookstore and &amp;quot;fronting&amp;quot; your title.</description></item><item><title> Eric Gunnerson s C Compendium So you want to write a computer book | Quick Diets</title><link>http://blogs.msdn.com/ericgu/pages/396328.aspx#9715706</link><pubDate>Tue, 09 Jun 2009 14:38:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9715706</guid><dc:creator> Eric Gunnerson s C Compendium So you want to write a computer book | Quick Diets</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://quickdietsite.info/story.php?id=11383"&gt;http://quickdietsite.info/story.php?id=11383&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>