idontgetit12

Why on earth would I assume, given that comment, that he is posting in good faith? I'm not going to assume good faith when someone has made it clear they're only here to look down on shared information.

You're right, it shouldn't be necessary, but their first sentence...

>I was convinced for a while there as I scrolled down that this was a joke. "Good parody!" I thought to myself. Then I realized to my horror this is actually serious.

...is pompous and holier than thou. Being unable to see the value in this infographic doesn't mean it's trash, and I think it's unnecessary to comment with such an arrogant attitude like that, especially when it's obvious they're just either not the intended audience or they're misinterpreting the goal of the graphic.

>After you've been doing this for a few years you realize that code is code, whether it's running on a server, or in a browser, or on a desktop or mobile device. It's just code.

Except, it's not "just code". Front-end/back-end/ops, whatever, all have vastly different contexts. Hence the separate learning paths. You should know all three, but that doesn't mean you have to learn them at the same time or the same pace. You people are taking this chart way too literally.

Agreed, the "required" skills isn't in a great spot and isn't properly labeled. And beyond "learn a language" (looking at the back-end part), it's really not for beginners. That being said, if you have some familiarity with programming but not the state of tooling/environment/etc in modern web dev this should be invaluable.

Maybe your brother needs to learn how to take things one step at a time if this would make him quit at first glance. I don't understand why it's a bad thing to have a consolidated source of information like this, I would have loved to have a detailed roadmap as a beginner. These graphics lays things out very clearly and obviously you don't need to rush through the steps.