In Defense of Microsoft Word

It does the whole job.

About a month ago, I was having trouble with my Mac and decided to head off any serious problems by reformatting my hard disk and reinstalling all my software from original program discs. In the old days, before we all had hard drives measured in gigabytes, I did this every single time there was a major system software update. Nowadays, it’s a lot of work and I avoid doing it if I can. My 24″ iMac is just over a year old and shouldn’t have been giving me problems, but I figured I’d try the reformat before bringing it to a genius. (Turns out, it was the swapping out of 2 GB of RAM for 4 GB of RAM that probably fixed the problem.)

For some reason, I didn’t do a typical install of Microsoft Office 2004. I thought I’d save disk space by omitting the proofing tools for the languages I don’t speak — which is every language except English. Word, which I use daily, worked fine — until I noticed that it wasn’t checking spelling as I type. Although my spelling is above average, I count on Word to put red squiggly underlines under my misspellings and typos. No matter what I did, I couldn’t get this feature to start working.

I sent an update to my Twitter account about this as I went about troubleshooting the problem. The result was an outpouring of suggestions from my Twitter friends for replacing Word or Office with other software, ranging from Open Source Word or Office replacements to Google Docs.

Whoa!

I fixed the problem by uninstalling and then reinstalling Word. Life went on. But it got me thinking about Office and Word and why so many people go out of their way to avoid both.

Word and Me

I should probably start off by saying that I have been using Microsoft Word since 1989 or 1990. Although I got Microsoft Works with my first Mac, I soon learned Word and began teaching it in a classroom setting. It was Word 4 for the Mac in those days; I don’t know what the corresponding version in Windows was because I didn’t use it or teach it. I’m not even sure if Microsoft Windows was a player back then.

I’ve used every version of Word for the Mac since then.

My first book about Microsoft Word was The Macintosh Bible Guide to Word 6. Word 6 sucked. It was a processor hog. I remember working with it in beta as I wrote my book about it. I remember whining to my editor, asking if he thought they’d fix the performance issues before the software went out. They did, but not very well. I disliked Word 6 and the way it handled outlines and “master documents.” Everything seemed to be “embedded.” It seemed as if they’d prettied up Word to look more Mac-like and had done the job by pouring maple syrup all over the inside of my computer, bogging things down.

Word 98 was a vast improvement. From then on, each version of Word was an improvement. The interface remained basically the same but features were added and solidified. Some of the features worked with Microsoft server software, which I didn’t have, didn’t want, and certainly didn’t need. All I cared about was that Word did what I needed it to do, using the same interface I knew from years of experience as a user.

The End of the World as We Know It: Office 2007

Then Office 2007 for Windows came out with its ridiculous “ribbon” interface. What the hell was Microsoft thinking? Take a standardized interface that your existing user base knows by heart and throw it out the window. Force them to learn a whole new interface. Keep telling them that it’s easier and maybe a handful of morons will believe you.

I had to use Office 2007 for two Excel books. The only good thing I can say about it is that the complete, radical interface change — I’m talking menus vs. ribbon here, not spreadsheet basics — made a book about the software necessary. How else would users figure out how to get the job done? Fortunately (for users, not authors) Office 2007 adoption is slow.

Woe is Me: Office 2008

Word 2008 Splash ScreenOf course, I’m a Mac user and use the Mac version of Office. I held my breath when Office 2008 came out. Thank heaven they didn’t get rid of the menu bar — although I don’t understand how they could. Office 2008 retains much of the Office 2004 interface. It just adds what Microsoft calls “Element Galleries” and the usual collection of features that 1% of the computing world cares about. Fortunately, you can ignore them and continue using Office applications with the same old menus and shortcut keys we all know.

I would have switched to Office 2008 — I even had it installed on my MacBook Pro — except for two things:

  • Its default document formats are not compatible with versions of office prior to Office 2007. That means someone using Word 2003 for Windows or Word 2004 for Mac can’t open my documents unless I save them in an Office 2004-compatible format. This isn’t a huge deal, but it is something I’d have to remember every single time I saved a document. I’d also have to remember not to use any Office feature that only worked with Office 2007 or 2008.
  • It does not support Visual Basic Macros. One of my publishers makes me use a manuscript template that’s chock-full of these macros. Can’t access the macros, can’t use the template. Can’t use the template, can’t use Office 2008.

(I wrote about these frustrations extensively in a Maria’s Guides article.)

So I’m apparently stuck with Office 2004 — at least for a while.

But do you know what? I’m perfectly happy with it.

Why I Like Word

I like Word. I really do. It does everything I need it to do and it does it well.

