Sunday, February 12, 2006
« Expert VB/C# 2005 Business Objects updat... | Main | SPOIL - interesting ideas »

Every now and then someone asks what tools I use to write books and articles.

 

I write in Word. Typically the publisher provides a specific template with styles that are to be used, so when they get to the last stage and need to do layout they can easily change the styles to get the proper appearance on the printed page.

 

Graphics, figures and screen-shots are, I find, the most frustrating part of the process in many ways. I use Snagit for capturing screen images into TIFF files, which isn’t too bad. But for creating other graphics I use a combination of Visio, PowerPoint, Corel Draw, MS Paint, screen shots and Snagit – along with Acrobat and (more recently) PDF Converter to generate PDF docs containing the figures. Not being graphically oriented, I find the whole process arcane and frustrating – especially as I’ve often had to redo figures a couple times because they are “blurry” or something – typically due to various resolution issues.

 

As an aside, this is what scares me about WPF (Avalon), since all of us programmers are going to be forced to learn all this arcane graphics stuff just to be competent at even basic application development. Personally I think that this could derail WPF adoption overall – at least until a large set of stock, good-looking, controls come into being from either Microsoft or third parties.

 

Microsoft seems to have this deluded idea that business sponsors are going to pay for graphic designers to build the UI – which I think is highly unlikely, given that they typically won’t even pay for decent testing… Who’d pay to make it pretty when they won’t even pay to make sure it actually works?!?

 

But back to the tools.

 

All the writing is done in Word. The final stage of reviewing however, occurs in PDF form. The publisher does the final layout, resulting in a PDF which will ultimately be sent to the printer. But I have to go through each chapter in PDF form to catch any final issues (typos, graphics issues, etc). I annotate the PDF files and send them back, so the layout people can make the changes and recreate the PDF.

 

I also use Microsoft Project. Not for the writing itself, but to schedule the process. Before committing to a writing schedule I create a project of my life. I put fixed-date tasks for all my travel, client commitments, vacations and anything else that I know will consume time during the writing process. Then I put in floating tasks for every chapter and have Project level my life (so to speak). This gives me at least a reasonable projection of how many calendar days it will take to do each chapter.

 

That’s pretty much it :)

Monday, February 13, 2006 8:01:01 AM (Central Standard Time, UTC-06:00)
Regarding Avalon, you don't have to hire graphic designers, you can use the default look-and-feel of the OS for the controls - like Windows Forms does.
Monday, February 13, 2006 9:09:31 AM (Central Standard Time, UTC-06:00)
Rocky,

Sounds like a hell of a lot of work but i'm glad that you put yourself through it. I'm really looking forward to the books.

I have to agree with your sentiments about companies paying for stuff though. I've lost count of the number of times i've come across organisations that want a bit of software developed from scratch but won't pay for the time taken to test it properly.

In my opinion that's a recipe for disaster and in the long term it's only going to cost them far more money than if they actually tested properly in first place.

When the books are done make sure you give yourself a rest!

ChrisD
Monday, February 13, 2006 10:49:45 AM (Central Standard Time, UTC-06:00)
I have no idea about other companies, but we've already started interviewing for a WPF designer. People with web development and graphical design skills (which are suprisingly common) seem to be fitting the bill.
Monday, February 13, 2006 2:40:40 PM (Central Standard Time, UTC-06:00)
Thank you for the determination to see the process through to the end. I appreciate the insight and the information.
Kurt Gulden
Monday, February 20, 2006 10:42:06 AM (Central Standard Time, UTC-06:00)
I do a lot software development for small companies, and from my experience only the high end projects get to hire a dedicated designer. But for the other 90% that are not high end, the developer gets stuck doing the interface work. Maybe that's why there are so many bad interfaces out there :)
Mitch
Saturday, March 18, 2006 10:08:41 PM (Central Standard Time, UTC-06:00)
Thank you for confirming that Word can actually work for writing full-length books (that's why I came to your site). I've researched this subject on the net and I found that most people dismiss Word entirely and suggest that something like Adobe's FrameMaker is the best for technical long documents. Adobe has a trial version for FrameMaker which may be a mistake on their part because after trying it I certainly wouldn't buy it. Their InDesign output is better but has far fewer features than Word for things like cross-references. The graphics part of book writing is frustrating (though SnagIt is amazing) and I plan to pay better attention to this and try to come up with a procedure and system/software settings that will work predictably. I'll report on that if I find something that works every time.
David Mc
Thursday, April 27, 2006 6:53:55 PM (Central Standard Time, UTC-06:00)
Who’d pay to make it pretty when they won’t even pay to make sure it actually works?!?

Marketing!
John Whattam
Comments are closed.