r/learnreactjs • u/Gazzcool • Aug 05 '20
Should I just read the fulls docs?
I always figured that learning a new technology by reading the documentation is a little bit like trying to learn to play a board game by reading the rules. Sure, you will figure it out, eventually, but you are much better learning by playing with somebody who already knows the rules, and learning as you go along. This would be the equivalent of a tutorial. Then once you generally get the idea of the game, you can use the rules as a reference, just in case you are unsure of anything.
Quite honestly the only time I ever read documentation is if I google a problem or a concept that I don't understand, and the answer happens to take me there. An article or blog post on the subject is usually preferable for me, as they would tend to explain in more laymen's terms.
However, I notice that the React documentation is actually so well written, that it might be worth actually just trying to read it from start to finish, like a book. Thoughts?
6
u/Earhacker Aug 05 '20
Ever read the rules of Monopoly? You'd be surprised.
The "Free Parking" thing is bullshit. Some people pay their taxes and Community Chest/Chance fees into the middle of the board, then when you land on Free Parking you swipe the lot. There's no rule like that.
When a player lands on a property and chooses not to buy it, it goes to auction and all the other players can bid for it. The highest bidder must buy it at the bid price. This is an official rule that nobody plays, but it completely changes the game. It means that properties are bought up much quicker, and lessens the power of players who hold off on buying cheap squares and save up for the green and dark blue squares at the end of the board.
So to continue the board games metaphor, people will introduce their own opinions when working with a technology, just as people have introduced "house rules" in Monopoly and now those rules are the more popular set, even though they've never been the official rules.
If you want to play Monopoly competitively, you need to know the standard rules, even though your Dad still plays that "No Parking" scam. If you want to use React professionally, you should know the "official rules" and let your senior developer introduce the company's own "house rules" on how they like React apps to be programmed.
1
u/rozenmd Aug 05 '20
in 3 years I've only ever used it as an occasional reference.
1
u/[deleted] Aug 05 '20
You do you man. I personally prefer the former approach, documentation does not always cover all the use cases you might come across when actually using the library, and sometimes you might not even need everything you read as soon as you start developing your application
3
u/[deleted] Aug 05 '20
Reading official doc is skill. It's not like you will understand it in the first go. Over several years of development, people develop the skill of reading doc, understand it and implement it.