arry

What's the rationale for allowing the components to be defined as functions in the first place? As far as I can see, it has a single thing going for it: saving a line of code, at the expense of jumping through the JavaScript hoops to implement the class/function distinction described in the post. Besides, when the function component evolves and acquires the need for state or other features, the saved line of code goes right back in.

What's the positive answer to "What do they value?" for you?

Did you feel great? Did you become a great Ruby programmer?

Yes, you're the only one. When an article is about Kafka, it's about Kafka. When it's about the streaming library, it's going to be about Kafka the streaming library, and no need to pollute the comment thread with glib remarks about Kafka the streaming library when the article is about Kafka.

Which book would you recommend for learning this stuff? I'm not very interested in 800-p. gorillas; there surely must be something short, not too theoretical, and to the point.

Justin has a series of videos on the fretboard organization [1]. From looking at the contents of the linked book, I think it covers similar material. And he sells an ebook Chord Construction Guide [2].

[1] http://www.justinguitar.com/en/TB-030-CAGEDsystemVid.php

[2] http://www.justinguitar.com/en/PR-011-ChordConstructionGuide...

So what? There are people who'd like to help you. So what? When I have suicidal thoughts, I don't care in the least about other people who could help me. Posts like this are helpful, of course, to raise the awareness of the problem, for other people. But when I, as a person thinks about suicide at the moment, look at this page, I just think: so what? and close the browser tab.

How about, "Walk and you'll come"?