Is It Better to Copy Code from Tutorials or Build Your Own Projects?

Sure, go ahead and copy-paste from tutorials, but remember that it won't teach you the necessary skills for real-world problems. What happens when faced with a project that lacks a tutorial? If you've only imitated code, you might find yourself stuck when debugging complex issues. Experiencing trial and error is essential—it's like understanding the full journey instead of just taking the easy road.

Copying code from a tutorial might seem easy, but it can lead to what's called 'tutorial hell.' You need to understand the why behind the code you write, or else when you face a problem without a guide, you’ll struggle. It's crucial to work through errors and unexpected behavior; that’s how you build real problem-solving skills.

It really depends on your goals! If you just want a working blackjack game, copying code makes sense. But if your aim is to learn programming, those mistakes you’re making are crucial. It’s not a waste of time if you're gaining insights along the way; every challenge is part of the learning process!

Trial and error is key! When I started coding, I also used tutorials and copied their ideas, but I always tried to tweak them into something new afterward. For example, instead of just sticking with blackjack, I’d think about poker or other variations. That’s when the learning really kicks in! Using documentation as a base and modifying it is a great practice, even now.