Learning to Program? Read this.
Learning to program is hard. I know because I’m learning, and it’s hard.
When I first got started, I wanted to build EVERYTHING because I thought that was the best way to learn. I wanted to build the car, and also build the parts.
But that’s like learning to be a mechanic, and focusing on manufacturing. For some reason you think you need to know how to make wheels, tires, nuts, bolts, and timer belts.
Yes, you want to know how they fit together. You need to know how to assemble them. But no, you don’t want to learn to make them yet. You want to learn how to fit these parts together to make a car.
Then you want to learn how to fix the car when it stops working.
Then you want to learn how to make the car go faster, or turn tighter, or add 4 wheel drive, or a solar panel, or install a new engine.
Then maybe you’ll learn how to manufacture an engine. Then maybe you’ll learn how to manufacture tires.
But you don’t need to learn ALL of it now. Just learn how the damn car works. And then get really good at building cars out of parts.
Learn how to make fast cars. And then learn how to make off-roading cars. Maybe learn to build camper vans. And then learn how to build an off-the-grid van.
Do that first, and then you can decide to learn how to make parts or not. Because by now you’ll realize you have a choice. You don’t have to learn to make parts.
By now you’ll have developed momentum, and skill, and experience, and context for the profession that you’re interested in. You have overcome the initial obstacle of starting. You have gotten past the massive barrier that you yourself created.
Remove complexity and examine what is most important.
Learn to make a car first, then decide if you want to build parts.