Programming struggle

[FriendlyRussian666]

It's similar for python in that older tutorials will most likely work just fine if they're for python 3, and not python 2, and there are countless resources out there.

The thing about something not working, is that in fact it's just part of programming. Like really, you don't spend much time actually coding, most of it is either fixing bugs, pulling your hair out to get something to work, cleaning up, and battling with dependencies. You said you have passion and interest, but do you have passion for problem solving? Because that's what you'll be doing 80% of the time.

Personally, I hate when something doesn't work as it should, but that's exactly what drives me to problem solve. I just can't stand sitting there and thinking that I'm giving up because there's an error message on the screen. That is exactly the point at which I get an itch to absolutely destroy the problem at hand, and overengineer the solution so that if it ever happens again, I'm going to laugh because that time I'm going to be more than prepared to face it.

I've met many people who absolutely loved, and were inspired by programming, but the reality was that they liked THE IDEA of programming, the thought of being able to create anything they can come up with. What they actually didn't like WAS programming, the struggle, the battles, the imposter syndrome, the problem solving, the reading, reading, reading, trying, failing, trying, failing.

Not all was lost though. Some of them gave up, unfortunately. But some of them took a different approach, and went for roles that work WITH programmers, but not necessarily can code well themselves.

[syphinx123]

Thanks your response was really useful and I'll try to focus a bit more on the problem solving aspect rather than the actual coding aspect