That's a great idea, making it a regular thing to reflect on all your good work makes such a difference
It really does help.
I think doing reports of what I have done written (spoken reports I'm too shy and I don't want to brag or something) to someone really keeps it at bay. I'm required to report twice a week and it doesn't only help me realize I make contributions but help me organize my time better and keeps me accountable.
I find it important to reflect on what I have learned. Someone else could say it wasn't much but that's not important and not the point of it.
The important part, and I think it helps, is that it's used more observationally than to judge or comment upon and it has really helped me grow into myself more and I'm thankful for it. :)
Maybe use „git log“ as reminder what you did? :)
Missed this last comment until now, but that only works if most/all of your work is code related. I started this habit as I was transitioning from individual contributor/team lead to CTO. Since the git log approach did not work anymore (there were quite a few days where I myself didn't code at all) I started doing the text file as a way to record other things (PM, planning meetings, client relations, 1-on-1 meetings etc).
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.