I’ve heard of the importance of keeping such a journal in the past but need to actually start doing so.

  • sup
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Interesting… I think it’s a good idea and worth a shot!

  • masterofn001
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    I’m not a programmer or coder or engineer or anything of the sort, I just use the command line and do experimenting and tweaking a lot on linux. I have progressed from a basic start.exe to multiline commands and functions, scripting, compiling, running tor and DNS relays, (I love this shit!) and have had to use the tiniest morsels of code from god knows how many different languages used by all these things. (This has actually helped me a lot.)

    And I always think, ‘i should make some kind of personal archive and be at least a little structued, and maybe not do all this when you’ve been up for 3 days’.’

    Then, I type out the same commands, usually forgetting some bit of syntax or rule in my current context, spend some time wondering why it didn’t do what I wanted.

    Or have to think for a bit about that one obscure issue that might be relevant again and what was that command for this odd scenario?

    But, now I’m 10x faster at the whole process of making mistakes and not remembering because I have done it 1000 times!

    I think this journal thing just might help.