February Needs More Days

We are experiencing scheduling difficulties. Please stand by.

Ever have one of those months where there just aren’t enough days? We all say that about February — mostly because it usually only has 28 of them — but even if it had its full share, it wouldn’t be enough. Mine is booked solid.

Want a glimpse of what my work/personal life is like right about now? Here’s the bullet point edition:

  • I have two chapters left to write on a book I’ve been struggling to finish since November. Part of the problem was that my editor didn’t seem to take much interest in the project, which led me to feel much the same way. Now, of course, they want it done already (as they should) and I also feel the same way.
  • One of my other publishers suggested a topic for a brand new book for them. I need to come up with an outline and make contact with the public relations person for the software company to see what kind of support I might be able to get from them.
  • That same publisher is gearing me up for a revision of my Mac OS X book for Lion. That book, which I also do layout for, has a brand new look, requiring a new template and mindset.
  • Another publisher is making noises about another revision for another project. I’m think it might be pretty far out on the horizon, but I need to chat with them about needs and scheduling.
  • AircraftOwner Online has announced that my monthly article deadline is now the 12th of the month rather than month-end.
  • I’m under contract to write two more articles (that I keep putting aside) for a Web publication. I won’t get paid for the first one I wrote (last year) until I hand in these two.
  • One of my aerial survey clients wants a 1-2 day wildlife survey flight in northern Arizona next week. (This just popped up today.)
  • One of my aerial photo clients has booked a 4-day photo flight in Arizona and Utah for mid-month. The flight requires me to obtain permits for flying low level in three different national parks. (And yes, one of them is the Grand Canyon. Wish me luck.)
  • I have to drop off my helicopter for its 100-hour inspection in Mesa, AZ; a few days later, I have to pick it back up. I also have to hope there’s nothing wrong with it that would prevent me from picking it up on time.
  • I have an FAA Part 135 check flight scheduled near month-end.
  • I have a day trip to Sedona scheduled near month-end.
  • I have a week-long vacation in the Bahamas with my husband. (A business trip for him; a chance to breathe for me.)
  • I have to drop off and then pick up Alex the Bird from his boarding facility before and after the vacation.

Get the idea?

You might have noticed that blogging does not appear anywhere on this list. That’s not a mistake. Blogging falls very low on the priority list. So low, it doesn’t even appear on lists. So this might be the only original blog post you see for quite a while.

Just thought it fair to warn you. This is going to be a very long short month.

And who says freelancers don’t work hard for a living?

Freelancers Don’t Get Sick Pay

We actually work for a living.

It occurred to me the other day that there’s a huge difference between employees and freelancers. I don’t mean to say that I suddenly saw the light — I didn’t. I’ve known the differences for a long time. But the other day, I actually stopped for a moment to think about them. I thought I’d share some of my thoughts here, laid out in a simple table to make comparison easier.

EmployeesFreelancers
Employees can stop looking for work once they get a job. The only times they need to look for work again is if they want to change jobs, they get fired, or they need a second job.Freelancers are always looking for work, even when they’re working. The ability to earn a living depends on having the next job lined up.
Employees seldom have to worry about losing their jobs to someone who claims he can do it cheaper.Freelancers are constantly competing for work with others who claim they can do the same job for less money.
Employees usual do one job at a time, although that job might entail several concurrent projects for the same employer.Freelancers often work on several jobs for several clients concurrently.
Employees are usually given all of the tools and equipment they need to perform their jobs. These tools are usually purchased, maintained, and updated by their employers.Freelancers usually have to buy, maintain, and update all of the tools and equipment they need to perform their jobs.
Employees often spend part of their workday socializing with coworkers around the water cooler, coffee room, offices/cubicles, cafeteria, etc.Freelancers often work alone. Most time spent socializing is not time they’re being paid for.
Employees often get benefits that include paid vacations, paid holidays, paid sick days, health care, pension contributions, profit sharing, and bonuses. There are holiday parties, company picnics, and sometimes even birthday cakes.Freelancers don’t get benefits. If they can’t work because of illness, they don’t make money. In the U.S. (and some other countries), they have to pay for their own health care, often at extremely high rates. There are no holiday parties, company picnics, or birthday cakes.
Employees have a predetermined workday, such as 9 to 5. They also get scheduled days off, like weekends and holidays. If they don’t feel like coming into work, they can take a paid sick or personal day off. The flip side of this is that an employee has a limited amount of time off.Freelancers work as long as they need to to get the job done. If that means 12 hour days and lost weekends, so be it. If they don’t feel like working in the middle of a job, that’s too darn bad; the job needs to get done on time. The flip side of this is that a freelancer can have as much time off as he wants, as long as he works enough to earn enough money to survive.
Employees are usually not bothered by their bosses outside their normally scheduled workday.Freelancers can be bothered by clients any time the client wants to make contact (although most clients keep contact within their working hours).
Employees can have annoying or even stupid bosses.Freelancers can have annoying or even stupid clients.
As long as an employee performs his job to some level of satisfaction, he’ll likely remain employed.A freelancer needs to perform high quality work for every job to set himself apart from the competition, with the hope that the client will either give him future work or recommend him to others.
Employees get paychecks. The government ensures that they get paid.Freelancers issue invoices and spend time following up on accounts receivable. They sometimes have to remind, nag, and then possibly sue clients to get paid.
Employees have payroll taxes taken from their pay and remitted to the government. In the U.S., their employers pay 50% of their social security tax liability.Freelancers don’t usually have taxes taken from their pay and remitted to the government. They are required to submit taxes quarterly, along with the related paperwork. If they don’t submit on time, they could be penalized. In the U.S., they are personally responsible for 100% of their social security tax liability.

