Welcome to www.minisinbox.com
|
Finishing a Masterpiece and Getting it on the Shelves
(how to get a book published)
Writing a book is a monumental task in itself. The process is long, drawn out and grueling. Even if you thoroughly enjoy writing and writing on the same subject for an extended period of time, you will no doubt be exhausted by the writing of a book. Getting that book published, however, will take even more time and effort than producing the thing in the first place. Are you thinking about writing a book? Have you already written one and now are just wondering how to get a book published? If you are, read on. Here are a few tips on how to get from the starting line to triumphantly crossing the finish line.
Writing that Book
When starting out writing your book, before you are ready to consider how to get a book published, you may already feel daunted. To write a successful book you need to start out with some original thought. You probably have plenty of originality, but you may have trouble getting your ideas into a coherent flow of information that will be digestible by the general public. The first step is to create a book skeleton. You need to organize your thoughts into a progression of chapters.
If your book will be non-fiction, start with a table of contents. Write chapter headings and sub-headings. You will automatically know that you’ll need an introductory chapter, but you should probably leave the content of your introduction for the last step. Organize your chapters so that they build upon one another. The more headings that you can brainstorm to begin with, the easier it will be to fill in your book with a series of short articles that flow into one another.
If your writing will be fiction, you will need more of a storyboard. You will need to create cause and effect as well as character sketches. To make your story coherent your characters will need events to react to. Their reactions should become predictable as your readers get into the story. You may need to create some situations for your characters just for the purpose of introducing their traits to the reader.
These are very general guidelines about how to begin constructing your book. The actual process will be much more involved as you move closer to finding out how to get a book published. Even after you are finished with the bulk of the content, your goal is still a ways off into the future.
Getting to Print
The next step in how to get a book published is finding a publisher. There are resources at your local library that will let you know who will be the best candidate for publishing the kind of writing that you do. After a series of queries and correspondence with the potential publishers you may get an invitation to send your manuscript. Then the work begins.
A publisher is very experienced in finding books that are marketable. He knows what it will take to get your book to sell. Don’t be offended when his editors tears your writing apart. If they are doing that, you can enjoy the fact that you are on the road to a published book. Expect to enter into a close relationship of compromise and change with the editor as you rework and rework what you have already so painstakingly written. When you are finished you will have a readable and clean and correct manuscript ready for print.
The road to getting a book published is a long one, but well worth the effort. Trust yourself, and trust the publisher to create a beautiful masterpiece. Don’t be discouraged if several publishers are not interested in your book. You may have to just keep the first few for yourself, and then again, they may eventually get accepted. Good luck and enjoy the process.
Web Hosting - Redundancy and Failover Among the more useful innovations in computing, actually invented decades ago, are the twin ideas of redundancy and failover. These fancy words name very common sense concepts. When one computer (or part) fails, switch to another. Doing that seamlessly and quickly versus slowly with disruption defines one difference between good hosting and bad. Network redundancy is the most widely used example. The Internet is just that, an inter-connected set of networks. Between and within networks are paths that make possible page requests, file transfers and data movement from one spot (called a 'node') to the next. If you have two or more paths between a user's computer and the server, one becoming unavailable is not much of a problem. Closing one street is not so bad, if you can drive down another just as easily. Of course, there's the catch: 'just as easily'. When one path fails, the total load (the amount of data requested and by how many within what time frame) doesn't change. Now the same number of 'cars' are using fewer 'roads'. That can lead to traffic jams. A very different, but related, phenomenon occurs when there suddenly become more 'cars', as happens in a massively widespread virus attack, for example. Then, a large number of useless and destructive programs are running around flooding the network. Making the situation worse, at a certain point, parts of the networks may shut down to prevent further spread, producing more 'cars' on now-fewer 'roads'. A related form of redundancy and failover can be carried out with servers, which are in essence the 'end-nodes' of a network path. Servers can fail because of a hard drive failure, motherboard overheating, memory malfunction, operating system bug, web server software overload or any of a hundred other causes. Whatever the cause, when two or more servers are configured so that another can take up the slack from one that's failed, that is redundancy. That is more difficult to achieve than network redundancy, but it is still very common. Not as common as it should be, since many times a failed server is just re-booted or replaced or repaired with another piece of hardware. But, more sophisticated web hosting companies will have such redundancy in place. And that's one lesson for anyone considering which web hosting company may offer superior service over another (similarly priced) company. Look at which company can offer competent assistance when things fail, as they always do sooner or later. One company may have a habit of simply re-booting. Others may have redundant disk arrays. Hardware containing multiple disk drives to which the server has access allows for one or more drives to fail without bringing the system down. The failed drive is replaced and no one but the administrator is even aware there was a problem. Still other companies may have still more sophisticated systems in place. Failover servers that take up the load of a crashed computer, without the end-user seeing anything are possible. In fact, in better installations, they're the norm. When they're in place, the user has at most only to refresh his or her browser and, bingo, everything is fine. The more a web site owner knows about redundancy and failover, the better he or she can understand why things go wrong, and what options are available when they do. That knowledge can lead to better choices for a better web site experience. Web Hosting - Bandwidth and Server Load, What's That? Two key performance metrics will impact every web site owner sooner or later: bandwidth and server load. Bandwidth is the amount of network capacity available, and the term actually covers two different aspects. 'Bandwidth' can mean the measure of network capacity for web traffic back and forth at a given time. Or, it sometimes is used to mean the amount that is allowed for some interval, such as one month. Both are important. As files are transferred, emails sent and received, and web pages accessed, network bandwidth is being used. If you want to send water through a pipe, you have to have a pipe. Those pipes can vary in size and the amount of water going through them at any time can also vary. Total monthly bandwidth is a cap that hosting companies place on sites in order to share fairly a limited resource. Companies monitor sites in order to keep one site from accidentally or deliberately consuming all the network capacity. Similar considerations apply to instantaneous bandwidth, though companies usually have such large network 'pipes' that it's much less common for heavy use by one user to be a problem. Server load is a more generic concept. It often refers, in more technical discussions, solely to CPU utilization. The CPU (central processing unit) is the component in a computer that processes instructions from programs, ordering memory to be used a certain way, moving files from one place to the next and more. Every function you perform consumes some CPU and its role is so central (hence the name) that it has come to be used as a synonym for the computer itself. People point to their case and say 'That is the CPU'. But, the computer actually has memory, disk drive(s) and several other features required in order to do its job. Server load refers, in more general circumstances, to the amount of use of each of those other components in total. Disk drives can be busy fetching files which they do in pieces, which are then assembled in memory and presented on the monitor, all controlled by instructions managed by the CPU. Memory capacity is limited. It's often the case that not all programs can use as much as they need at the same time. Special operating system routines control who gets how much, when and for how long, sharing the total 'pool' among competing processes. So, how 'loaded' the server is at any given time or over time is a matter of how heavily used any one, or all, of these components are. Why should you care? Because every web site owner will want to understand why a server becomes slow or unresponsive, and be able to optimize their use of it. When you share a server with other sites, which is extremely common, the traffic other sites receive creates load on the server that can affect your site. There's a limited amount you can do to influence that situation. But if you're aware of it, you can request the company move you to a less heavily loaded server. Or, if the other site (which you generally have no visibility to) is misbehaving, it's possible to get them moved or banned. But when you have a dedicated server, you have much more control over load issues. You can optimize your own site's HTML pages and programs, tune a database and carry out other activities that maximize throughput. Your users will see that as quicker page accesses and a more enjoyable user experience. |