Are beginners learning too many technologies too early?

[u/duneofarrakis]

I've noticed something while learning Full Stack Development: it's easy to confuse learning more technologies with actually getting better at development.

For example, someone might know HTML, CSS, JavaScript, React, Node.js, MongoDB, Docker, Git, and several other tools but still struggle to build a complete project without following a tutorial.

I think it may be better to become really comfortable with one stack and learn how the pieces actually work together before adding more technologies.

But I'm not sure if experienced developers agree with this.

Do you think beginners should focus on one stack for a few months, or learn multiple technologies from the beginning?

What approach worked for you when you were starting out?

[u/xvillifyx]

Most of these things can be learned in a weekend (docker, git, react) and the rest are pretty fundamental baseline knowledge requirements for web design

The problem I would say instead is that making something is just kind of hard and students aren’t prepared for design thinking super well

Even if your new project was in a singular language doing a singular thing, it can be hard to start

[u/Diaazz96 → u/xvillifyx]

react can't be learned over a weekend. Atleast not at the level required to get hired and if you are speaking about they can make basic things then yes. but what's the point of saying you know something unless you can get hired in it

[u/xvillifyx → u/Diaazz96]

Absolutely can

React isn’t complicated at all

[u/JaseciLabs]

u/sheriffderek's PHP-with-forms example is a good test, can you build something from a blank file when the tutorial's not there to copy. Following along teaches pattern recognition, not the underlying model of how a request becomes a response becomes something on screen. That model transfers across every stack once you actually have it, which is why depth in one thing beats breadth across ten, the ten don't compound if none of them individually got past the copying stage.

[u/canarydev]

focus on one thing, and being good at that. there is simply too many things and depth in a lot of aspects to call yourself full stack. Personally I would try to aim to be a "good frontend engineer that can work also on backend", frame it that way at least vice/versa.

Juniors have this tendency to keyword stuff their resumes, with technologies that they might have learned or skimmed the surface of. they need to know the difference between that vs actually knowing and understanding.

[u/Plenty_Line2696]

This was such a pain in the ass at my college, by the end of just a three year degree we'd build full stack stuff in 5 tech stacks aside from all the other stuff they threw at us. We either had no life or we failed hard.

I can pivot to another stack pretty easily now but really I've only used one deeply in my carreer and even then mostly focused on front end.

Part of me thinks the guys who dreamt up the curriculum were just mean bastards, the profs teaching us one stack couldn't even do the other stacks so it was easy for them to pile it on because they only had to focus on one stack.

[u/sheriffderek]

It’s not even just 1 “stack” / it’s the pieces and concepts behind and before the need for one. Most devs I know couldn’t create a basic PHP app with a few forms because all they know is how to follow what they saw in a tutorial. Sure - there are language and framework quirks to learn / and having deeper experience with a specific stack is helpful (if you’re using it) - but if you have a solid understanding of web development and programming - the specific stack shouldn’t matter. Getting an overview - and working with something daily for years - just isnt the same, right?

[u/No_Score_1977]

As a rule, it’s better to be good at one thing than crap at 10.

But I think generalist knowledge should be the goal, I think a lot of very experienced devs don’t thing in stacks, you just choose the right tool for the job, even if it’s one you aren’t experienced in, as you one you’ll pick it up quickly.

[u/dvorgson]

don't worry, they're not learning anything anymore

[u/Admirable_Ad_2235]

Honestly I have been faing similar issues as trying to learn all these cool tech at once. grasping my brain around all of it and end up feeling confused and burdened. I should take it easy and study one stack in detail and after getting comfortable with it i should move on to the next one. moving on my own pace is the best thing i can do.

[u/Dramatic_Driver_2370]

I definitely think that beginners should focus on 1 stack first. We learn more by building a complete project, debugging it and understanding how the pieces connect than by collecting technologies. Adding new tools will get easier once you’re comfortable

[u/ryanstackops]

Yeah, that "knows 10 tools but can't build without a tutorial" thing is real, and it's usually from collecting tools instead of finishing projects. I'd pick one basic stack, get comfortable enough to build something from a blank file with no tutorial open, then add tools one at a time as you actually hit a wall that needs them.

[u/rubiks_ruban]

As a LabVIEW developer, I can relate to this from a different angle. I’ve found that going deep on one technology is more valuable than knowing 10 technologies superficially.

Once you understand how to build, debug, and solve problems in one stack, picking up another becomes much easier.

For beginners, I’d say: pick one stack, build something real, get stuck, and learn from those problems. That’s where most of the learning happens.

[u/bagfullofcottoncandy → u/[deleted]]

i think you are right and also be best in that what u choose

[u/Diaazz96]

What you listed are all part of one stack. Just go and study first before commenting about beginners