How To Start Writing Your BOOK

Hi <>

Issue # 023, June 28, 2011

In This Issue:

1. Site Build It! works for me
2. Like our Page
3. Google +1
4. Get LET GO
5. Write a Book! Part 4
6. Spread the word

Site Build It! Works for Me. It can Work for YOU too!

Site Build it! works for me. It reduces the cost and complexity of creating a high-traffic website so much that anyone who knows how to use a computer can do it. Yes, Site Build It! works for me. It can work for you too. Give it a try. Now.

Site Build It! Can work for you too

Like Our Page

We have a cool page at Facebook up and running. We want to have a lovely community of writers from all over the world, united into one, big, happy family, merrily scribbling away!

Already we going at 64 likes. Now, I know that's far below the number of people subscribed to this ezine. So please, if you have not yet liked our page, please like it.

I know some folks don't like liking facebook pages, but ours is really worth liking. You are going to know why in a little while. Follow the link below to like us. PLEASE. I've even put a little smiley to go with it :-)

Lovers of Writing

Google +1 Buttons

Okay, google is getting smarter and smarter. They want all of you folks to participate in the ranking of pages, and identifying good quality content for their search engine. So,they've asked us to put their +1 buttons to our webpages. So, in a few weeks time, you are going to see +1 buttons springing up all over the place. It's going to be quite simple: If you like the page, you click on the little +1 button. It will help to create a google account if you don't have one. I'm really excited about all this. Aren't you?

Stay tuned for the +1 phenomenone.

Get LET GO

I am currently trying to self-publish my books. Depending on how successful or unsuccessfull this turns out to be, I will certainly make a decision on how I am going to manage the rest of my works.

I have one request from you. Please try and obtain a Hard Copy (Print) of 'Let G'o from Lulu. If you manage to get it, please get in touch with at my website (via the 'Meet Me' page), so that we can chit-chat about it (so that you tell me how cool it is, how nasty it is, how bad it looks and all....). I really need to see if this can work, so please help out if you can!

Follow the link below to obtain the book:

Write a Book! Part 4 : How To Start.

Got that great idea? Good. So you know what your book is going to be about? Okay, let us get the engines started...

Whoops! That's just the problem, right? You just don't know how to start, do you?

Yep, that's where the problem is for most people. A lot of people send questions to my website asking me how to start writing a story or book. And my answer is usually the same. Just pick up that pen of yours and start writing.

Okay, let me admit. It's not that easy.

Here's an analogy that might help.

In my Computer Science lessons, I have learnt about the approach programmers use to sort out a problem. We can also use it here to show how we can tackle this issue.

The first thing programmers do is to identify the problem that exists, after all, a computer program solves a specific problem. In the same way, you have to have a reason, a motive, a moral. What is the main idea behind your story? Once you establish that you are ready to move on to the next step.

After a programmer has identified a problem, he carries out a critical analysis of the problem, so that he understands it. He has to get it right. He has to know what exactly the problem is. Same thing applies to your writing. Identify the moral behind your story. Not only should you identify it, but you should also understand it. Asking the following questions may help achieve this objective: why am I writing this story? What is the motive behind it? What do I want my readers to learn from it?

Most of the time, if not all the time, the moral behind the story translates into the conflict of the story. The conflict is the problem that characters work to solve and gives life to the story. So this is a very important stage.

After thoroughly understanding a problem, the programmer comes to the next big step. He has to design a solution to the problem. Sometimes, he even has to draw charts so that the solution can be clear. The solution will show what data will make the inputs, what processing has to be done and what outputs are required. Most of the time, the design focuses on WHAT is expected and not on how it will be achieved.

For a writer, this is the critical stage. Coming up with a design. Most writers make draft. A draft is a plan, and most of the time, highlights the major events of the story. It can be very detailed, or it can be very general. It is a guide. It shows what events should occur and when; what characters are in the story, what they should achieve and when. Most importantly, a draft will identify the conflict and show the series of major events that will take place as the characters move towards solving the problem.

Once the design is up, the programmer will start the coding, that is, making an actual program that solves the problem. Yep, he starts the real work, getting all dirty and sweaty, figuratively speaking. He closely has to stick to the design. Note that oftentimes, the design does not specify exactly how to solve the problem, but specifies what has to be solved.

Same is true for writers. After having planned and created a draft of the story, he can begin to write. Yeap, the real dirty work begins. Watch out, it can get real mercy! He better stick to his plan or things can spiral out of control (but sometimes, that's for the better).

When the programmer has finished his coding, you would assume that it's over. He's done. The program is good to go. Not quite. Not really. He has to now test his program. He has to thoroughly test it to see that it does exactly what is expected of it. Same is true with the writer. After he has finished writing, it don't mean that's it. He has to go over his work to see if it is right. Sometimes he got to rewrite whole sections and the like, or start all over from scratch. It is tough, but.... he ain't no quitter. He's going to write and rewrite till he gets it right. And of course, he is going to get a little help from his friends the editors.

Finally, the programmer's program can be implemented. Yes, his hard work finally pays off and the users are merrily clicking away! For the writer, this point arrives when he sees his books on the shelves of book stores. Yippee!

Okay, I've said too much, but I am sure you've gotten the picture. So to summarize:

Figure out exactly what you want to write and how you want to write it. Plan. And then... start writing, sticking to your laid out plans.

But sometimes, things don't go quite according to plan do they? Or the plan can change, can't it? Hey, don't worry, there are no hard and fast rules. Just remember to have fun, and in the end, everything will work out--hopefully.

Stay tuned for the next article. I am going to let you in on some of the techniques I use to plan for my work. Some of them are really cool, if you know what I mean.

Don't miss the next exciting article!

Thanks!