Programming

23348 readers

184 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

Do you actually read documentation, or just search it when you’re stuck? (programming.dev)

submitted 6 days ago by CoderSupreme@programming.dev to c/programming@programming.dev

21 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

[–] N0x0n@lemmy.ml 3 points 6 days ago* (last edited 6 days 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 !!!