|
Searching for what isn't there can only be done by searching for what might be there and shouldn't be. I remember over 25 years ago learning SQL and realising that searches can only return what is in the database.
Finding stuff missing is a draft review and is really hard, not real proof reading. A beta reader can help, but no-one can spot what's in your head that you never committed to paper.
A week or too after taking notes on paper I might not understand them or know which piece of paper. So I started to enter notes into the computer in an organised fashion. I tried my own local "wiki" for a while. It's really worth while using Notepad++ (Windows), KATE (Linux) or Jota (Android phone). I do still print and annotate some data like timelines on paper, then update the spreadsheet / text file.
I use a spreadsheet to track the status of all the projects and authors as it's not enough data (also single user) to make setting up an SQL database worth while.
|