Tag Info

Hot answers tagged

4

The question is who you want to write for. I read one of the major daily newspapers of my country every day. The articles appear well researched (and are well written), and I feel I learn something reading them. But whenever an article deals with a topic in which I am an expert myself, I see many flaws: false information, central concepts not touched upon, ...


3

I've written manuals under a Scrum process, so I'll describe what worked for my team. I'm going to treat your task as if you're writing a new book. From your description, you'd be replacing the vast majority of the content anyway, so better to think of it as a new book (for which you might be able to take advantage of the occasional previously-written bit) ...


1

Gee, I agree with what. You need a specialist. Something that helped me, though (I was a perfectionist, too) is this quote: "Art is never finished, only abandoned." - Leonardo da Vinci Give up perfection. Look at your writing as something that improves incrementally rather than something that is fixed. You can always come back and edit later; something ...


1

I don't have any experience with cowriting, so take my advice with a grain of salt. But I have two thoughts: First: If you're relatively new to writing (it sounds like you have yet to write your first novel), then I think there's probably a period of self-discovery and learning ahead of you. If your coauthor says "let's do X", but you don't have the ...


1

The idea of letting the developers write the notes will shatter on the cliff of reality. Most developers don't want to write them, so even if you force them somehow, you will only get a mess and not a note. Just for the record: I am a developer. What you can do is just improve your existing workflow a little bit. A little bit often does wonders and you will ...


1

In order of descending utility, IMO: Project/feature/bug tracking software, for well-defined product changes. A must. Email notification to other writers (broadcast) that refers to entries in #1 or to a wiki entry describing the doc change. The email summarizes the context & change enough that other writers can tell whether it affects them. The wiki ...



Only top voted, non community-wiki answers of a minimum length are eligible