I’ve been switching from Vim to Helix recently. I did the built-in tutor, and whenever I need to configure something, I look it up in the docs. The problem is, I only find what I already know to look for. Without reading the documentation more broadly, I don’t really know what I can configure in the first place.

So I’m curious, do you sit down and read documentation to understand a tool, or do you just search it when you hit a specific problem?

  • sbv@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    6
    ·
    19 hours ago

    If it’s readable and well organized, I read it. I did the vim tutorial because it was very easy to run through. Ditto for some of the Android lifecycle docs.

    But there are a lot of bad docs out there.