American library books Β» Education Β» Learn to write 101 by Kimberly Jackson (best historical biographies TXT) πŸ“•

Read book online Β«Learn to write 101 by Kimberly Jackson (best historical biographies TXT) πŸ“•Β».   Author   -   Kimberly Jackson



1 ... 3 4 5 6 7 8 9 10 11 ... 15
Go to page:
all, despite the fact I could call you stupid. A book is just a collection of 8,000 or so sentences. If you can write one you can write 8000. When anyone laughs at your book, just say β€œok, where is yours?” Then when they start to make up some excuse for not having one, hit them in the face (with your book).
Kim, who perhaps did not read the post, asked:
I know I can write; I live and breath to write. What completely douses my enthusiasm are the odds of getting published. That thought takes the wind right out of me!
To hell with publishers then. Go to kinkos. Go to lulu. If you are obsessed with someone else publishing your book your problem isn’t writing, it’s your ego. Self publishing gives you control over the odds.
Tereai said:
If the truth be told writing is natural. It cannot be taught. Thats why there’s a word called TALENT. If its not in you no matter how you force yourself it wont be as good as the naturals.
Who cares? The coolness of writing is you can revise. If you are willing to put in effort writing gets better as you work with it. I’d agree with you perhaps for figure skating or opera, but the tools for writing are available to all. And besides, name a talented writer who didn’t work. Name a natural. I’d bet you they didn’t see their process, discipline or effort as natural. They’d describe it, much like I did in the original post, as work.
MJ quipped:
The first is write the beginning.
write the end and then fill in the blanks !
As silly as this sounds, the first question I ask people when they ask about writing books is this: Have you written a page? And when they say no, I suggest perhaps their problem isn’t with writing books, it’s with writing a page. If you can’t write a page, don’t worry about books, worry about paragraphs.
If you missed part1, this will all make more sense if you go back and read it.


