If you’ve ever hankered after writing a technical book then Michael Foord has some advice for you garnered from writing IronPython in Action.
Sounds like a shed load of work for no money… something I seem to be specialising in at the moment. 
Update: Michael has done a post detailing his first quarter earning from IronPython in Action. Not a lot of money for two years work… the only thing worse paid than writing a book is writing open source software.
Popularity: 2% [?]
Related posts:
{ 3 comments }
Wow, great link. It’s very enlightening to hear about the troubles he had. And yeah, it definitely sounds like money shouldn’t be the motivating factor
Jack – nice article that. He pretty much hits it on the head and the parallels with software development projects is overwhelming – a case of getting down to the nitty gritty before a line is written. I have to say that I once started writing a technical book and got quite a bit through it before other commitments took over. As the author says it is a rewarding process if you get finished !!
@Brendan – any kind of writing is a major time sink, even writing this blog believe it or not. Writing a book must be a nightmare! The parrallel to writing software I think is very well made. Though, software is done when the specification is met, with writing things tend to be more subjective. If you’ll forgive me for asking, what was the topic of your book?
Comments on this entry are closed.