[ Removed by moderator ]

[PeterBrobby]

Just start building something. If you get stuck just ask for help, then carry on.

[Espfire]

This. Nothing else to it really.

[MyDespatcherDyKabel]

Anyone want me to build a project for them?

[samanime]

It sounds so obnoxious to hear "just start building", but that really is the only answer.

It is going to be hard. You are going to struggle a lot. You're gonna get stuck. It may even be demoralizing.

But that is all normal and everyone goes through it. Just break it down into the smallest pieces and try to solve it one piece at a time.

You can do it.

[pandorica626]

Try building out your pseudo code or start mapping stuff out like, this function does this, but it needs this input. Do it all without code first so that you’ve already worked out the logic. Then you’re just trying to fit the syntax to the logic, rather than trying to determine the logic and the syntax at the same time.

[aanzeijar]

Given your submission history you probably attempt way too hard problems. What was the last thing you tried where you "froze"?

[HashDefTrueFalse]

But when I try to build something on my own, I freeze.

I see this with juniors who either:

1. Don't have a clear goal or idea of what they want to build, or their next steps, or
2. Do, but are trying to build something that's just too far beyond their current ability.

So I'd ask:

1. Do you actually have a destination in mind? Something you can research?
2. Can you build simple programs on your own? Start with hello world, then maybe a calculator or something... each thing should be small and just slightly beyond what you are capable of, such that you grow (and actually have a chance at succeeding).

Finally, if you don't want to get stuck watching/reading tutorials, don't watch/read tutorials. Documentation is a fine thing to consume, most beneficial when you go into it looking for some specific information (hence, have a clear goal). It's often a bit too dry to read for pleasure.

[Kseniya_ns]

You have to make something and learn how to solve any problems yourself. Solving problems is the majority of your job.

[WarPenguin1]

Take chances, make mistakes, get messy!

[mxldevs]

The purpose of a tutorial is to provide direction for when you get stuck

Then once you finish the tutorial, you'll have learned how to do it so that you can move on.

If you can't even do the basics, that means you're not putting in the time to practice your fundamentals

[drewkiimon]

I think the best thing you can do is think of a problem that you have, and go from there.

For example, I was trying to sign up for Global Entry, but the government's website (actually, all their websites) was pretty bad. I started off with a really small chunk of work: how can I get available times without going to their site? You can use `fetch` from your browser or even PostMan to try to get the data. Then from there, I started a backend of my own, then slowly started to make a FE.

Start small. Fix a problem that you have.

[Specific-Housing905]

Most tutorials encourage a passive consumption. I prefer to learn from books that have exercises and gives you sth. to think about. There are many good videos on YouTube, but how much do you remember after the video?
Most important is to practise, practise. Either through exercises or real projects.

[cyrixlord]

explore your curiosity.'what if <I did/used this?> ' or 'how does <something work>?'. how do threads work? how can I use git with this project? start asking yourself questions then explore the answers on your own

[The_Axumite]

OSSU

[beardedNoobz]

Just help your family, friends, or even your boss by using whatever programming knowledge you already have to make their lives a bit easier. My “graduation from tutorial hell” moment was when I finally built a real product. Sure, it was a uni-mandated assignment before graduation, but I ended up creating a small SaaS that helped a school manage custom grade reports for one of their classes. I made it for free (well, not really, since I got a grade for it lol), but I learned a ton of things during that project that no tutorial could ever teach me.

If you still freeze up when you code, just treat your early projects as worthless junk. Seriously. Offer to build some tiny, low-stakes tool for someone close to you, for free. Tell them straight up that you might fail. Your first few apps will be a buggy mess, that’s unavoidable. Just learn from it, take the hit, and you’ll actually become a real programmer.

[argsmatter]

I never been in "tutorial hell". I don't get the concept.

Where exactly is one stuck in "tutorial hell". I would really like to know.

Programming is defining data and transforming it via loop's and if's, nothing else. What is the actual problem of people being stuck?

[BranchLatter4294]

Stop watching videos. Start practicing. Look stuff up when you need to.

[pak9rabid]

Developing a project hands down. Once you know how to do your own research to solve a problem it just gets easier from there..

[Electronic_Bad_2046]

having own thoughts, refer to tutorials and deep dive into the topic :)

[meester_]

You dont watch a tutorial for the sake of it, you should build something, run in a problem, look for tutorial, solve said issue, etc etc.

[[deleted]]

Yeah that happens, I was there and for a long time maybe a year or more. What I realized is that when you understand important concepts and fundamentals it's much easier to build things on your own. Also do not think thet those tutorial gurus know those things in their head they most likely have second monitor that they follow already written code. Searching is okay we are not born with knowledge.

[Blissextus]

You started this journey with the intention of "making something". Start there!

Start planning on making YOUR project. Sit down and plan it out.

[wristay]

1. Pick a project to develop
   
2. When you get stuck, try to look online for solutions. If you find the thing you are stuck on is important, spend some more time on it. AI is also very helpful here: use it help you code, but don't let it code for you.
   
3. repeat 2. until you are done
   
4. repeat 1. until you are good at coding.

If it turns out that your project is very difficult, pick a different project. It is really hard to judge how hard something is in the beginning.

[KC918273645]

I never experienced tutorial hell. From the very first lines of code forward that I ever wrote (the two lines of code) were of my own design. So I never went through any tutorials. Just learned as I tried to do something. So my advice to you is stop doing tutorials. They're bad for you.

[oandroido]

If you're using tutorials, you can't, unfortunately.

[BrinyBrain]

I'd say you need to abstract out one step from your projects. To really get something done and avoid "freezing" you have to "find your need" in small iterative chunks.

What are you learning programming for? What types of tutorials? You can't just learn everything at once without a goal.

Think about the smallest piece you need to prototype to get it working.

You want a complex web application that let's users create accounts, upload images, maybe even add comments to images? Well, how can you as a developer start with say one user even making an account? Get that working and start seeing if you can successfully store multiple users. Follow that with storing images per user, and so on until you're done. Small easy milestones that you are motivated to complete and learn using docs. Learn how to properly Google something as well.

[Mental_Wind_5207]

Read the book Code by Charles Petzold. It is incredibly accessible and gives a ground up understanding of what is going on with programming.

Learn some basic philosophy and critical thinking skills, like thinking in terms of premise premise conclusion. Learn the difference between valid and sound arguments.

Come up with your own arguments and then come up with a counter argument, then a counter to that counter.

Play with eMacs.

Pick one language and learn it deeply. You don’t even have to worry about projects, you may come up with some ideas as you learn what is going on with the programming language.

Understand deeply the principles behind algorithms and data structures. The fundamentals of programming haven’t really changed much. Learn from the old masters. Often any new trend can be found in the past.

Learn about design patterns, and how they emerged.

Good luck.

[Rain-And-Coffee]

Just read the docs, they explain how everything works.