Sure, it has a bunch of default options that are set stupidly. I wrote about how to set them more intelligently in an article for Informit.com. (Read “Three Ways Word Can Drive You Crazy[er] and What You Can Do About Them.”) It certainly includes far more features than the average writer needs or uses. And despite what Microsoft might tell you, it’s probably not the best tool for page layout (I prefer InDesign) or mail merge (I prefer FileMaker Pro). But it does these things if you need to.

I use all of the basic word processing features. I use the spelling checker — both as I type and to correct errors. I like smart cut and paste, although I have the ridiculous Paste Options button turned off. I like AutoComplete and love AutoCorrect (when set up properly). I use all kinds of formatting, including paragraph and character styles, tables, and bulleted lists. I rely on the outlining features when preparing to write a book or script for video training material. I use the thesaurus occasionally when I can’t get my mind around the exact word I’m looking for, although the word I want is usually not listed.

I’ve used some of the advanced features, such as table of contents generation, indexing, and cross-references. These are great document automation features. Trouble is, I don’t usually use Word to create documents that require these features. I use InDesign for laying out my books, which are usually illustrated. (And I admit that I’m looking forward to trying out the new cross-referencing feature in InDesign CS4 for my next book.)

I don’t jump on board with every new Word feature. I prefer the Formatting toolbar over the Formatting Palette. I write in Normal view rather than Page Layout view. I create my own templates but don’t use the ones that come with Word.

I don’t use the grammar checker; I think it’s a piece of crap designed for people who know neither grammar nor writing style. I don’t like URLs formatted as links. (Who the hell wants links underlined in printed documents?) I don’t use any of the Web publishing features; I’d rather code raw HTML than trust Word to do it for me. I very seldom insert images or objects or anything other than text in my documents. I have InDesign for serious layout work. I don’t use wizards. WordArt is UglyI think WordArt is ugly and amateurish. I keep the silly Office Assistant feature turned off.

I admit that I don’t use any of the project features that work with Entourage — although I’d like to. I decided a while back to switch to Apple’s e-mail, calendar, and contact management solutions (Mail, iCal, and Address Book respectively) because they’d synchronize with .Mac (now MobileMe) and my Treo. Entourage probably does this now, but I really don’t feel like switching again. Am still thinking about this.

The point is, I use a bunch of Word features and I completely ignore a bunch of others. The features are there if I need them but, in Word 2004, they’re not in your face, screaming for attention. (Wish I could say the same about Word 2008.)

iWork with Apple Computers

iWork '09Lots of people think that just because I’m a Macintosh user — an enthusiast, in fact — I should be using Apple’s business productivity solution: iWork. For a while, I thought so, too.

I own iWork ’08. I just bought iWork ’09. I’ve tried Pages. I’ve really tried Pages. I wanted to use it. I wanted to break free of Microsoft Word.

But old habits are hard to break. No matter how much I tried to use Pages each time I needed to create a document, when I was rushed, I reached for Word. No learning curve — I already know it. After a while, I just stopped trying to use Pages.

Why Use a Bunch of One Trick Ponies?

I know a bunch of writers who swear by one software program or another for meeting their writing needs. They use special outliners to create outlines. They use special “writing software” that covers the entire screen with a blank writing surface so they’re not distracted by other things on their desktops. They use special software to brainstorm, footnote, and index.

I’ve tried these solutions and do you know what? They don’t make my life easier. Instead, they just give me another piece of software to learn and keep up to date and interface with other software. They make more work for me.

I’m not going to forget my Word skills and Word isn’t going to suddenly disappear off the face of the planet anytime soon. In fact, it’s far more likely for one of these one-trick ponies to disappear than a powerhouse with millions of users worldwide like Microsoft Office.

Thought PatternI remember ThoughtPattern, a program by Bananafish Software. I saw it demoed at a Macworld Expo in the early 1990s and thought it was the greatest thing in the world for organizing my thoughts and ideas. I was sure it would make me a better writer. I was so convinced, I bought it — and it wasn’t cheap. I used it for a while and rather liked it. Evidently, I was one of very few people who’d joined the ThoughtPattern revolution. In April 1993, it was discontinued. I was left with software that wouldn’t work with subsequent versions of the Macintosh system software. Worst of all, the documents I created with ThoughtPattern were in their own proprietary format. When the software stopped working, the contents of those documents were lost. (Do you think it was easy to find a screenshot from software that was discontinued 16 years ago?)

So perhaps you can understand my aversion to one-trick ponies that promise a better writing experience.

Will the same thing happen with Microsoft Word? I don’t think so.

I Don’t Compute in the Cloud

