Like soup-to-nuts. I know I need to document what I’m doing and I’ve started several times, but then I never go back and make updates. I don’t know if it’s just the ADHD or if I’m just going about it or thinking about it in the wrong way.

So I’m curious about:

  • what you use for your documentation
  • how you organize it
  • what information you include
  • how you work documentation into your changes/tinkering flow

Edit: Dang, folks! You all have given me a lot to read through, think about, and explore. Thank you!

  • captcha_incorrect@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    15 hours ago

    In only have one server with NixOS. I don’t use flakes, just plain nix files. It still works great as documentation.

    The only thing it is missing is why something is setup in a certain way.

    • shrek_is_love@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 hours ago

      Do you use git? That basically forces you to do some documentation as you go. Multi-line commit messages are often helpful too. (When I first learned git, I only committed using git commit -m which is a bit restrictive in terms of how much you can fit in commit messages)