What did I leave out? Employees and freelancers, use the Comments link or form to fill us in.

Is Writing a Book Like Riding a Bicycle?

Is it possible to forget how?

Despite all my blogging about Flying and helicopters, I still earn the bulk of my income as a writer. I’ve been writing computer how-to books since 1991 (depending on which book you consider my first) and have authored or co-authored more than 70 titles since then.

You’d think that by now I could write a book in my sleep. In a way, I can. Or at least I thought I could.

This past week, I began discussions with a publisher I’d never worked with before about two new titles. I you might expect — I certainly did — I was asked to submit an outline for each proposed book. I sat down with Microsoft Word’s outline feature on one laptop and the software I was going to be writing about running on a laptop beside it. And, for longer than I’d like to admit, I felt overwhelmed.

Writing a Book ≠ Revising a Book

Creating Spreadsheets and ChartsYou see, although I’ve got 70+ books under my belt, the vast majority of those titles are revisions. Two of them have been revised at least 10 times. In fact, on consulting my list of books, I realized that the last time I wrote a book from scratch was in 2004 (Creating Spreadsheet and Charts with Microsoft Excel: Visual QuickProject Guide for Peachpit Press), although I did co-author one (with Miraz Jordan) from scratch in 2006 (WordPress 2: Visual QuickStart Guide for Peachpit Press).

And revising a book is not like writing one from scratch.

When I revise a book, I start with the book and its text. There’s no need for a new outline. If the book will need major changes, I might take the existing book’s table of contents, bring it into Word’s outline feature, and modify it to fit the changes into appropriate places. But if the changes are minor — and believe me, quite a few revisions were like that — I didn’t even bother printing the table of contents. Either way, I go through each chapter and read the text, making changes as necessary. I re-shoot all the screen shots — even in books that have hundreds of them. I add sections and remove sections. Occasionally, I’ll move sections around or expand on sections to make them clearer. More and more often these days, I’m asked to remove sections simply to reduce page count. Then I’m done.

But when I write a book from scratch, I’m starting with nothing more than the subject — usually a software program or online service — and a blank outline page. I need to build the outline from scratch, knowing just a few things:

  • The audience. This is usually beginner to intermediate users; I don’t write for advanced users or programmers very often. Knowing the audience is important; it enables me to make assumptions about their experience and goals. My audience has changed in the 20 or so years I’ve been doing this. In the old days, I often had to begin with basics like how to point and click and close windows. Now I can assume my readers know all that and get on with topic-specific content.
  • The series. Most of my books are part of a book series. In the past, I’ve authored the first book in a series, but that’s not common. I like writing series books. They give me an idea of the style and format my editors want. I can visualize the final pages as I write. Heck, for some books — Peachpit’s Visual QuickStart Guide series, for example — I actually lay out the pages as I write.
  • The software or service. That’s my subject matter. I need to know the software or service very well to know what I’m going to write about. Often, I’m working with beta software that’s not quite ready for prime time or, worse yet, changes as I write. I have to explore menus and palettes and dialogs. I have to try things to see what happens. I have to learn so I can teach.
Don’t Torture Yourself
I always write with the software or service I’m writing about running on a second computer. Anyone who tries to write a book without being able to reference the subject matter while writing is putting himself through a lot of unnecessary torture.

The trick is to build an outline from the ground up, knowing where to start and where to end and how to get from one point to the next. Each chapter should have a logical flow, starting with the basics and moving on to more complex topics. I can’t explain how to perform one task until I’ve already explained how to perform the subtasks that are part of it. For example, I can’t write about formatting text until I’ve explained how to select the text to format and why selecting that text is important.

Have I Lost My Touch?

It’s this logical flow of things that had me stalled this week as I struggled with the two outlines. I seemed to have lost my touch. I couldn’t focus on the software and approach it as a new user might.

What made matters worse was that the editor I was working with gave me outlines to start with. I wasn’t sure whether he wanted me to follow those outlines or build my own. The outline for one of the books was very good. I wouldn’t have had any problem using it as a basis for my book. But I felt weird about using someone else’s outline — even if I had permission to do so. It was almost as if I were copying someone else’s work. I didn’t like that idea at all.

That meant I had to come up with an entirely different approach.

And that’s what stalled me. My mind went blank and I simply couldn’t think of another way to do it.

I’ve Still Got It

Putting the other outline aside and concentrating on the software is what saved me. I was eventually able to focus on the software. I started writing Part names, Chapter names, and A-Head names, following the style used in the series. I shuffled heads around. One thing led to another, just like it always had.

When I was halfway finished and clearly comfortable with my own approach, I consulted that other outline to make sure I covered all the applicable topics that it did. Since the other book was about the Windows version of the software (for the same publisher), only about 80% of the topics applied my Mac version book. My outline presented them in a completely different order, building skills along a different path.

Looking back on it, I realize that my outline is more like one of my outlines and wonder what I’d liked about the other outline in the first place.

Back on the Bicycle

I find it more difficult to write an outline than a book. That might sound strange, but it’s true. Getting the organization settled is the hardest part for me. Once I have that blueprint, I can start building pages.

With the initial period of uncertainty mostly behind me — at least on one of the two projects — I’m looking forward to writing a new book and working with new people. I’m hoping I get some good feedback from my editor on the outline and that we can work together to fine-tune it to meet the publisher’s needs. The contract comes next and then the writing. It’s all part of a workflow I’m quite familiar with.

Now if only I could knock out that second outline…