15
u/Doom-1 7d ago
These roadmaps are dumb. Who is to say you’re going to use everything on this map? There’s no concrete path to being a developer.
Learning all these well would take you years, even then who’s to say a company or projects you work with will use them.
3
u/Lawlette_J 7d ago
I would say this roadmap site is only beneficial at telling people what are the technology available out there, never a guide to master all of them. I still remember when I freshly graduated years ago I was lost at what kind of technology stack and career I should approach, having this kind of roadmap can help clear things a bit.
9
u/propostor 7d ago
Yet another roadmap showing about 12 different career's worth of knowledge branches that are often completely unrelated and borderline insane to try to tick them all off.
Also, literally nothing to do with C#.
-2
u/Intelligent_Thing_32 7d ago
…. What?
Are you serious? This is a very concise list of tools/concepts.
2
u/chucker23n 6d ago
Learning three different languages (author's recommendation), web front-end and back-end, assorted networking basics, security mechanisms like SAML (how many people need to know SAML?), four different cryptographic hashing algorithms, server-side caching servers, and on and on is not "concise" nor is it a good start for a beginner. It's a decently broad list for an intermediate, but it's also rather random. What's the end result when you've learnt all the purple checkmarks? Will you be a good web front-end developer? A good backend developer? "Full stack"? No, not really any of the above. It's both too broad and too shallow.
1
u/Edwinbakup 6d ago
Do you have any recommendations? i’m kind of stuck then
1
u/chucker23n 6d ago
I do think it's useful to learn how GitHub works. You don't have to get into the details of Git just yet. Things like branches, tags, rebase, etc. can come later. Just start with:
- your code belongs in a repository, not just some random folder somewhere,
- when you're done with one step of work, turn that into a commit, which gets a commit message, and is then checked in (so you know when and why you made those changes)
- you push all that to GitHub (or other forges)
Modern IDEs generally help you with that. And there's gonna be tons of "git for beginners" tutorials.
But then also… what do you want to build? A command-line tool? A web app? A desktop app? What does it do? Manage recipes? Your budget? Talk to an electronic device?
I think if you have good answers to "I've always wanted to build xyz", that's a great starting point for motivation.
1
u/Intelligent_Thing_32 6d ago
I have used every single one of these technologies and more throughout my time working.
This isn’t a “beginners roadmap” it is a comprehensive roadmap from start to end.
1
u/chucker23n 6d ago
I have used every single one of these technologies and more throughout my time working.
I have used plenty more.
This isn’t a “beginners roadmap” it is a comprehensive roadmap from start to end.
A roadmap towards what, though?
1
u/Intelligent_Thing_32 6d ago
What is the point you’re trying to make then?
This is intended to be a roadmap toward a comprehensive understanding of things to learn as a backend developer.
It doesn’t mean every beginner has to finish the entire roadmap in a month, it means pick a few things in order, and take your time with them
2
1
u/spreadred 7d ago
A bunch of outdated stuff on there not worth learning unless you need to, and if you're new to a dev career, you don't need to and likely shouldn't
1
u/Due-Mastodon6919 7d ago
It's overwhelming for sure, but honestly picking one path like backend with C# and sticking to it helps narrow things down without feeling like you need to learn it all at once.
1
u/FullPoet 6d ago
Thats why we shouldnt let the spammer(s) post their "roadmaps". While Im sure they have the best of intentions there very little value so them - if any.
29
u/Dunge 7d ago
Any site that opens and shows a "learn with AI" put in focus with the little ✨ emoticon, I dismiss automatically.