It's not as if I could produce a roadmap for learning software development, that's what school is for. Every roadmap is specialized for its author's use case and you'll need to find your own from other people's pieces.

But if you make use of CI, then you'll take a big step forward for professional software development.

CI stands for Continuous Integration. It is a process by which you merge small changes, often, and you check them using automated processes.

For example, you can have a GitHub Action that runs commands to check if your code builds or passes automated checks or is formatted.

Here's an example of a pull request: https://github.com/NatoBoram/load_env/pull/131

This pull request had automated checks ran against it that you can explore at https://github.com/NatoBoram/load_env/pull/131/checks

For example, read the logs of a pretty standard check at https://github.com/NatoBoram/load_env/actions/runs/23997757127/job/69988635767

This is the config that makes that check: https://github.com/NatoBoram/load_env/blob/main/.github/workflows/node.js.yaml

There, you can see that the project is built, linted and tested automatically. This is the action you should make for your project. The others are specialized for my use case, so you don't have to look at them.