refactor old notes

Big notes violate the guiding principle that notes should be atomic. (See notes should be atomic)
- Notes shouldn't contain sets of information.
- If they do, the notes become difficult to revise and then, boring
- Eventually, the big notes become stale.
- That is, you revise them but do not actually see them.
Stale notes, on the other hand, violate the guiding principle that notes should be in motion. (See SRS is not a bucket SRS is a pipe)
What you want to do is creatively split the note into smaller revisable bits. (If this is not possible, then delete the stale note.)
That is, when you come across a stale note during your revision session, you should add new questions (i.e, notes) for each of the sets of information in the question and answer pair of the old note.
For example, the following note is a question that asks too many "things" at once:
Where the answer is a piece of code:
To answer the question, one would have to come up with an initial pseudocoded bruteforce solution to the problem, analyze the initial solution, make improvements or explore another approach to solving the problem, and then code it up. That is a lot to think about during a 1hr review session.
- Sometimes, it is okay to create nonatomic notes (See notes should be atomic) when you are in a hurry. But you should attend to the note later.
To refactor such a stale & old note, on Anki, you can Forget that particular note. What this does is it makes the note appear in review sessions as if it was newly added. (See using anki feedback to make ideas salient)
- Once this is done, for the example of a stale note above, notes such as "How can cubes of numbers be generated when attempting to generate the ramanujan numbers with C++?", or "If you are given a set of cubes, how to you obtain pairs that sum to...?" etc.. can be newly created and properly tagged/linked.

Backlinks