Google Docs was one of the solutions suggested to me by my Twitter friends. I guess they think it’s better to avoid the evil Microsoft empire in favor of the “we’re not evil” Google empire. Along the way, I should give up the interface and features I know from almost 20 years of experience with the software and rely on an online application that could change its interface daily. Oh, yeah — and keep my documents on someone else’s computer.

Yeah. Right. Good idea.

Not.

Until I’m part of a multinational corporation that requires its employees and consultants to keep all their documents on some remote server for collaboration purposes, I will not be computing in the cloud.

One of the things I like about keeping my documents on my own computer — rather than a remote server accessible by the Internet — is that the Internet is not always available. What do I do then? Stop working?

Security is an issue, too. While I don’t usually write much of a confidential nature, I don’t like the idea of not having control over my documents. Servers get hacked. I don’t want my work suddenly accessible to people who I don’t want seeing it.

I will admit that I use MobileMe’s iDisk feature to keep some documents on an Apple server. This makes it a tiny bit easier to access them from my laptop when I’m away from home. But I’ve recently moved to a new strategy. I bought a pocket hard drive that’s bigger than my computer’s Home folder. Before I hit the road with my laptop on a trip for business or pleasure, I sync this portable drive with my Home folder. I then have every single document on my computer with me when I’m away. The added benefit: complete offsite backup.

That’s My Case

That’s my defense of Microsoft Word. I rest my case.

Please understand that I’m not trying to convince a non-Word user to switch to Word. If you’re happy with something else, stick with it! That’s the precise reason I’m sticking with Word. I’m happy with it.

I guess the reason I wrote this post was to assure other people like me that there’s no reason to be ashamed of being a Word user. You do what’s right for you. There’s nothing really wrong with Word. If it makes your life easier, why switch?

Microsoft Flight Simulator X For Pilots: Real World Training

A surprisingly good training aid.

I just want to take a moment to heap some praise on a computer book I’ve found very helpful with my recent Instrument flight training studies: Microsoft Flight Simulator X For Pilots: Real World Training by Jeff Van West and Kevin Lane-Cummings.

The book is, on the surface, a user’s guide for Microsoft Flight Simulator X (FSX), a Windows PC program that supposedly simulates flight in different aircraft. (I have issues on the realism of its simulation, as I reported here.) It takes you through the pilot ratings, one at a time: Sport Pilot, Private Pilot, Instrument Rating, Commercial Pilot. But instead of flying a real plane, you’re flying a simulated plane in the software.

What’s amazing about this book is its ability to communicate valuable and real information about flight training and knowledge required by pilots. I’m concentrating on the Instrument Rating chapters in the second half of the book. I read the first two chapters of that part yesterday and learned more about making departures and planning en route flights using real FAA charts than I did in three days trying to decipher the same charts with other study material.

The book’s text is clearly written and easy to understand. Best of all, it doesn’t put me to sleep — which is always a challenge, since I do most of my reading in bed at night.

While I can’t comment specifically on the exercises to be followed with FSX since I’ve been skipping them, if they’re half as good as the background information, the book is an excellent source for anyone interested in learning to fly using FSX as a training aid. I look forward to finishing the Instrument Rating chapters. And, with luck, I’ll be able to try a few of the exercises myself using the FSX software.

From one computer book author to others: Good job, guys!

Microsoft Flight Simulator — for Pilots?

Realistic? Are they kidding?

Yesterday, I received a flurry of packages delivered by USPS, FedEx Ground, and FedEx — all within 30 minutes of each other. Inside were Christmas presents from my family.

The Benefit of Having an Amazon.com Wish List

I maintain an Amazon.com Wish List. I use it primarily to store the items I’d like to buy but don’t want to buy right now. But it also makes a handy way for family members to send me gifts at Christmas time. There are items there ranging in price from about $10 up to $200 or more, and ranging in type from books and music to movies and electronics and housewares. So whether someone is shopping by price or by type of item, they can find me something I really want.

This year, my mother, sister, and brother decided to dip into the list. And because I told them not to pay extra for shipping if free shipping was available, most of my Christmas gifts arrived after Christmas.

Yesterday, in fact.

My First Computer Game in 10 or More Years

Product ImageAmong the items on my list was Microsoft Flight Simulator X Deluxe. On the surface, that may seem like a pretty average gift for a pilot. But I’m a helicopter pilot and I normally use Mac OS computers. FSX (as it’s apparently nicknamed by its cult of users) runs on a Windows PC.

I’d asked for this to help me with my instrument rating, which I’m working on this winter. A flight instructor had suggested it to help me with my “scan.” The scan is an important part of instrument flying — it involves scanning a certain group of instruments in a certain order or frequency to maintain situational awareness and keep the aircraft from doing aerobatics in the clouds with you on board.

