free-programming-books VS developer-roadmap

What’s even more powerful is how these tools support maintainers. Code review can be a time-consuming process, especially during Hacktoberfest when contributions flood in. But with AI-assisted code reviews and automation checks, maintainers can focus on the things that make sense: architecture, logic, human decisions, instead of being bogged down in syntax or formatting issues. As an example, I contributed to EbookFoundation and their GitHub Actions bot picked up if any resources were placed in the incorrect order:

Most of my pull requests went to the free-programming-books repository, which had around 376k stars at the time of writing. I believe even small changes — like fixing broken links — can help others. Sometimes, one dead link in documentation can change someone’s entire learning path.

Evidence to the contrary (anecdotal, admittedly):

- https://github.com/EbookFoundation/free-programming-books/is... -- "The most recent freely available draft of C17/C18 used to be c17_updated_proposed_fdis.pdf, but it's no longer available directly and you need to use Wayback Machine to download it."

- I used to work for a multinational software company whose bread-and-butter was C. The company had indeed purchased a catalog of standards, but that catalog didn't include ISO C. When I formally proposed just that, they rejected it (and kind of made me feel uncomfortable about my proposal, to boot).

A massive collection of free programming books covering languages, frameworks, and paradigms, perfect for self-learners. Explore the repository

🔥 Top 20 GitHub Repositories Every Developer Should Know 1️⃣ Free Programming Books 📚 📌 https://github.com/EbookFoundation/free-programming-books A legendary collection of free programming books covering AI, web development, Python, JavaScript, and more!

Stars ⭐ : 344K Repo Link

Browse the repository and find books relevant to your interests.

Free programming books repository

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:

🔥 9. Developer Roadmaps 📍 https://github.com/kamranahmedse/developer-roadmap  Why it's awesome:  Visual learning paths for Frontend, Backend, DevOps, AI, DBMS, and more. It helps you stay on track with skills demanded in the real world. ✅ Best For: Career clarity seekers  📌 Update your resume based on this map

Anyways enough of that ranting, let me talk about what I have been upto these days. I started learning rust a month ago and have been learning DevOps for the past 3-4 months, I am following this roadmap from roadmap.sh (Great open source Place for roadmaps), and following that only made a switch from windows to linux. One of the better decisions I made recently cause I use this i3 laptop with 8Gb ram so windows had some difficulty working smoothly but ubuntu runs phenomenally disreagarding a few chrome crashes here and there everything run really smoothly.

Roadmap.sh Visual tech roadmaps for frontend, backend, DevOps, security, etc.