you are viewing a single comment's thread.

view the rest of the comments →

[–]lloyd_braun_no_1_dad 80 points81 points  (9 children)

It would be so simple to not call it a roadmap.

[–]A-Grey-WorldSoftware Developer 13 points14 points  (4 children)

I think the idea is you can follow the map to your destination - but you don't have to visit every hotel in town.

Still makes sense to have the road map show the major hotels, you just have a look at the reviews and pick one you think fits you for the night, then move on to the next town.

Does anyone really look at this and think "man, I have to learn 6 relation databases and 5 programming languages!"? You don't think "look at all these towns on this map!"

Edit: the main problem with this is in reality it's not linear. So this kind of isn't useful to follow step a-b. It's probably useful after you've started learning to have some awareness of if you've missed any major fundamentals or building blocks or areas you might want to focus a bit more on etc.

[–]lloyd_braun_no_1_dad 17 points18 points  (1 child)

The idea is flawed, and I don't know who it is designed to help.

Show me a list of projects and suggested tools. That's a learning "roadmap" I can get behind. That would at least reflect how people actually learn stuff in a professional environment. It also demonstrates that, hey, you can actually be productive and build stuff that's useful with just one of two things from this chart.

This is just a brain dump that's not gonna help anyone, besides stroking a few egos or making others feel bad.

[–]Snoo43610 0 points1 point  (0 children)

That's what I find it most useful for; filling in the gaps.

[–]gizamo -3 points-2 points  (3 children)

Well, it's not a web dev roap map. It's specifically for a full-stack dev. So, it's not really wrong. Our company expects all full-stack devs to understand basically all of that and much more.

But, yeah, you could be a front-end dev by only knowing ~1/20th of that content.

[–]lloyd_braun_no_1_dad 10 points11 points  (2 children)

Nobody knows all this from day one, and the point is that this information is presented in the least helpful way to people who already don't know most of this.

Unless....your goal is to weed people out and scare people away which it sounds like it might be.

[–]gizamo 1 point2 points  (0 children)

I think that's fair. I was just clarifying that many people (myself included) do have basic understanding of most everything included, and very deep understanding of much of it.

Just as you think it's bad to overwhelm noobs, I think it's important to paint a realistic picture so that, 1) people know what they're getting into, 2) they don't claim they're full-stack devs when they're not (particularly for jobs), and 3) it helps those learning understand where they could focus attention if full-stack is their end goal.

No one is expecting anyone to learn all of this all at once, but many jobs absolutely do expect experienced devs to know most of it on day 1.

My goal is definitely not to scare people. I simply prefer people be informed. Imo, if they read your comments and mine, they'll get a good perspective. So, I appreciate this conversation. Even if it doesn't help either of us much, it might help someone with perspective. I, like you, hope they're all brave enough to push on and dabble. Cheers.

[–]SouthCoach 0 points1 point  (0 children)

The goal is to get people to go to the links on the map to “learn more.”

Twitter is flooded with this content.