I attempted to refrain from this comment, but it has bugged me every time I have returned to this website. So here it is:

Call me vain, but your 'story' was posted merely 4 hours after my question, so your third section here seems very much like it was aimed at me or fueled by my inquiry. I would like to address this.

Remember how I sad your post offers no value at all? Yeah, well that is an understatement. Your post offers no value and makes you out to be an a-hole.

"3. I Learned X, Y, Y languages / frameworks / markup - whatever in X days. I must be a pro!"

Way to put down confident students. You're really letting your colors show with this statement. The usual statement that your paraphrase here is referring to goes like this: "I have achieved X, Y, and Z. I am confident in my study. What should be my next step?" Never do we assume we are prodigies or in any way amazing simply because we are confident and proud of what we have achieved.

You are putting students down and attempting to discourage them because you believe they are oblivious. You're assuming that there is no middle-crowd and that users are either 100% stupid and don't know a damn thing about development, or that they are professionals.

With feeling that your third section was inspired by my question (only hours prior to your post), I would like to state that in my four months of study, I have put in more hours than the average American will work a full time job over an entire year. This is no lie, no exaggeration. I have put in over 2,000 hours of study in four months.

" You roughly sat through the equivalent of a weekend seminar and have an idea of how stuff works."

You are a man full of assumptions about people's study. If your post was in any way inspired by my question, then you are so very far from incorrect about my experience equating to 'a weekend seminar.' Furthermore, you don't know what people have really put into their endeavors. You don't get all the facts in 200 character questions.

Lastly, I would like to make this piece of information publicly available, and since it applies to your redundant statements above, I think this is a perfect place to share it.

Novice developers want and need guidance. They want and need to hear answers that have been thought up and authored specifically for them. johnBoy10284 was told on Quora that he should learn Angular, but timMan35832 is not johnBoy10284 and needs a more experienced developer to assist him with a hand crafted answer to the answers that timMan35832 has.

We can Google all day and read that 'React and Angular are not comparable', and then read that 'React is better than Angular', and then be asked by other developers 'Are you using Angular or React?', and wind up completely confused because a-holes like you like to try to 'show up' noobs with your knowledge and opinion of what is comparable, what is right, what is wrong, what is good, what is bad, and all this other bullcrap that is completely irrelevant to our study. Every single one of your 'answers' not only attempts to belittle the subject, but also challenges the ideas and concepts possessed by him or her. You literally went out of your way to choose questions that you could not only answer, but that you could say 'you're stupid if you think that. Even your question is incorrect to ask, because you are wrong about the subjects of said question.'

Save it, and conjure up something useful to the community. Not this garbage.

I've seen posts like this before. You're not writing this for novice developers. You're writing this for other developers of intermediate to advanced skill to read, pat you on the back, and you both feel like you're a part of something together. "Fck those noobs, they don't know sht, but you sure told 'em, Mario." Yeah, you're totally in the club, man.

Being a self acclaimed intermediate developer, myself, I confidently state that you have not improved your image or standing in the developer community at all with this bullsh*t of a post, and that if any part of your post were inspired by the question I posted four hours to the creation of this post, then you are an opinionated, self-righteous, Narcissistic fool.

I am on my way to becoming a professional developer. I am giving it 20+ hours a day, every single day. No going out to eat, no bars, no shopping, no tv, no video games. I am going to be a great developer, and I would never accept a job offer from you or anybody like you.

Maybe I'm blowing it out of proportion, but I dislike you and I dislike people like you, and I am tired of seeing your bullsh*t literary works that are deconstructive and irrelevant. People like you make this an undesirable industry for novices to try to enter and grow into, and I absolutely am disgusted by you.

Your replies to these specific questions and statements are very generic. Answers like these are tiresome to the community. Just because you repeat the same things that have been said hundreds of time (almost as though it is trendy) does not mean that you know the secret hand shake and that you're part of the in crowd.

Furthermore, your statements are not beneficial to a novice developer at all. Sure, they show how much you seem to know, but fail to offer any value.

Have you visited codering.info? Ratings there are built up by developers only and are always up to date on trending languages.

I hate to pick, really, but you've made a couple of odd assertions in your post that I feel I need to address for the reasons in your first paragraph. Your example that "any commit after the first initial push" is a failure is a bit of a misnomer, especially (for example) in an agile project where each commit is an atomic enhancement, a step toward a short term goal. It's only a failure if that code doesn't work or has completely missed the point of its spec. Enhancement doesn't imply the code that came before it was incorrect (which your assertion does). Otherwise your notion of failure is entirely correct, and new developers should definitely be aware that the entire learning process is fraught with experimentation and failure. Don't take my criticisms as a rebuttal, but rather a fine tuning of some of the details.

I disagree with the "don't ask Angular vs React" notion simply because although they are different in nature (one is a framework, one is a view library) they both have such unique and well defined concepts that it's the actually the concepts themselves that are in question, not whether features of one will be better than the other. Angular has an ecosystem, but React needs to be supported by whichever library you back it with in a relatively specific way (be it a Flux implementation or otherwise). At the end of the day, choosing Angular vs React is more a choice between paradigms, rather than just semantics.