A year ago I wrote up the Scrimba Backend Developer Path, a project-based curriculum for learning backend development. You can read the original here: Scrimba Backend Developer Path. It covered Node.js, Express, SQL and NoSQL databases, authentication, REST APIs, testing, deployment, and security, all taught through interactive screencasts and hands-on projects.
This is the revisit. A year later, what still holds up, what changed, and what I would tell someone starting it now.
What we cover
- What the path is, one year later
- What still holds up
- What changed
- What I would add now
- Who should start it, and who should not
What the path is, one year later
The Backend Developer Path is a structured online curriculum for becoming a backend developer. It blends friendly teaching with hands-on work: interactive screencasts you can pause and code along with, video lessons, and multiple portfolio projects. The core topics are Node.js fundamentals, Express for building APIs, working with SQL and NoSQL databases, user authentication, RESTful API design, testing and debugging, deploying applications, security best practices, and integrating third-party services.
It is self-paced, with a community for feedback and a certificate at the end. No prior backend experience is needed, though some programming basics help.
What still holds up
The fundamentals have not moved. Node and Express are still the workhorses of JavaScript backend work. REST APIs are still how most of the web talks to itself. Authentication, database modeling, and deployment are still the skills that separate someone who has built a tutorial app from someone who can ship a real one.
The project-based structure holds up best of all. The path does not just teach concepts, it makes you build things, and the things you build become a portfolio. That is the part that matters when you are looking for work. Nobody hires you for the lessons you watched. They hire you for the projects you shipped.
The interactive screencasts hold up too. Being able to pause a lesson, edit the code, and see the result immediately is a better way to learn than watching a video and hoping it sticks.
What changed
The biggest change is not in the curriculum. It is in the workflow around it. AI-assisted coding is now part of how developers actually work, and a backend course that ignores it is teaching a workflow from last year. That does not make the path obsolete. It means the path is the foundation, and the AI workflow is the layer on top.
The backend landscape itself keeps moving, as it always does. New tools appear, old ones fade, and the specific libraries in any course will age. What does not age is the shape of the work: requests come in, logic runs, data is stored and returned, and the whole thing has to be secure and testable.
What I would add now
If you are starting the path now, add three things alongside it:
- A real deployed project. Not a tutorial app, a thing you built and put on the internet. Deploy it, break it, fix it. That loop teaches more than any lesson.
- AI tools in the workflow, deliberately. Use them to explain code you do not understand and to draft boilerplate, but write the logic yourself until you can. The goal is to learn backend development, not to learn prompting.
- Testing from the start. The path covers testing, but treat it as a habit, not a module. Write the test before you are sure the code works. That discipline is what separates a junior from a mid-level developer.
Who should start it, and who should not
Start it if you are moving from frontend to backend, or starting web development and you know you want the server side. Start it if you learn by doing and you want structure without a bootcamp price tag.
Do not start it if you want a certificate to frame. The certificate is the least valuable thing the path gives you. The projects are the valuable part, and they only work if you actually build them.
Final thoughts
A year later, the Scrimba Backend Developer Path still holds up, because it teaches the fundamentals through projects, and fundamentals do not expire. What changed is the workflow around it. Start the path, build the projects, deploy something real, and learn the AI tools as a layer on top, not a replacement for the work.
The short version: the fundamentals and the project-based structure still hold up a year later. Add a real deployed project, deliberate AI tool use, and testing as a habit, and the path is still a solid way in.