What I have discovered recently is that it's really useful (or at least I am inclined to do that) to keep track of you daily findings or useful ideas as a developer.
An example is a pretty simple technical concept like dealing with polymorphic associaions in database modeling. There is nothing rocket sciency here, but having read a chapter in Bill Karwin's SQL Antipatterns book, I feel like I have learned a lot.
That said, it often happens that you might not encounter certain techniques or approaches for a long time and your knowledge fades.
This is why I briefly described the problem solved on my Notion journaling page, noted the book chapter and tried to summarize the approaches I considered and the one I ended up with (and why). At least, now I feel some kind of mental relief :)
What approaches do you use to make sure that your new pieces of knowledge do not evaporate too fast?