I didn't go to a coding bootcamp. I didn't follow a curriculum. I just started building things, broke them, fixed them, and did that over and over until I could build more complicated things. That's basically the whole story.
It's not the most efficient way to learn, but it's the way that worked for me — and I've picked up a few things along the way that I wish I'd known earlier.
Just build something
Tutorials are fine for getting started, but they'll only take you so far. At some point you have to close the tutorial and try to build something on your own — something you actually want to exist. That's when the real learning happens. You hit problems that no tutorial covers and you have to figure it out yourself, and that's what actually sticks.
Being bored is underrated
Most of the stuff I've built started because I was bored and had an idea. Boredom is genuinely one of the best conditions for making things. No deadline, no brief, just "what if I made this." Some of it goes nowhere. Some of it turns into something real. Either way, you learned something.
Pick a thing and go deep
Early on it's tempting to try and learn everything at once — a bit of Python here, some JavaScript there, maybe a framework, maybe another one. It leads nowhere fast. It's way more useful to pick one thing and actually get good at it. The skills transfer more than you'd think.
Read the error message
This sounds obvious, but actually read it. The whole thing. Slowly. Most of the time it's telling you exactly what's wrong. The number of times I've seen people ask for help without reading the error message is genuinely staggering.
You don't need permission
Nobody is going to hand you a project and say "here, go learn on this." You have to make your own projects. You have to decide what you're going to build next. You have to keep going when it's not working. No one's grading you, which is terrifying — and also completely freeing once you get used to it.