Public Opinion

I realize that public opinion doesn’t really matter.

I run a Web site called wickenburg-az.com. Its primary purpose is to provide information about Wickenburg, including things to do and see and businesses that operate here in town. I built the Web site because there was no non-commercial Web site about the town. Basically, if you wanted your business on the Web, you had to cough up big bucks to get it on one of the commercial sites in town — sites that weren’t even updated on a regular basis. I didn’t think that was fair. I also didn’t think any of those sites provided useful information for residents or visitors.

Over the years, the site has become quite a forum for voicing opinions about the way things are going here in town. I admit that I started it. Then John started adding his two cents and since what he submitted was well-written and well-reasoned out, I couldn’t help but publish it online. Along the way, a handful of other people submitted articles and I published them. I felt that these opinion pieces helped round out the site.

Recently, I’ve gotten quite a few opinion pieces from people I’ve never heard from before. I’ve been publishing most of them. Others are a bit over the top, even for me. What amazes me, however, is how many people have written to say they agree with much of what appears on the site — even though these opinions aren’t what’s reflected in the local newspaper or among local politicians.

In other words, the town’s government is pushing one way on many issues and the newspaper is rubber-stamping their decisions. In the meantime, many people don’t agree with or even like what’s going on.

This has me a bit baffled. My understanding is that in a democracy, when the people vote, they are choosing the elected officials that stand the same way they do on most issues. When they vote on a proposition, they’re telling their elected officials that they either want it to pass or they don’t. It seems to make sense that the elected officials would do the things that their constituents expect them to, based on popular opinion. It also seems to make sense that if a proposition fails, it would simply fade away into obscurity — not be put up for another vote when a different collection of people were around to vote on it.

Sadly, that’s not the way democracy works in Wickenburg. Majority public opinion seems to have little or no bearing on what actually happens in town. Elected officials do whatever they want to, for whatever reasons strike their fancy. I still haven’t decided if they’re motivated by greed — money under the table and other reward promises — or stupidity — being led around by the nose by smooth-talking developers.

The bypass issue is a perfect example. This has been going on for years. The route 93 and 60 corridor has become a major thoroughfare for traffic between Phoenix and Las Vegas and will be part of the Canamex highway that will link NAFTA members Canada and Mexico. As a result, there is a huge amount of truck traffic going right through town.

ADOT brought consultants into town on a regular basis to meet with the public and gain their opinions on the dozen or so options. The public clearly favored an out-of-town bypass that would keep all those trucks south and west of town. Yet the local government and chamber of commerce favored a route that would put the traffic right through town. (I guess it was important to them for McDonald’s and Circle-K to keep selling burgers, coffee, and gas to the drive-through crowd.)

As a result, the “interim bypass” was developed. This monstrosity would put four lanes of traffic along the riverbed near the existing bridge — it isn’t clear yet whether they’ll build another bridge, too — and route that traffic right past the Community Center and Coffinger Park, through a neighborhood and a ranch (thus displacing dozens of people and destroying the values of the remaining homes), and deposit it back on 93 right where a local developer is attempting to build a high-priced housing development. (It will be interesting to see how many people will pay $800K+ for a house overlooking 4 lanes of truck traffic.) Along the way, this crazy plan calls for two “roundabouts” — the old-style traffic circles that are being dismantled throughout the east — so that our “winter visitors” (most of whom are in the 65+ age bracket) can merge with the trucks on their way to and from Wal-Mart in Surprise. (It might be a good idea to move the ambulance base to that intersection, since that’s where it’ll be spending a lot of time.)

All this is completely against the majority public opinion. People who live in Wickenburg year-round care about the town and its atmosphere. We don’t want highways in the riverbed where exhaust fumes will settle and noise will destroy the quality of life and whatever downtown ambiance we still have.

We also don’t want high-density housing, especially when there aren’t enough high-paying jobs to fill those homes with year-round residents. We don’t want an economy that centers around winter visitors who don’t even like to spend their money in town. We don’t want two Dollar Stores or two check cashing places or a pawn shop. We want businesses that will provide good jobs and the goods and services we need.

But in Wickenburg, public opinion doesn’t matter.

Finished “Mac OS X 10.3 Panther: Visual QuickStart Guide”

Thoughts and insights on a tough revision and the computer book publishing industry.

Mac OS X 10.3 Panther: Visual QuickStart GuideMy last entry was pretty depressing. I was under a lot of stress to get the book done. Now that it’s done and the stress is gone, I’m feeling much better. The book is nothing short of a masterpiece, if I do say so myself, and I’m extremely pleased with it. We (Peachpit Press and I) got a lot of feedback from readers about previous editions. It seemed that my VQS wasn’t considered “good value for the money” because it didn’t have as many pages as other competing books. What most people didn’t consider was that VQSes are traditionally short (around 300 pages). Mine was actually long at about 400 pages. And it was considerably cheaper than the other books. But I guess if you calculated price per page, I probably fell a bit short of the competition. And I can’t deny that buying two books (a VQS and a VQP) does cost readers more money. In defense of Peachpit, the idea behind that strategy is that not all readers need all that information and we could provide affordable books tailored to two markets. But that’s not how reviewers saw the situation.

That said, we decided to combine the two books into one title. The resulting “Mac OS X 10.3 Panther: Visual QuickStart Guide” is about 670 pages long and features 20 chapters and over 2,000 screen shots. Topic range from the most basic basics (like how to point and click) to Unix commands. The price tag is an extremely competitive $29.95 US, making it a very good value. If this book doesn’t please readers, I don’t think any book will.

