Post History
IDE-like tools exist for writers. Scrivener is a powerful general-purpose tool (also with questions here). Madcap Flare, aimed at technical writers, has good support for updating links, defining "s...
Answer
#4: Post edited
IDE-like tools exist for writers. Scrivener is a powerful general-purpose tool (also with [questions here](https://writing.stackexchange.com/questions/tagged/scrivener)). Madcap Flare, aimed at technical writers, has good support for updating links, defining "snippets" (xinclude blocks, essentially), variables, conditionalization, advanced build options, and more. Arbortext Epic is another tool in that vein. There are XML editors like Oxygen and Notepad++ that you are probably already familiar with as a programmer. That's just a sampling.Many writers prefer to just _write_ and find that too much tooling gets in the way. Some of them use tools for _planning_ separate from _writing_. Maybe fiction doesn't need to be refactored as often as code (though it does need to be refactored sometimes, and doing that in an editor using search is a pain). There are a lot of different kinds of writing and writers, and generalizations like "writers don't (or do) X" don't always stand up to scrutiny. Some do, some don't, some would if they didn't cost so much, and some do _sometimes_, depending on the task at hand.(Psst. Some software developers still use emacs or vim...)
- IDE-like tools exist for writers. Scrivener is a powerful general-purpose tool (also with [questions here](https://writing.codidact.com/categories/1/tags/228)). Madcap Flare, aimed at technical writers, has good support for updating links, defining "snippets" (xinclude blocks, essentially), variables, conditionalization, advanced build options, and more. Arbortext Epic is another tool in that vein. There are XML editors like Oxygen and Notepad++ that you are probably already familiar with as a programmer. That's just a sampling.
- Many writers prefer to just _write_ and find that too much tooling gets in the way. Some of them use tools for _planning_ separate from _writing_. Maybe fiction doesn't need to be refactored as often as code (though it does need to be refactored sometimes, and doing that in an editor using search is a pain). There are a lot of different kinds of writing and writers, and generalizations like "writers don't (or do) X" don't always stand up to scrutiny. Some do, some don't, some would if they didn't cost so much, and some do _sometimes_, depending on the task at hand.
- (Psst. Some software developers still use emacs or vim...)
#3: Attribution notice added
Source: https://writers.stackexchange.com/a/45037 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
IDE-like tools exist for writers. Scrivener is a powerful general-purpose tool (also with [questions here](https://writing.stackexchange.com/questions/tagged/scrivener)). Madcap Flare, aimed at technical writers, has good support for updating links, defining "snippets" (xinclude blocks, essentially), variables, conditionalization, advanced build options, and more. Arbortext Epic is another tool in that vein. There are XML editors like Oxygen and Notepad++ that you are probably already familiar with as a programmer. That's just a sampling. Many writers prefer to just _write_ and find that too much tooling gets in the way. Some of them use tools for _planning_ separate from _writing_. Maybe fiction doesn't need to be refactored as often as code (though it does need to be refactored sometimes, and doing that in an editor using search is a pain). There are a lot of different kinds of writing and writers, and generalizations like "writers don't (or do) X" don't always stand up to scrutiny. Some do, some don't, some would if they didn't cost so much, and some do _sometimes_, depending on the task at hand. (Psst. Some software developers still use emacs or vim...)