Pretty much everything is frustrating to configure at first. Then I learn it and it’s not so bad. Then I don’t use it for a few years, and completely forget how! Back to step 1.
I learned this lesson pretty quick when working in IT.
It’s not always feasible to document everything as it happens, but I definitely learned to do so if I had the time and means to while I was doing the thing.
Just started at a new company with 0 documentation, they’re super psyched that I’ve actually been writing down all their processes/procedures/configurations etc. as they explain them to me/as I work with them.
If you want to get into doing it, I found searching through a lot of note taking applications until I found something I really liked helped me remember to go do it regularly.
For FOSS stuff a lot of people like Joplin, and I could certainly recommend it. Personally though, I really like Obsidian for its backlinking and graph view features, but it’s not open source.
Furthermore, just carrying around a notebook and a pen everywhere you go as a habit helps a lot. I got into the habit of doing this by maintaining a personal journal for some time. For writing effective notation on paper which can easily be digitized, I would recommend looking into “bullet journaling” methods, and again, finding a notebook and pen that you really quite like, helps a lot to make the experience enjoyable and develop it as a skill.
Pretty much everything is frustrating to configure at first. Then I learn it and it’s not so bad. Then I don’t use it for a few years, and completely forget how! Back to step 1.
Initial thought was “I can’t think of anything”. Then I started scrolling through this thread showering upvoted on all of the repressed memories.
I learned this lesson pretty quick when working in IT.
It’s not always feasible to document everything as it happens, but I definitely learned to do so if I had the time and means to while I was doing the thing.
Just started at a new company with 0 documentation, they’re super psyched that I’ve actually been writing down all their processes/procedures/configurations etc. as they explain them to me/as I work with them.
I really should learn this habit.
If you want to get into doing it, I found searching through a lot of note taking applications until I found something I really liked helped me remember to go do it regularly.
For FOSS stuff a lot of people like Joplin, and I could certainly recommend it. Personally though, I really like Obsidian for its backlinking and graph view features, but it’s not open source.
Furthermore, just carrying around a notebook and a pen everywhere you go as a habit helps a lot. I got into the habit of doing this by maintaining a personal journal for some time. For writing effective notation on paper which can easily be digitized, I would recommend looking into “bullet journaling” methods, and again, finding a notebook and pen that you really quite like, helps a lot to make the experience enjoyable and develop it as a skill.
Thanks very much. I’ll take a look at your suggestions.