Writing the book was a bit of a challenge. First, there was the merging of the content from two books. What do we include? What do we exclude? Not much. The biggest casualty was the AppleScript chapter written by Ethan Wilde, which was replaced by an AppleScript basics section in the Applications chapter. (Those interested in AppleScript really ought to buy Ethan’s book!) Almost everything else that was in my Mac OS X 10.2 VQS and VQP remained in this edition.

Of course, everything has been updated for Mac OS X 10.3 Panther. That was the second challenge. Not just the update, but merging information about new features into existing chapters. Where do we discuss each new feature? Chapter 4, which is available as an excerpt from my Web site , got quite a few new pages. So did the i-Applications chapter, which was expanded to cover iCal and iSync (neither of which was available when I wrote the Mac OS X 10.2 VQS last year). The only chapter that got trimmed down a bit was the installation chapter. I cut out the info about installing Mac OS 9.2, since that information appears in the Classic Environment chapter.

There was a lot of pressure to finish the book on a timely basis. Timing is everything in the computer book publishing world and when a hot new product hits the market, publishers want their books out first. Trouble is, authors have to work with beta software, which often changes on a weekly (if not daily) basis to get the book done timely. Mac OS X 10.3’s beta software was available for about two months before the software was finally released. But the beta software changed. Any author who wrote about early versions of the beta wrote some stuff that isn’t right.

Want some examples? The first beta or two included a Print command under the Finder’s File menu. That command disappeared before I could try it out. Those first betas excluded a Favorites folder in the Sidebar. Sometime in the middle of the beta process, the Favorites folder reappeared. Then, near the end, it disappeared again. It was almost as if Apple wanted to kill favorites, thought they would get a lot of negative feedback, and then decided “to hell with the bad feedback” and killed it. (But favorites aren’t really gone, as you’ll discover when you read my book.) Icons changed, too. Internet Connect’s new icon didn’t appear until halfway through the beta process. Any screenshot of that icon taken before the beginning of October will be wrong.

So here’s the situation: publishers want the book written quickly. Once the book is written, it has to be laid out, proofed, edited, and printed. For most publishers, this is where time is lost. From the moment the author hands over the last manuscript chapter and TIFF files to the time the book appears in print, two or more months may have gone by. So do the calendar math: if the author waits until Gold Master of the software — on or around October 15 in this case — to finalize the draft manuscript, the book can’t possibly appear in stores until December 15. So what do authors do? Under pressure from publishers, they finalize before Gold Master. As a result, their books contain inaccuracies.

Peachpit and I don’t work this way. We have a remarkable arrangement. I do layout as I write, so I submit fully laid out pages as I work. My editors mark up this draft manuscript and I update pages as the software is changed and I get edits. As a result, when the software went Gold Master, we already had fully laid out pages for about 3/4 of the book. I wrote and laid out the rest the following week. This made it possible to send our completely accurate 650+ page book to the printer only three days after the software’s release date. I expect to hold a copy of the finished book in my hands by November 14 — just three weeks after the software’s release.

Any book that makes it to stores before mine can’t possibly be based on final Mac OS X 10.3 software. It’s just impossible. And that’s not an author’s fault. It’s the fault of publishers who don’t trust their authors to do layout. Peachpit trusts me and I don’t let them down.

Next on the agenda, Excel 2003 for Windows: Visual QuickStart Guide. Another revision — but this one should be a piece of cake.

On writing Mac OS Visual QuickStart Guides

Sometimes I feel like a machine.

Pardon me, but I’m about 2/3 of the way through the largest Visual QuickStart Guide I’ve ever written. This is book #55 and the sixth or seventh (I’ve lost count) edition of my bestselling Mac OS VQS for Peachpit Press.

The first edition covered Mac OS 8, years ago, and it was an instant bestseller. People were hungry for books about the new Mac OS software and mine was the only book available at Macworld Expo (although in limited quantities) when the software went on sale. It was three weeks before the second book came out. That was a nice competitive advantage.

The book went through some changes throughout the year. It got fatter and fatter with every edition until we decided to split it into two books, a Visual QuickStart Guide (VQS) and a Visual QuickPro Guide (VQP). The VQS got skinny all of a sudden, then started to fatten up again. The Mac OS X 10.2 edition is about 370 pages and the corresponding VQP is about 350.

Simple math should have told me that when we recombined the two books into one big fat VQS, the resulting book would be VERY FAT. I’m estimating about 650 pages right now. I was wondering a while ago why this book was taking me so long. It’s because I’m really writing two books that’ll fit between one set of covers.

And I do feel like a machine. I have the VQS thing down to a science. Two computers, one to work with the software on (an eMac “test mule”) and one to write on (a G4 “production machine”). A network connection dumping screenshots into my production machine. InDesign and Photoshop running all the time. Templates, libraries, style sheets. I can produce a page from scratch in about 30 minutes (if I don’t have to take time to figure out what I’m doing) and can revise a page in about 15. I’m a machine.

And I’m very tired. Burned out. Sick of taking screenshots and laying out captions and callouts.

I start work at 6 or 7 AM and work until I’m done with whatever I’m working on. Sometimes that means working until 6 or 7 PM. That’s a long day. But most days, I quit by 4 PM. Then I go home and try not to think about computers.

But I do admit that I still get a thrill out of seeing a good book in print. A “good book” is a book that I feel that I’ve done my best on. This book will be a good book. Well, at 650+ pages, it’ll probably be a GREAT book. And a real bargain for readers.

More another time. I’m going home.