every-programmer-should-know VS developer-roadmap

And adds an ad.

[1] https://github.com/mtdvio/every-programmer-should-know/commi...

✅ mtdvio/every-programmer-should-know : https://github.com/mtdvio/every-programmer-should-know

Repositorios: https://github.com/practical-tutorials/project-based-learning https://github.com/mtdvio/every-programmer-should-know Desarrollo web: fullstackopen.com theodinproject.com YouTube ````

5. Every Programmer Should Know

Every Programmer Should Know. A collection of (mostly) technical things every software developer should know. Backed by a community of developers, of course.

Ci sono anche un po' di repo su GitHub che possono aiutare: https://github.com/arialdomartini/Back-End-Developer-Interview-Questions https://github.com/mtdvio/every-programmer-should-know https://github.com/schmatz/cs-interview-guide

github.com/nilbuild/developer-roadmap. 354k stars. Originally kamranahmedse/developer-roadmap, now under the nilbuild org. The DevOps roadmap is at roadmap.sh/devops.

If you're a developer, you probably know roadmap.sh. It's the gold standard for figuring out what to learn, packed with community-curated articles and videos.

Useful for many languages and technologies, roadmap.sh is a community-driven site offering free, visual learning roadmaps. The Python Developer roadmap guides you step by step from Python fundamentals to advanced topics.

Recently, while revising Node.js, I came across the project section Node.js roadmap on roadmap.sh(https://roadmap.sh).

You can also check out roadmap.sh to get a visual idea of what you’re working toward. Just pick one path and follow it for a few weeks. No need to jump between 10 tutorials hoping one of them will unlock your genius.

supermatt makes an interesting distinction there: if you're more interested in the practical/professional aspect, don't get too sidetracked in the theoretical side.

Computer Science is fascinating and wide, but if you're interested in reskilling into a new, professionally profitable sector, veering too much into the theoretical aspect can prove detrimental.

However, as you mention, your objectives will adjust the more you come to learn, so it's important to keep an open mind and read more widely than just the next necessary thing.

Just beware of ADD side-tracking you, and have clear road maos. (Speaking from personal experience there, I always have to keep a check on my direction during both study and work, lest I lose too much time without much benefit.)

Speaking of roadmaps to study, perhaps this site can provide an early guide, augmented by books and courses, for your chosen field:

https://roadmap.sh/

And don't let your age deter you. People who love what they do are rare and priceless in any age range. If a company doesn't want to hire you due to your age, then that's probably a company you wouldn't enjoy working for anyway.

​Roadmap.sh​ is a wonderful resource for any developer. It gives you a terrific map of the things you could learn in the future and helps you understand where in the learning journey you probably are.

> everything is human-reviewed and open-sourced for community auditing

2 projects worth checking out here: https://github.com/kamranahmedse/developer-roadmap (open-sourced roadmaps, no course content) and also https://github.com/ossu for more college curricula level (with references to outside courses).

I've been personally working on AI generated courses for a couple of months (probably will open source it in 1–3 months). I think the trickiest part that I haven't figured out yet is how to kind of build a map of someone's knowledge so I can branch out of it, things like "have a CS degree" or "worked as a Frontend Dev" is a good starting point, but how to go from there?

I really like how Squirrel AI (EdTech Company) breaks things down — they split subjects into thousands of tiny “knowledge points.” Each one is basically a simple yes/no check: Do I know this or not?

To navigate effectively in this new era, you need to master both fundamentals and modern tools. Roadmap.sh offers a comprehensive guide, but here are the critical areas every engineer should master: