[–] 2 points 6 days ago (1 child)

Traditionally I open a README.md in the dir the application lives in after I configure something I will open my browser history, and dump every link I clicked into the file.

I then copy paste a choice selection of my shell history into the file.

This is the bare minimum. It's easy to do, takes like 5 minutes, and you will be happy to have it in 8 months. I would make the argument that anyone who tells you to do anything else can suck it. Do the readme first, any "better" documentation second.

Getting Into the habit of doing this matters more than a good documentation system. You will be lazy and try to get around to documenting something later. Don't let it be later. Shitty link dumps are still gold mines for your future self

  • source
  • [–] 24 points 1 month ago (2 children)

    Hasn't this been a thing for a long time? Personally I don't eat more than one "proper" meal a day unless I'm being physically active.

    I think it's fine. I don't like cooking that much and it's less effort.

  • source
  • [–] 3 points 1 month ago

    Git is designed as a permanent, historical record of text documents. You don't "clear" it out by deleting stuff, committing, and pushing. That stuff still exists, even if you change commit history it's going to stick around in the reflog for a long time.

  • source
  • parent
  • context
  • [–] 4 points 1 month ago (2 children)

    GitHub has a maximum of something like 10GB of storage available. That being said, I think your described requirements don't actually match git. If you're just publishing messages publicly (even if encrypted) then you can do the same thing with a simple http server.

    I think it's a really poorly thought out idea.

  • source
  • [–] 1 point 2 months ago

    I think I take issue with the idea that it's the "chat" interface that makes people shut off their brain and stay in that groove. I feel that the answer is more the very nature of LLMs being one of our attempts to get AI to pass the turing test. Continuing the conversation is such a core part of what an LLM is beyond the UI. If it made you think, you wouldn't believe it to be a human.

  • source
  • [–] 2 points 2 months ago

    We use Ruby at work, for a team I'm only tangentially involved with, and I'm not a fan. I'd be curious to know what a company that uses it as their primary language looks like. It seems like there's a lot of funky edge cases especially in templating that have bitten us.

    Has it really been 10-15 years since Ruby peaked in popularity? I never really paid much attention but I feel like time is a fiction.

  • source
  • view more: next ›