It’s not fully clear what you currently know beyond having 2 years of experience working with VB6 on what sounds like an existing stack.
So I’ll throw out what I know of the current “modern” way to develop software. You might be doing part of it, or some of it, or none of it. You also might not be able to do most of it because it is usually very radical shift that requires company buy-in to work properly, it isn’t something one person can just “do” on their own most of the time.
The “method” I’m talking about is DevOps.
A DevOps approach to building software at the highest level is all about optimizing the process of building software. This means the time between getting an idea/problem, and getting the solution to end-users is as fast and optimized as possible. This leads to a lot of “DevOps” technologies that can help optimize that process as much as possible. This also means integrating all parts of the company into the process, from developers, security, operations, to even business people.
To help manage a project, you’d optimize what you can. You’d write testing for your code to prevent regression that is automatically checked all the time, and continuously integrate your changes with your co-workers. If done correctly, you could deploy your changes to QA/testing personal who then could have their own automated tests/checks to further optimize their review, and possibly continuously deploy changes to end users.
This shortened lead time means the company as a whole can adapt and change as it needs to to meet end user demands and empower them to increase their market share.
I learned about DevOps, and bought into the idea after reading The Phoenix project. It reads well and is a novel, so its vastly more entertaining to read than most sources about software development.
There’s also classics such as: Clean Code, and The Mythical Man Month.
However in general most of these sorts of books don’t focus on specific technologies, only the ideas behind each technology.
Good luck, keep learning, keep building