If you have ever thought, even half seriously, that you would like to write a practical book about computers or computer software, then you probably can. Moreover, given the proper editorial and publishing support, you can probably write a successful book. It's all a matter of doing the right things in the right order. And it helps a great deal if you have a publisher willing to do everything in its power to help you along. That is how we at O'Reilly understand our job.
The first thing that must happen, however, is for us to hear from you--your wild and crazy idea, or your carefully analyzed proposal. We may tell you that what you want to do is indeed crazy, or that your detailed analysis is off the mark. But then again, we may say, "Let's see what we can make of this thing." In which case, together we are off and running.
Overview of the Publication Process
But first things first. Here's an overview of the publication process, from beginning to end:
β€’ You send an email query to [email protected], asking if we're interested in a book on such and such a topic. Your query need not be a full proposal, but it should give enough of a sense of the book you want to write and your relevant skills and experience that we'll be intrigued enough to ask for a full proposal. Before sending a query, you should review our catalog or website to be sure that we don't already have a book on the topic you propose. If we do, but you think you have a new angle on an old topic, be sure to explain why your approach will be unique and valuable. Be sure to include the topic in the subject line. We hate queries and proposals labeled simply "Book Proposal."
β€’ We let you know whether or not we're interested in seeing a full proposal. Be warned that this may take a few weeks. We get thousands of unsolicited queries and proposals a year, and sometimes they get backed up. We'd like to be able to get back to you in a few days, but sometimes it takes quite a bit longer.
β€’ You submit a book proposal to us. Your proposal should contain an outline of the book, a discussion of who will buy the book and why, an analysis of any competing books showing why yours fills a real need in the market, and a tentative schedule. If you have not previously published a book, we would also like to receive a writing sample from you, though in some cases the proposal itself will serve as an adequate sample. For more information on what constitutes a good proposal, see Chapter Two of this document.
β€’ We consider your proposal, and perhaps talk it over with others who understand your topic. At this point, we might reach a simple decision, or else we might enter into a series of exchanges with you, asking for further information, seeking your opinion about problematic aspects of the book, inviting your response to criticisms, and so on. Eventually, this all leads to a go/no-go decision.
β€’ Having decided to run with the book, we sit down together with you and work out a contract. This might involve payment of an advance against royalties, and also places certain schedule constraints upon both of us. We like to think of ourselves as more flexible than other publishers--able to to accommodate the peculiar needs and conditions of a particular author or project. We always look forward to sitting down with you and "working it out." That being said, we want authors who are committed to getting the book out as planned. Some topics are more time-critical than others, and in some cases, missing the schedule will make the book unpublishable.
β€’ You are now ready to begin writing. You will probably use Microsoft Word, FrameMaker, or XML, although we can work with manuscripts in certain other formats as well. (Internally, we convert most books to FrameMaker before publication.) See Chapter Two for details on the accepted formats and for infomation on getting the appropriate templates from us. A particular editor will have been assigned to your book, and as you complete the first draft of each chapter, you forward it to your editor. He or she in turn will, as needed, provide editorial guidance, and you will be expected to revise the chapters you submit until the editor agrees that they are acceptable. In some cases, if the individual chapters you submit appear to be exceptionally well written, the primary editorial work may wait until the first draft of the entire manuscript is completed.
β€’ We then subject your book to a thorough editorial and technical review, calling upon experts in the field, as well as our own staff. In many cases, we may begin the technical review on a chapter-by-chapter basis before the first draft is complete; in other cases, we may wait for a complete draft before sending it out for review. It is then your responsibility to revise the book in accordance with the critical commentary you receive. There is much room here for some back-and-forth discussion, and many ways in which we can be of assistance.
β€’ When you have completed your revision, the book goes back to the editor. There may be some further, more rapid iterations of the edit/revision process now, but the hope is that we will soon have a book ready to go into production.
β€’ Our production and design people prepare the book for printing. This includes converting the material to its final format, putting it in the appropriate interior design, bringing the text and graphics together, final copy editing, and proofreading. You will have an opportunity to review the book before we send it to press.
β€’ Meanwhile, our marketing people have been getting out the word about an exciting new O'Reilly title. They will have contacted you early in the development process and asked you to fill out an author questionnaire, which asks you not only for information about you and your book, but also for your ideas about how and to whom we ought to market it. Now you will see the fruits of that dialog. There will be notice in our own catalogs and newsletters, together with reviews in trade journals and many other forms of advertisement. We may ask you to write articles promoting your book on our website, attend or even speak at trade shows or conferences, and participate in other promotional activities. Your willingness and ability to do these things can be an important factor in the success of your book.
β€’ All that remains, we fervently hope, is a long and successful sales run for your book! This sales run will be punctuated, most likely, by periodic revisions that will keep it at the forefront of current technology. If you are documenting a fast-moving technology, you might want to start planning immediately for how you will keep the book up to date.
A Word About Ourselves
If you have seen many of our books and catalogs, or have had dealings with us before, you will know that O'Reilly doesn't quite fit the usual publisher's mold. For one thing, few of us come from a traditional publishing background; we started as a small group of writers and engineers working primarily in Unix research and development environments. For another, our editors are "computer people"--remaining thoroughly immersed in the technical community. It is almost certain that your particular editor will be exercising the software you are writing about--if not testing your examples, or even rooting around in the source code.
This leads naturally to a certain "feel" of our books. We would like our readers to learn in the same way we ourselves have learned most effectively: by having the opportunity to look over the shoulder of an expert who is sitting at a terminal and carefully, patiently explaining how something works. And so we like our books to flow in a rather informal, helpful, and friendly manner. This is, after all, not incompatible with rigor and thoroughness. Expertise, yes; obscurantism, no.
This same style infects our own organizational manner. While our company has grown with extraordinary rapidity over the past twenty years, the "rules" governing our interactions with each other and with authors remain informal. It's just a question of focusing on the task at hand and working together to do whatever has to be done.
Our Major Book Series
Before submitting a proposal, it is worth familiarizing yourself with some of our major series, or types of books. These include:
"Animal" Books
To many of our readers, all of our books are "animal books"--after all, In a Nutshell references, Pocket Guides, Cookbooks, and Essentials titles all have animals on the cover--but internally, we think of the animal books as the the classic, in-depth O'Reilly books on specific topics. Our goal for each of these books is for it to be the definitive work on the program in question. Think Sendmail, DNS and Bind, or Programming Perl. Sometimes the title includes the words "Definitive Guide" or "Definitive Reference", and sometimes it will include a word like "Mastering," "Programming", or "Running", but it will usually include, in big letters on the cover, the name of the technology animal the book aims to tame.
If a topic is complex enough, we might approach it with several volumes -- for example, consider Learning Perl, Programming Perl, and Advanced Perl Programming. But this is the exception rather than the rule. More often, if the topic deserves more than one book, it is likely to be by way of "drill down" rather than by the addition of some audience-level modifier to the title. So, for example, we continued to expand in the Perl market by publishing ever more specific books, such as
1 ... 3 4 5 6 7 8 9 10 11 ... 15
Go to page:

Free e-book: Β«Learn to write 101 by Kimberly Jackson (best historical biographies TXT) πŸ“•Β»   -   read online now on website american library books (americanlibrarybooks.com)

Comments (0)

There are no comments yet. You can be the first!
Add a comment