One way that I leave a trace, which is a practice I've adopted from Simon Willison, is to record blogmarks for interesting and useful things I come across. Sometimes I just leave a pull quote, but usually I try to add my own thoughts or make a connection to something else.
I don't remember my first steps with subversion, mercurial, or git too well, but I don't think any of them were any more intuitive. My understanding is that jj is supposed to be easier to use for day-to-day version control. I'm very comfortable with git, but that was hard earned and I don't see that level of confidence with most devs that I've worked with over the years. Hoping jj can be more accessible to the average working software engineer than git has been.
Great article -- I'm going set aside some time with a notebook and pencil today and give this a try.
I'm not sure I agree with the left brain/right brain, analytical and logical vs creative and emotional dichotomy. I think good design work can be just as analytical as it is creative. I think it has to be when it comes to UI and UX.
I outsource most of my esoteric `jq` syntax questions to ChatGPT. It does really well with them, usually turning up solutions that I'd struggle to munge together from several different google search results.
I wonder how ChatGPT would do with focussed pandoc requests.
Hey, I'm Josh, the creator of this TIL repo. I've started it back in 2015 and still contribute to it a couple times a week. I reference TILs all the time to remember how to do something. It has been a great practice and I'd recommend to anyone to maintain their own TIL repo.
https://still.visualmode.dev/blogmarks