Although I’m a Mac user, I do have a PC. Each year for the past 10 years, I’ve written a book about Quicken for Windows. [Greetings Google Alert scanners at Intuit!] I did a Mac version for a few years, too, but sales weren’t impressive enough for the publisher to keep doing it. I’ve also used PCs when writing about Microsoft Office products. In fact, I did two Microsoft Office Excel 2007 for Windows books in 2007. So although I don’t really like using PCs, I have one — a Dell laptop everyone who knows about PCs seems to be impressed by — and I do know how to use it. And since it’s sufficiently loaded to run Vista in all of its questionable glory, I didn’t think it would have any trouble with FSX.

My brother and his wife got the software for me. This makes sense. My brother is a big Windows PC gamer and spends hours fighting wars on the Internet. (Ah, if only that were enough to satisfy world powers!) He’d asked for a bunch of components to load up his PC, but I was a more practical gift giver this year and sent him and his wife Home Depot gift certificates to help them fix up their kitchen, which really needs work. Oddly enough, I’ll probably give him this game when I’m finished with it.

I mentioned in the subhead that this is my first computer game in 10 years. I’m estimating. My first computer game was Myst, which I found interesting, if not a little spooky. I followed that up with the sequel, which I don’t recall actually playing. That’s the extent of my game experience. I’m not a gamer; I don’t believe in spending hours in front of a computer entertaining myself. I’d rather read a book or do something more constructive with my time.

The Flight Simulator

Product ImageI installed FSX last night. It took nearly an hour to copy the 15GB of data from two DVDs to the Dell. While it installed, I perused another gift from my Wish List, Microsoft Flight Simulator X For Pilots Real World Training. My mom sent me that one and it arrived yesterday, too.

This book is a big, fat, extremely well thought out volume that explains how to fly, using FSX as a training tool. It assumes you know nothing about flight but want to learn. It then teaches you from the ground up (pun intended), using accurate descriptions, illustrations, and features within FSX. It has chapters that take you through all the ratings you might want: sport pilot, private pilot, and instrument rating. It’s the instrument rating chapters that interest me and they look very complete.

The only problem is, the book — and the software, for that matter — assumes you want to fly airplanes.

I don’t fly airplanes and I don’t want to learn.

FSX comes with two helicopters: a Robinson R22 Beta II (which I’ve already customized with the N-number of my old helicopter) and a Bell 206B JetRanger. So rather than mess around with the airplanes, I went right for the R22.

And crashed it numerous times.

I have to mention here that when you’re a 2,000-hour pilot and you’re manipulating the controls of a virtual aircraft and can’t keep it in control, you can get pretty freaked out.

The problem is, the controls are not sufficiently realistic. In a helicopter, when you move the cyclic, you get immediate feedback. Push it forward, the nose immediately dips. Push it to the right and the aircraft immediately starts to bank. And you don’t have to push very much, either — a little dab will do ya (with apologies to Brylcreem). Although there might be delays of a fraction of a second in different helicopters depending on hydraulics or rigging, a pilot can get the “feel” for these minor differences within a few minutes and be able to fly.

But these delays were not fractions of a second. The delays between control input and aircraft reaction had to be at least two or three seconds. While a non-pilot might think that two or three seconds delay isn’t such a big deal, it really is — when it’s not what you’re accustomed to. I’d make a control input and, when nothing happened right away, I’d make a bigger input. By that time, the first input was just starting to take effect and the second would send the aircraft careening out of control. Too much correction and it would be headed the other way.

If I climbed into the cockpit of a real-life helicopter today and it had lag time like FSX’s R22, I’d crash it, too.

R22 PanelThe details inside the cockpit, on the other hand, are amazingly accurate, from the vertical card compass (not shown here) on the split cockpit bubble to the instrument panel — although this particular configuration is not one you’re likely to find on a real R22. (The instrument in the bottom center is normally found on Instrument trainers, which have a larger panel with more instruments.) The realism of the scenery, airports, etc. is also pretty good. This screenshot has everything set to low quality graphics — I’m trying to realistic performance — but when you crank it up a few notches it looks pretty darn good. (Of course, there aren’t any houses near the runway at Phoenix Sky Harbor.)

As I type this, I’m downloading a 213MB update to the software. I’m hoping that the update, as well as finding the power cord for the Microsoft Force Feedback Joystick we have (from Mike’s old Flight Simulator days) will work together to make these aircraft fly more realistically.

I’m simply not willing to re-learn how to fly just to get practice on a computer — when I can go out and fly the real thing for a lot more benefit.