Like another commenter mentioned, I have different types of notes: procedural (how did I fix X), thought processing (I want to design Y, what's the best way to

Like another commenter mentioned, I have different types of notes: procedural (how did I fix X), thought processing (I want to design Y, what's the best way to do it), and non-code documentation (this setup works this way because person Z requested it). I regularly refer back to procedural notes (I'm a contractor with multiple projects on infrequent maintenance for years), almost never refer to thought processing notes, and rarely refer to non-code documentation. However, while my rate of reference to procedural or documentation notes is fairly low, the value I get from that reference tends to be very high - for instance, "how did I solve that problem with the database that took me an entire day to resolve, because online docs/examples were sparse?" or "my client is asking why feature A was implemented in such a silly way; it's because they insisted it be that way, five years ago". For me I think the trade-off of regular note-taking is worth it. I suppose I could delete my thought processing notes after I've used them, but they're already archived and don't clutter my note space, so there's not that much point.