What is the best way to organize a complex or chaotic topic into an organized whole? I'd be grateful for practical solutions people actually used to complete a book. Thanks.
Ask HN: How do you write a book?
1–10 of 27 posts
Re: Ask HN: How do you write a book?
#2Notepad
Re: Ask HN: How do you write a book?
#3I'm going through this right now for nanowrimo. ;)
At first I used word (very lame, I know), but a friend recommended Scrivener (http://www.literatureandlatte.com/scrivener.html) to me a while ago, and I've been using that instead, but it's an OS X only tool. I love it. I'm not a writer, but I really needed some tools to help me finish nanowrimo, and scrivener is it.
I've occasionally used mindmapping tools for occasional papers I've written, if it's extremely chaotic you may want to look into that, although I don't know how much help it might be.
Re: Ask HN: How do you write a book?
#4Just start writing, using whatever works best for you. I've been using TextEdit on the mac a lot lately for my writing, but anything's good.
If you're writing for a publisher, then they're going to give you a template that's probably for Word, and you don't have to worry about complicated document struturing stuff -- they'll help with the referencing, etc.
If you're doing it all yourself, then a document description system such as LaTeX might be the way to go. If I was writing a technical book that i knew had little chance of being published, I'd probably use that.
Re: Ask HN: How do you write a book?
#5I always like to start with a mindmap (http://en.wikipedia.org/wiki/Mind_map) of the key points. Once I have those, I flesh out the individual nodes underneath. I then organize into Chapters/sections and start writing.
I've read where some people create a PowerPoint presentation and work backwards from that as well. The key thing for me is that I don't want to get tied down to Chapter 1, Chapter 2, etc too early - I want the flexibility to move things around without hindering my thinking process. That's the sort of thing that is perfect for mind mapping tools like FreeMind (http://freemind.sourceforge.net/wiki/index.php/Main_Page).
Re: Ask HN: How do you write a book?
#6The advice I've gotten: Write a book proposal. In it, lay out chapters with one or two paragraph summaries. The process forces you to think a lot about organization. It also provides a blueprint/outline for you going forward. You'll see how the ideas fit together to recognize missing gaps in your thesis. Keep in mind that it's an evolving document and as you write more you'll be better able to incorporate new material and scrap old forks. Starting with the summary provides clear signposts along the way.
Good luck!
Edit: Of course, I forgot the reason why many folks also write a proposal: To shop it around, get an agent, and an advance. Problem is, that usually requires some connections in the industry, special expertise, compelling story, and/or all of the above. You don't need to shop it around to get the benefits, though it's nice to have if you happen to run into someone who could help.
Re: Ask HN: How do you write a book?
#7Just start writing, using whatever works best for you. I've been using TextEdit on the mac a lot lately for my writing, but anything's good. If you're writing for a publisher, then they're going to give you a template that's probably for Word, and you don't have to worry about complicated document struturing stuff -- they'll help with the referencing, etc. If you're doing it all yourself, then a document description…
"Just start writing" is pretty terrible advice for writing a non-fiction book. The greatest value of such a book is in the synthesis of the subject at hand... without high level organisation, that synthesis simply won't be. Chaotic, messy non-fiction is terrible.
Fiction writing, on the other hand, can go totally chaotic... but I imagine the OP is talking about non-fiction.
Re: Ask HN: How do you write a book?
#8Just start writing, using whatever works best for you. I've been using TextEdit on the mac a lot lately for my writing, but anything's good. If you're writing for a publisher, then they're going to give you a template that's probably for Word, and you don't have to worry about complicated document struturing stuff -- they'll help with the referencing, etc. If you're doing it all yourself, then a document description…
"Just start writing" is pretty terrible advice for writing a non-fiction book. The greatest value of such a book is in the synthesis of the subject at hand... without high level organisation, that synthesis simply won't be. Chaotic, messy non-fiction is terrible. Fiction writing, on the other hand, can go totally chaotic... but I imagine the OP is talking about non-fiction.
Actually it is ok advice taken as the first step. Write to see what you think. Then rewrite, rewrite, rewrite.
Re: Ask HN: How do you write a book?
#9"Just start writing" is a fiction thing.
The nonfiction equivalent is "just start writing index cards."
Re: Ask HN: How do you write a book?
#10The advice I've gotten: Write a book proposal. In it, lay out chapters with one or two paragraph summaries. The process forces you to think a lot about organization. It also provides a blueprint/outline for you going forward. You'll see how the ideas fit together to recognize missing gaps in your thesis. Keep in mind that it's an evolving document and as you write more you'll be better able to incorporate new materia…
I've just finished writing a book that will be published by O'Reilly next year. I'd echo your comments:
1. Write an outline. This is boring, but vital. If you don't do this you won't realize that extent of the task you are taking on. By writing an outline you are convincing yourself and a publisher that you can actually write a book.
2. Do some other writing first. For example, I wrote extensively for different magazines. This is both good practice and gives you sample writing to show to a publisher.
3. "Phone a friend" Do your best to find someone you know who can introduce you either to a publisher or to an agent. This also applies to getting VC funding, it's best to find some way in via someone your know (or someone someone you know knows) than just trying to cold call.
4. If you do get a contract track carefully your progress (I used a spreadsheet) so that you stay on target.
5. Do not get hung up on the right tools to use. I've written plenty of stuff in a text buffer in emacs, or in Word, or using a specialist XML editor. Your publisher may actually ask you to use a specific tool, and the reality is that the tool is the least important part of the process. Figuring out what to write, and then writing the sentences is hard. (I'm not joking about the last part)
6. Read your work aloud. After I'd written a section I would read aloud what I'd written to see how it flowed. And I'd modify, read aloud, modify, read aloud until it seemed smooth.