I’ve been writing a technical book now since October 1st. I originally blogged about this with a post of the prospective index. Since I’ve gotten the first two chapters done and have started on the 6th, 3rd, and 4th. The reason I am doing these out of order is because of other related items I’ve had to work on related to presentations or the regular 9-5 job. There are a few things that have hit me while writing the book so far.
- The writing for me isn’t all that hard, it’s presenting the how-to parts of the book in a way that work smoothly. Directions are easy to write up, but making them fit into the larger idea of what is being accomplished is difficult. Keeping all the steps, screen shots, and other material in order when they’re not in one single document adds to this. I end up with a chapter directory, a word doc in that, another directory in that for images, and then another directory for edits from the editor and one inside that for final edits back to the editor. Needless to say it is a growing file structure of stuff.
- Jeff Barr wrote in My AWS Book is Now Available! that two things he learned is to set aside time and stay focused and disciplined. I’m learning that in spite of me already being aware that I needed to be focused and disciplined. I wanted to set aside time from the beginning but have been hitting a few snags with daily life and community tech events. I’m getting back on track now, but I’ve been a little behind on some segments.
- Be ready to write when you least want to. It doesn’t matter if you have writer’s block or your head hurts or your drunk, you have to write and get things to progress in a timely manner or things start to unravel. Be ready when writing a book to crunch late on some nights in order to get things back on track if a derailment occurs.
That’s my book update, for now, back to the writing.
I’ve decided to go for it. I’m going to write a book and today is the day that marks the beginning of this journey. I’ve read up and asked for advice from writers that have undertaken the technical book effort before. John Papa, provided some great information in the past, and even wrote a new blog entry related to some of those past efforts More Tips for Writing A Technical Book. The previous entries are great material too; 10 Things to Consider Before Writing a Book and 6 Great Tools for Writing a Book. I’ve read through these and am taking heed of the advice John gives.
Another blog entry I’ve come upon recently is by Bart Czernicki titled Technical Book Sales Insight Through Real-Time Amazon Rankings Analytics.
One of the things I’ll be doing, is blogging some of the notes, book sections, and other things to see if ordering, writing, and other bits work according to you the blog readers. With that in mind, I present my first table of contents. It’s a rough draft, but what do you think so far?
Title: Windows Azure Cloud Computing
Subtitle: From Enterprise to Startup, A Clear Path
1. The History & Ideas of Cloud Computing
a. Literal History of Cloud Computing
b. Modern Cloud “Services” Focus
c. Why Jump Into The Clouds
i. First, The Disadvantages
ii. Now, The Advantages
d. The 60k Ft. View of Cloud Architecture
i. Public & Private Clouds
ii. Enterprise, Startups, and More
iii. On Premises
2. Starting Windows Azure Development
a. What you’ll need, what you’ll want.
b. Other languages; Java, PHP…
c. Build a Cloud Site & Service with…
3. The Platform Elements of Windows Azure
a. Web Role
b. CGI Role
c. Service Role
e. …OTHER BITS
4. Architectural Patterns for Windows Azure
a. Queuing Patterns
b. Storage Patterns
c. Instance Patterns
d. Mixed On-Premises or Private and Public Cloud Patterns
e. Cloud to Cloud Patterns
5. Cloud Security
a. Physical Security of Facilities
b. Device & Data Security
c. Cracker & Social Engineering Security
d. Strategies for Additional Security
6. Business, Ideas and the Future of Cloud Technology
a. Super Computing for Anyone
b. SaaS is Ideal, but PaaS and IaaS are core.
c. Enterprise, Startups, and the Drivers of Cloud Computing
7. Closing – Summary & Appendixes