Getting lost and found

Mon, Nov 1, 2021 2-minute read

It’s really frustrating to be following your own footsteps every time, as you may notice I love exploring, trying new things, tools, commands, etc… I would say that I’m not the only one that “learned” something new on the terminal after looking for some solutions online and reading some fucking manuals and once configured properly then you forget it almost instantly.

Having projects structured in repos is not the only way to get things “repeateble”, some projects or explorations are mostly changes on .cfg files, some “properties” or some “dotfiles” but they are more random and sometimes it’s hard to group them in one specific project.

Let’s face it, documenting is hard, but is the only way that things will not be lost on the space of the different installations, backup folders, and so…

So what I will try to do to solve this problem, here are my future steps:

  1. Making sure that once I found something relevant I will ask myself the following:

    1. It was hard?
    2. It was some kind-of “interesting” for the future?
    3. It is worth it to document it?

    If all the answers to the above questions are YES then I will go to step 2.

  2. Create the record:

    1. It was already documented online? Then bookmark the solution
    2. Is documented online but you addeded some additional details? Then I will post it on this website
    3. Is poorly documented or the experiment was personal? Then create a new .org file with all the details and add it to “my-linux-setup” project

With this small procedure I find myself more confident that I will not lost any of the major knowledge that I’m investing on my journey with Linux and other systems.

But this fits only for future projects, what happens with the past? Should I re-visit my backup’d home directories from the past to search if I found something interesting?… What procedure I should perform?