From doug.hellmann at gmail.com Sun Jul 12 15:38:14 2009 From: doug.hellmann at gmail.com (Doug Hellmann) Date: Sun, 12 Jul 2009 09:38:14 -0400 Subject: [Python-authors] Python book authors on TV In-Reply-To: <906718.68641.qm@web88102.mail.re2.yahoo.com> References: <906718.68641.qm@web88102.mail.re2.yahoo.com> Message-ID: <71A78DCD-61DA-4E2D-B70F-40120EED24F3@gmail.com> [Cross-posting from advocacy at python.org] On Jun 26, 2009, at 12:27 PM, Warren Sande wrote: > Carter and I were on the local 6:00 news a couple days ago, when we > had the book launch for our book "Hello World! Computer Programming > for Kids and Other Beginners" > > You can see it here: > > http://watch.ctv.ca/news/clip186877#clip186877 Hi, Warren, What a great clip! I really enjoyed your book, and have been hounding all of my friends with kids to pick up copies of their own. Thanks, Doug -------------- next part -------------- An HTML attachment was scrubbed... URL: From fuzzyman at voidspace.org.uk Tue Jul 14 00:33:42 2009 From: fuzzyman at voidspace.org.uk (Michael Foord) Date: Mon, 13 Jul 2009 23:33:42 +0100 Subject: [Python-authors] Writing a technical book Message-ID: <4A5BB646.8090201@voidspace.org.uk> Hello all, I've written up my experiences of writing a technical book for Manning. Despite it all I still recommend Manning if you really *have* to write a book... Includes the process, what I learned and some advice on contracts (which I didn't follow myself but wish I had): http://www.voidspace.org.uk/python/articles/technical-writing.shtml All the best, Michael Foord -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog From wescpy at gmail.com Tue Jul 14 01:06:41 2009 From: wescpy at gmail.com (wesley chun) Date: Mon, 13 Jul 2009 16:06:41 -0700 Subject: [Python-authors] Writing a technical book In-Reply-To: <4A5BB646.8090201@voidspace.org.uk> References: <4A5BB646.8090201@voidspace.org.uk> Message-ID: <78b3a9580907131606j374c9847p986f15b07e6c2622@mail.gmail.com> > I've written up my experiences of writing a technical book for Manning. > Despite it all I still recommend Manning if you really *have* to write a book... > > http://www.voidspace.org.uk/python/articles/technical-writing.shtml michael, thanks for your write-up... it is pretty educational and definitely brings back memories of my own writing. i haven't taken the opportunity as you have to document everything... goodness knows i already didn't have time to write the book(s) themselves! LOL on a somewhat related note, there was a similar thread a few years ago on the newsgroup where some people highlighted some of their frustrations with Manning: http://groups.google.com/group/comp.lang.python/browse_thread/thread/8527e080899a6246 finally, regarding your comment about Word, DocBook, and XML, and can also understand your situation there. in fact, the way authors create their manuscript had become somewhat of a passion/interest area enough for me to have done some research on it. i shall reveal my results, both typical as well as perhaps mindblowing to some, at OSCON in a few weeks: http://en.oreilly.com/oscon2009/public/schedule/detail/8038 best regards, -- wesley - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - "Core Python Programming", Prentice Hall, (c)2007,2001 "Python Fundamentals", Prentice Hall, (c)2009 http://corepython.com "Python Web Development with Django", Addison Wesley, (c) 2009 http://withdjango.com wesley.j.chun :: wescpy-at-gmail.com python training and technical consulting cyberweb.consulting : silicon valley, ca http://cyberwebconsulting.com From fuzzyman at voidspace.org.uk Tue Jul 14 01:13:11 2009 From: fuzzyman at voidspace.org.uk (Michael Foord) Date: Tue, 14 Jul 2009 00:13:11 +0100 Subject: [Python-authors] Writing a technical book In-Reply-To: <78b3a9580907131606j374c9847p986f15b07e6c2622@mail.gmail.com> References: <4A5BB646.8090201@voidspace.org.uk> <78b3a9580907131606j374c9847p986f15b07e6c2622@mail.gmail.com> Message-ID: <4A5BBF87.1080406@voidspace.org.uk> Thanks for the comments Wesley. I did find Manning helpful - but their processes are long. Not going to be at OSCON but definitely interested in your talk and the toolchain you suggest. Michael wesley chun wrote: >> I've written up my experiences of writing a technical book for Manning. >> Despite it all I still recommend Manning if you really *have* to write a book... >> >> http://www.voidspace.org.uk/python/articles/technical-writing.shtml >> > > > michael, > > thanks for your write-up... it is pretty educational and definitely > brings back memories of my own writing. i haven't taken the > opportunity as you have to document everything... goodness knows i > already didn't have time to write the book(s) themselves! LOL > > on a somewhat related note, there was a similar thread a few years ago > on the newsgroup where some people highlighted some of their > frustrations with Manning: > > http://groups.google.com/group/comp.lang.python/browse_thread/thread/8527e080899a6246 > > finally, regarding your comment about Word, DocBook, and XML, and can > also understand your situation there. in fact, the way authors create > their manuscript had become somewhat of a passion/interest area enough > for me to have done some research on it. i shall reveal my results, > both typical as well as perhaps mindblowing to some, at OSCON in a few > weeks: > > http://en.oreilly.com/oscon2009/public/schedule/detail/8038 > > best regards, > -- wesley > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > "Core Python Programming", Prentice Hall, (c)2007,2001 > "Python Fundamentals", Prentice Hall, (c)2009 > http://corepython.com > > "Python Web Development with Django", Addison Wesley, (c) 2009 > http://withdjango.com > > wesley.j.chun :: wescpy-at-gmail.com > python training and technical consulting > cyberweb.consulting : silicon valley, ca > http://cyberwebconsulting.com > -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog From steve at holdenweb.com Tue Jul 14 02:01:39 2009 From: steve at holdenweb.com (Steve Holden) Date: Mon, 13 Jul 2009 20:01:39 -0400 Subject: [Python-authors] Writing a technical book In-Reply-To: <4A5BB646.8090201@voidspace.org.uk> References: <4A5BB646.8090201@voidspace.org.uk> Message-ID: <4A5BCAE3.60502@holdenweb.com> Michael Foord wrote: > Hello all, > > I've written up my experiences of writing a technical book for Manning. > Despite it all I still recommend Manning if you really *have* to write a > book... > > Includes the process, what I learned and some advice on contracts (which > I didn't follow myself but wish I had): > > http://www.voidspace.org.uk/python/articles/technical-writing.shtml > > All the best, > > Michael Foord > Nice one! Another rule of thumb for how long it will take is "think of a number, then double it, then double it again". regards Steve -- Steve Holden +1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/ Watch PyCon on video now! http://pycon.blip.tv/ From vceder at canterburyschool.org Tue Jul 14 02:26:40 2009 From: vceder at canterburyschool.org (Vern Ceder) Date: Mon, 13 Jul 2009 20:26:40 -0400 Subject: [Python-authors] Writing a technical book In-Reply-To: <4A5BB646.8090201@voidspace.org.uk> References: <4A5BB646.8090201@voidspace.org.uk> Message-ID: <4A5BD0C0.2020904@canterburyschool.org> Michael, I'm in the last (one hopes) stages of revising Manning's Quick Python Book for a Python 3 specific second edition. Obviously, doing a revision is less work than writing a new book from scratch, but I would second all of your observations about both the process in general and working with Manning in particular. (I also worked on a project with O'Reilly that was ultimately canceled, and I've found the process with Manning to be better, although sometimes still exasperating.) One thing that I would add to your advice on contracts is, "Get an agent." Sure, an agent will skim off 15% of your hard earned royalties, but in my case, having an knowledgeable agent increased my advances by over 25%. And they know all of the pitfalls of the publishing biz that most of us have never dreamed of. Just as tech book publishers have more book ideas than authors, agents also see more opportunities than they have clients, and are always on the lookout for authors to represent, so ask around and get good representation. JMHO. Cheers, Vern Ceder Michael Foord wrote: > Hello all, > > I've written up my experiences of writing a technical book for Manning. > Despite it all I still recommend Manning if you really *have* to write a > book... > > Includes the process, what I learned and some advice on contracts (which > I didn't follow myself but wish I had): > > http://www.voidspace.org.uk/python/articles/technical-writing.shtml > > All the best, > > Michael Foord > -- This time for sure! -Bullwinkle J. Moose ----------------------------- Vern Ceder, Director of Technology Canterbury School, 3210 Smith Road, Ft Wayne, IN 46804 vceder at canterburyschool.org; 260-436-0746; FAX: 260-436-5137 From fuzzyman at voidspace.org.uk Tue Jul 14 04:25:15 2009 From: fuzzyman at voidspace.org.uk (Michael Foord) Date: Tue, 14 Jul 2009 03:25:15 +0100 Subject: [Python-authors] Writing a technical book In-Reply-To: <4A5BCAE3.60502@holdenweb.com> References: <4A5BB646.8090201@voidspace.org.uk> <4A5BCAE3.60502@holdenweb.com> Message-ID: <4A5BEC8B.1030709@voidspace.org.uk> Steve Holden wrote: > Michael Foord wrote: > >> Hello all, >> >> I've written up my experiences of writing a technical book for Manning. >> Despite it all I still recommend Manning if you really *have* to write a >> book... >> >> Includes the process, what I learned and some advice on contracts (which >> I didn't follow myself but wish I had): >> >> http://www.voidspace.org.uk/python/articles/technical-writing.shtml >> >> All the best, >> >> Michael Foord >> >> > Nice one! > > Another rule of thumb for how long it will take is "think of a number, > then double it, then double it again". > So many people said this to me (or similar) when I started to consider writing a book that I went into it with no preconceived idea of how long it would take, just a determination to see it through - a mindset I can recommend. Michael > regards > Steve > -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog From aahz at pythoncraft.com Wed Jul 15 04:53:18 2009 From: aahz at pythoncraft.com (Aahz) Date: Tue, 14 Jul 2009 19:53:18 -0700 Subject: [Python-authors] Writing a technical book In-Reply-To: <4A5BD0C0.2020904@canterburyschool.org> References: <4A5BB646.8090201@voidspace.org.uk> <4A5BD0C0.2020904@canterburyschool.org> Message-ID: <20090715025318.GA6407@panix.com> On Mon, Jul 13, 2009, Vern Ceder wrote: > > One thing that I would add to your advice on contracts is, "Get an agent." > > Sure, an agent will skim off 15% of your hard earned royalties, but in > my case, having an knowledgeable agent increased my advances by over > 25%. And they know all of the pitfalls of the publishing biz that most > of us have never dreamed of. Just as tech book publishers have more book > ideas than authors, agents also see more opportunities than they have > clients, and are always on the lookout for authors to represent, so ask > around and get good representation. JMHO. More than that, it's worth 15% to me to not deal with that stuff. With remarkably few exceptions, writing books isn't directly remunerative after you figure out your hourly wage. I heartily recommend anything that makes the process easier. -- Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/ "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." --Red Adair