3 ms·
"#1 is the most important point. I've worked as a writer, and I'm currently working on several of my own projects, and I can say from experience that for certai
by jamesbritt 17y ago
"#1 is the most important point. I've worked as a writer, and I'm currently working on several of my own projects, and I can say from experience that for certain projects 1,000 words can take much more time and effort than 20,000 words."
Random thoughts:
I've written for books and magazines, and indeed there's extra work in being concise. But there's also great value in that, too, when done right.
If you don't already know if you like writing, then you probably don't like writing, or else you would be doing it and liking it.
Not all chapters are equal. The trouble is in knowing if your sample chapter is a proper sample of the book as a whole. However, if you find it hard or tedious, stop right away.
It's probably best to write about something you already know and love, but beware the pitfalls in explaining what you've by now internalized to some newbie. There's a good chance you've forgotten how odd or quirky many things are, and you really don't want to discover this at the point you are trying to explain it.
Good examples are hard. Most tech books have questionable example code. On the one hand, they need to be reasonably brief; on the other, they should not be contrived. I tend to prefer walking the reader though a longer code base spread out over chapters, as it will more likely match real-life code.
Very few authors make money off books. There's a good chance that for the time spent you would do better to wait tables. Be clear on why you are doing this, and realistic on what to expect. It can be fun and rewarding.