I think the other aspect is the easy to follow discussion threads. IMO it’s the cleanest way to show and follow branching discussions.
I think the other aspect is the easy to follow discussion threads. IMO it’s the cleanest way to show and follow branching discussions.
I keep a set of notes for each day. I have 2 journals. One for work and one for the rest of life. I use the same system in both. I took the Bullet Journal system of notation and added a few more to handle some edge cases that I encounter occasionally. The system works with any size of journal or pad of paper. I often drop sketches and diagrams in the middle of meeting notes. Actions get carried from day to day. Walk up requests get written down. I know when something was handed off to someone else. I like it! Totally not for everyone though. I skip the monthly and future planning parts. I would probably use that part if I was doing schedule management. Rapid logging is the part that I use all the freaking time.
https://www.tinyrayofsunshine.com/blog/bullet-journal-guide
Notes for small code projects/my network set up get tossed into .txt files. Eh. It gets the job done and there is only one place that file can be and it is the most up to date. Assuming I updated after the last changes. Which is a coin toss when things are busy. Comments in the code are a far more common way for me to keep track of what is happening.