←back to thread

628 points kiyanwang | 1 comments | | HN request time: 0.202s | source
Show context
gwbas1c ◴[] No.43631365[source]
> Read the Reference

> Don’t Guess

I find that, when working with a new "thing," I often like to guess for about an hour or so before I really do a deep dive into the reference. Or, I'll read a stackoverflow answer or two, play around with it, and then go to reference.

Why?

Often there's a lot of context in the reference that only makes sense once I've had some hands-on time with whatever the reference is describing.

This is especially the case when learning a new language or API: I'll go through a tutorial / quickstart; "guess" at making a change; and then go back and read the reference with a better understanding of the context.

BTW: This is why I like languages and IDEs that support things like intellisense. It's great to be able to see little bits of documentation show up in my IDE to help me in my "guess" stage of learning.

replies(11): >>43631414 #>>43631448 #>>43631816 #>>43633123 #>>43633315 #>>43633373 #>>43634655 #>>43636297 #>>43636782 #>>43637333 #>>43638699 #
1. wging ◴[] No.43637333[source]
I don't think your approach is bad, nor is it in conflict with the advice in the article, at least in spirit. You aren't (I think) describing a situation where your untested guesses end up in a released product, or in ill-founded advice to colleagues. (Both of those actually do happen.) Forming and testing hypotheses is valuable, building on unfounded assumptions is a very different thing.