AI Course for Golang incorrectly generates content about the Go board game
5 points · Open discussionnilbuild
developer-roadmap
TypeScript2017–2026
nilbuild / developer-roadmap
developer-roadmap
Interactive roadmaps, guides and other educational content to help developers grow in their careers.
Developer ToolsWeb DevelopmentScience & EngineeringLearning & ReferenceDevOps & CloudFinance & Commerce
41Distinct people
47Mentions
0Explicit recommenders
371.9KGitHub stars
What to know before exploring
What it is
Interactive roadmaps, guides and other educational content to help developers grow in their careers.
GitHub
Where it is used
The source check is incomplete. Verified examples will appear here.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year47 dated mentions
Observed mentions: 2017-03-15 14:22:16 UTC to 2026-08-12 21:38:34 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 12 | 9 | 3 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 9 | 3 | 6 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 10 | 2 | 8 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 8 | 0 | 8 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 1 | 0 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
roadmap.sh
Community-driven roadmaps, articles and resources for developers
Roadmaps are now interactive, you can click the nodes to read more about the topics.
View all Roadmaps · Best Practices · Questions
Here is the list of available roadmaps with more being actively worked upon.
Have a look at the get started page that might help you pick up a path.
Frontend Roadmap / Frontend Beginner Roadmap
Backend Roadmap / Backend Beginner Roadmap
DevOps Roadmap / DevOps Beginner Roadmap
DevSecOps Roadmap
Full Stack Roadmap
Claude Code Roadmap
OpenClaw Roadmap
Vibe Coding Roadmap
Forward Deployed Engineer Roadmap
HTML Roadmap
CSS Roadmap
JavaScript Roadmap
TypeScript Roadmap
Git and GitHub / Git and GitHub Beginner
API Design Roadmap
Computer Science Roadmap
Data Structures and Algorithms Roadmap
AI and Data Scientist Roadmap
AI Engineer Roadmap
Inference Engineering Roadmap
AI Product Builder Roadmap
Network Engineer Roadmap
Cloud Computing Roadmap
AWS Roadmap
Cloudflare Roadmap
Linux Roadmap
Leetcode Roadmap
Terraform Roadmap
Data Analyst Roadmap
BI Analyst Roadmap
Data Engineer Roadmap
Machine Learning Roadmap
MLOps Roadmap
Product Manager Roadmap
Engineering Manager Roadmap
QA Roadmap
Python Roadmap
Python for Data Analysis Roadmap
Django Roadmap
Power BI Roadmap
R Programming Roadmap
Software Architect Roadmap
Game Developer Roadmap / Server Side Game Developer
Software Design and Architecture Roadmap
C Roadmap
C++ Roadmap
React Roadmap
Next.js Roadmap
React Native Roadmap
Vue Roadmap
Angular Roadmap
Node.js Roadmap
PHP Roadmap
SEO Roadmap
WordPress Roadmap
Laravel Roadmap
GraphQL Roadmap
Android Roadmap
iOS Roadmap
Swift/Swift UI Roadmap
Flutter Roadmap
Go Roadmap
Rust Roadmap
Java Roadmap
Kotlin Roadmap
Spring Boot Roadmap
Design System Roadmap
PostgreSQL Roadmap
Elasticsearch Roadmap
SQL Roadmap
Redis Roadmap
Blockchain Roadmap
ASP.NET Core Roadmap
System Design Roadmap
Kubernetes Roadmap
Cyber Security Roadmap
MongoDB Roadmap
Product Design Roadmap
UX Design Roadmap
Docker Roadmap
Prompt Engineering Roadmap
Technical Writer Roadmap
DevRel Engineer Roadmap
AI Red Teaming Roadmap
AI Agents Roadmap
Bash/Shell Roadmap
Ruby Roadmap
Ruby on Rails Roadmap
Scala Roadmap
There are also interactive best practices:
Backend Performance Best Practices
Frontend Performance Best Practices
Code Review Best Practices
API Security Best Practices
AWS Best Practices
..and questions to help you test, rate and improve your knowledge
JavaScript Questions
Node.js Questions
React Questions
Backend Questions
Frontend Questions
Share with the community
Please consider sharing a post about roadmap.sh and the value it provides. It really does help!
Repository Structure
This repository holds the content behind the roadmaps on roadmap.sh.
roadmaps/<roadmap-slug>/content/<topic-slug>@<node-id>.md
Each markdown file is the content of a single topic on a roadmap. The node id in
the file name is what links it to the topic, so please keep file names intact.
Merged changes are synced to the website automatically.
git clone git@github.com:nilbuild/developer-roadmap.git --depth 1
cd developer-roadmap
scripts/ holds the sync tooling used by the maintainers, see
scripts/readme.md for details.
Contribution
Have a look at contribution docs for how to update any of the roadmaps
Add content to roadmaps
Add new roadmaps
Suggest changes to existing roadmaps
Discuss ideas in issues
Spread the word
Thanks to all contributors ❤
License
Have a look at the license file for details
Read the full README on GitHubWhat Hacker News says
47 sourcesAre you truly a “generalist”? These are the different “roadmaps” for someone who wants to be good at something.
https://github.com/kamranahmedse/developer-roadmap
I have one rule that I have kept for a decade - I don’t touch the clusterfuck of front end development.
My value proposition is simple. Like Joel Spolsky hiring criteria, I make sure I continue to have experience that shows “I am smart and gets things done” and I pick a lane to go deep in - “cloud native green field implementations”. If that lane starts to narrow, I’ll jump on projects at work that get me into another lane. Technology is just a tool. Anything you learn new, Tens of thousands of others will learn the same thing.
Learning technology and not knowing how to communicate with the “business” and how to communicate adding business value will not help you stand out.
I
Read the rest
’ve done this for over 30 years.
> 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 che
Read the rest
ck: Do I know this or not?
The idea makes sense, but actually pulling it off is tough. Mapping out all those knowledge points is a huge task. I’m working on it now, but this part MUST be open source
btw, feel free to email me to bounce ideas or such (it's in my bio)
This article makes me think of the skill tree or roadmap posts we’ve seen here on HN or Reddit over the years. For example https://roadmap.sh/frontend …
I feel like we could do a better job of providing ourselves fundamental tools like this in helping ourselves and others learn. Not just in tech, but in life overall. The “dev” tree above is embedded in the life skill tree that should start in elementary school.
Haha, even the life skill tree has “fictional” branches that intercept the game world skill tree … you really do have to learn all of the dependencies necessary to case 5th level fireballs … there are real rules to be learned in the games their usefulness is just siloed into the fictional realm.
Edit: I forgot to point out that roadmap is open source here: https://github.com/kamranahmedse/developer-roadmap
In You are not dumb, you just lack the prerequisitesDiscovered the concept of "developer roadmaps" on Github. Two good resources are the frontend roadmap(https://github.com/kamranahmedse/developer-roadmap) and this react roadmap(https://github.com/adam-golab/react-developer-roadmap).
In Request for front end reading listRoadmap to becoming a web developer in 2021
2 points · Open discussionYes, I've helped tutor kids in web dev & game dev and I'm passionate about making tech easier for them. Remake was made for beginners, so they don't have to learn everything about full-stack web development [0] the first time they want to build a simple web app.
If your kids know enough to build their first website (HTML + CSS), they can also build their first web app with Remake.
I'd recommend checking out the Remake Recipes page [1] to get an idea of just how easy it is to build something that works. All of the editable examples on that page – as long as they use Handlebars.js {{variables}} – are examples of fully-working Remake apps that can be pasted into a Remake project (the app-index.hbs file). After that, they'll be working apps with editable data and user accounts that can be instantly deployed.
However, if you want to start by u
Read the rest
nderstanding the vision of Remake and get a broad overview of how it works, I can recommend this video I recently made: "Why Build With Remake" [2]
Also, here are a few of the more difficult parts you might run into:
- Terminal. You will need to run a few commands (remake create & npm run dev) to get the local Remake server running. It sounds like your kids are familiar with the command line, so this probably won't be a problem.
- JSON. In addition to Handlebars.js templating and CSS, your kids will also need to learn a little JSON. It's a pretty simple version of JSON (just objects, arrays, and strings all the way down), but it's still an extra concept to learn.
- Routing. If your web app has multiple pages, each with it's own editable data (i.e. it's not just a one-page website builder) you'll need to turn on Remake's unique IDs. There's good documentation around this [3], but unique IDs is a slightly harder concept to grasp than just HTML ⇄ JSON.
Good luck and let me know if I can help in any way. If a concept is confusing and you send me an email [4], I'll be happy to make a custom tutorial on the subject.
[0] https://github.com/kamranahmedse/developer-roadmap
[1] https://recipes.remaketheweb.com/
[2] https://docs.remaketheweb.com/why-build-with-remake/
[3] https://docs.remaketheweb.com/nested-pages/
[4] https://remaketheweb.com/contact-us/
I filed an issue on the original repository [0], most likely they can file a DMCA complaint [1] as the copyright owners, if nothing else.
[0] https://github.com/kamranahmedse/developer-roadmap/issues/80...
[1] https://github.com/contact/dmca
In Resources for Frontend developmentSorry to be blunt, but what you've done here is not legal. The source you've copied all this content from is not permissively licensed [0] and you can't relicense your copy as MIT and then write your name as the sole author as you've done currently in the readme.
[0] https://github.com/kamranahmedse/developer-roadmap/blob/mast...
In Resources for Frontend developmentI'm wondering, why starting a new repo instead of adding / contributing to the already quite successful https://github.com/kamranahmedse/developer-roadmap
which you credit and took inspiration from?
In Resources for Frontend developmentThe hard part here is getting a curriculum to learn software engineering. Writing code is much much more then just a language. So much time spent on that. Just learn one freaking language and move on.
eg. I started with Basic -> QW Basic -> Pascal -> PHP -> Perl -> ruby -> golang and a lot of others languages too.
Writing code is not the hard part.
follow something like this: https://functionalcs.github.io/curriculum/
Or if you want to be something specifc follow this and find resources to learn about the topics: https://github.com/kamranahmedse/developer-roadmap
In On finally learning to program at the age of 40> it's one gigantic imposter syndrome trigger
Yes, this was exactly my experience when I first encountered the repo for this project a couple years ago [0]. I actually still remember what it was like to read this for the first time.
From the perspective of someone who has been impaled on the hedgerow of despair, trudged through the endless shale of '5-minute-must-reads' and fought their way through the jungle of 'lazy tutorials rehashing a languages main beginner resource', I see why these kinds of things are created and upvoted/proliferated by developers who are no longer beginners. They're probably helpful to a minority I expect to show up in this thread. But to me these roadmaps are pathological (no pun intended) - inducing a cocktail of fear, apathy, and perfectionistic mania.
If you happen to be a beginner reading through this thread
Read the rest
and thinking of using this map - don't. Get a feeling for the territory first. Don't worry about all these empty terms. Once you have a feeling for this programming thing you can use your powers of prediction, analogy, and noting minor differences to learn new stuff. You don't have to (you don't WANT to) jam it all into your brain at once. I took that route and it makes it really hard to play and explore for yourself, it was so painful and inefficient.
Go the naturalistic route. It's not wrong unless it doesn't work, in which case it's still not wrong. It's all good. Have fun. Make yourself laugh. Do it stupid, who cares. Edit/break/play around with stuff, maybe go Codepen [1] if that sounds fun. Maybe you want structure and streamlining, go see if FreeCodeCamp is for you - you'll tick off half the boxes here without even realising it, and that half will be the half that's worth anything to you :)
[0] https://github.com/kamranahmedse/developer-roadmap/
[1] https://codepen.io/picks/pens/
I glanced over your LinkedIn profile, to me it looks like you need to add more 'modern' tech skills to your profile. It sucks, but the industry moves to new tech quickly and unless you are an enterprise Java developer, your skills get pretty much outdated in few years and you need to catch up at a fast pace.
I would learn (or highlight it if you already know) React.js and Node.js immediately, along with Postgres and MongoDB. That should get a good boost to the resume.
If you are going full stack, you would definitely need to put in AWS, especially micro services and serverless experience along with golang if possible. You can also learn Python if you want to try your hands on Machine learning as well, but I would recommend just focussing on React and Node.js as they are low hanging fruits and there are good enough openings for those two a
Read the rest
lone..
I have been in your shoes before and I know it could be overwhelming but you can do it.
https://github.com/kamranahmedse/developer-roadmap
my 2 cents, check this: https://github.com/kamranahmedse/developer-roadmap
In Ask HN: Absolute noob here, what programming language to learn to land job with?Showing the 15 most recent of 47 sources. Enable JavaScript to search and browse every indexed mention.