←back to thread

628 points kiyanwang | 2 comments | | HN request time: 0.406s | source
Show context
ozim ◴[] No.43629839[source]
Reading documentation - if you are junior take time to go one level deeper to understand / fix issues you have. Then read also stuff adjacent to that.

By trying to read some documentation like a book from cover to cover will be waste of time.

replies(4): >>43629980 #>>43630090 #>>43630395 #>>43630600 #
1. Wool2662 ◴[] No.43630395[source]
Reading documentation cover to cover for tools you use a lot is a very worthwhile investment in my opinion. Junior dev or not.
replies(1): >>43630497 #
2. ozim ◴[] No.43630497[source]
There are always better sources to read usually than documentation cover to cover.

There is no "only SO and LLM shortest path" vs "always read full documentation" - there are always more sources like blog posts, walk troughs that will be much better investment of time.

Sometimes you need someone to explain architecture of the tool much differently than it is described in documentation when documentation is dry. Sometimes you need better examples better aligned to what you are trying to do. You need different approaches to grasp the thing.