Just build something. The easiest way to learn is to do. In fact I personally find fixing other people's bugs to be a terrible idea for someone wanting to learn

Just build something. The easiest way to learn is to do. In fact I personally find fixing other people's bugs to be a terrible idea for someone wanting to learn how to build things and learn more about the general field of software development. It's a quick way to burn someone out, or make them lose interest in the whole thing before they're even started. Choose an idea, preferably something personally useful to you (don't spend too much time on this part because ultimately it's the process itself that matters) then build it. You'll need to pick a language/framework and build something with it, so go with whatever you're most familiar with, or pick something you're interested in learning. In the process of building something, not only will you learn the general foundations but you will inevitably create your own bugs and rabbit-holes you'll need to learn to fix anyway. At that point I would say it's a good idea to start contributing to open source projects, fixing bugs, extending features, etc. But not before you've reached some low-hanging fruit and built some self-confidence in building new software.