10 reasons to use a code editor to write books
I have used code editors almost every day for over 20 years so I am very comfortable working with them. It is not that hard to learn the basics and as of this writing you can use the popular VS Code for free: https://visualstudio.microsoft.com/
1. Write text without worrying about formatting and fonts
That comes later: you should use a word processor to format your book and get it ready for Kindle or print.
2. Organize you project on the fly
Create folders and files in any order and move them much quicker than using the file system:
3. Search and replace text in every file at once with a single command
4. Easily create macros for certain tasks
5. Rename folders and files directly in the IDE as your project evolves
In most word processors you are going back and forth to the file system. In an IDE access to the file system is integrated
6. Multi tab and multi pane editing
You can collect your research/prompts into one pane and copy into another pane to write your chapters:
7. You can reconfigure the IDE depending on the tasks and set up different tabs,etc.
In many IDEs you can save this as a preset or macro.
8. Character and line counts are frequently integrated
9. With a subscription to GitHub CoPilot you will get AI recommendations as you type
At this point the results can be mixed but it can be a great antidote to writers block:
No comments.