I've missed writing a daily journal, something I did at the last company I worked for as there was so much to learn and remember. I also did a daily journal after leaving Citi when I did the "100 days of code" challenge (see #100-days-of-code channel and GitHub repo). I'll add the 100daysofcode content to the new journal as there are some interesting things in there I beleive. When carrying out work sponsored by Clojurists Together, then keeping a regular journal really helped when it came to writing reports on work done with that sponsorship. Generally, I found writing everything down allowed my to more easily switch off at the end of the day and also give me a sense of progress. Keeping a journal to hand also provided a single place to note things down quickly so I didnt forget anything and made learning more effective. I've started a new https://practical.li/journal/ and writing it in Markdown, using Neovim and https://squidfunk.github.io/mkdocs-material/ (the tool used for the Practicalli books) which now provides a support for writing blogs (which is a useful way to publish a journal). This journal will capture a lot of the tasks I do in the background to support Practicalli work and other things I learn that support my day to day work as an engineer (and engineer manager)