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
_______________________________________________
Python-authors mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-authors
