I absolutely agree with you pcr9103303. I have been following this practice since 5 years and I have benefited immensely from it (recall, retention and revision).
I have a dedicated screenshots root folder with sub folders that gets synchronized with the cloud and I go through them regularly.
I have been using http://leoeditor.com/ for couple of years and it is an essential tool in my workflow. Great to see other literate programming tools out there.
The problem is, there's 2 Unitys now, mixed up in one product, in various states of development.
There's 'Unity Classic', and 'New Unity'.
Almost everybody is using Unity Classic, but Unity is very focused on building 'New Unity' (DOTS/ECS, SRPs, Shader Graph, UI Elements, new input system, etc), which is intended to replace practically all of 'Unity Classic' one system at a time. It should probably have been a separate product, really.
I have not any problems with them. I got my card in my second week in the US and have been using it since then. I did ask them for an addon card for spouse and was told that might happen in the future.
I can attest to this. As a Technical Director supporting artists the tools I create for them are more effective when I study their process thoroughly and also get my hands dirty. Then design and implement the tool and it becomes my job to manage the complexity. Designing for change is something I keep in mind as well.
I have a dedicated screenshots root folder with sub folders that gets synchronized with the cloud and I go through them regularly.