Hacker News Reader

You have a point, in a more relax comment, how much learning is enough? As personal opinion just reading the documentation of your tool of choice can lead to vast amount of knowledge, default params, recommended practices, all of that is included in a well documented project, but how much should I dig into the rabbit's hole when using node?.

View on HN

I see your point. How much do I actually have to know is a very good question. Because there will always be something else to learn.

In my case, I want to have a good base knowledge before leaning on any kind of "magic". I got into Python with the MIT course on EDX and got bit by the programming bug. I decided to try and get into the web dev stack, so I started to dive into JS too. Now I want to start to build stuff, and the reason why I asked the question in my first post is because it may be easier to just go deep into one language (can't do web dev without JS), since I am so inexperienced.

Well if we can say things we can say that any abstraction is magic until insiders are seen, the question is how much abstraction you are willing to take in order to feel comfortable.

Reply on news.ycombinator.com