public-notes

I've been using GitHub Issues as a coding journal for a few years now and found it to work incredibly well. I work on most of my projects in public repositories and often end up posting hundreds of issues with thousands of accumulated comments across them all. I also have private repos which I use just for issue threads for coding journal mode entries that I'm not ready to share. Occasionally I'll take one of those private issues and make it public later on, for example this one: https://github.com/simonw/public-notes/issues/1

I've been trying to develop the habit of reading the documentation from cover to cover of any tool that I've been using for more than a year or so. I find that reading all of the documentation for a tool you've just started using isn't as valuable: if you haven't gained any experience with it yet, a lot of what you read will fail to stick. Once you have a few months (or years) of experience under your belt doing a thorough review of the documentation can massively increase your abilities with the tool. Here are some notes I made when I finally spent the time to read through every page of the Jinja documentation for example: https://github.com/simonw/public-notes/issues/4