52
Do you actually read documentation, or just search it when you’re stuck? (programming.dev)
submitted 1 year ago by to c/programming@programming.dev
20 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 year ago* (last edited 1 year ago)

Problem is a lot of people don't understand how to read a doc. There's a terminology, phraseology, syntax.

This reminds me of the ExifTool documentation... It feels like a well written documentation (and probably is) but the lack of context as a non programer can be overwhelming ://.

Thankfully, the forum was of great help and the maintainer is still active after all these years... Incredible tool by the way !!!

  • permalink
  • fedilink
  • source
  • parent