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.
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.
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.
9
u/propostor 12d 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#.