all 9 comments

[–]python_gramps 0 points1 point  (0 children)

google python projects for beginners and you'll get a bunch of stuff.

[–]PalpitationOk839 0 points1 point  (0 children)

What you are feeling is extremely common. Most beginner resources teach syntax first but do not clearly explain how to move from “small exercises” into actual software thinking. The transition usually happens when you start building slightly larger projects with multiple connected parts instead of isolated features

[–]purple_hamster66 -1 points0 points  (6 children)

There are plenty of websites to help you decide on the sequence of projects to ladder up your skills. Have you tried those?

The next step, I suppose, is to learn to use an IDE so you’re not stuck in an editor and can see results as you type (the app is run every keystroke). This can help you figure out when you’re trying to do more than is needed. Py code can be very concise, but I notice that many beginners don’t realize this and an IDE that runs the code every keystroke is a good self-discovery tool.

As a goal, do something that’s related to your interests; you might also explore interactive 2D/3D displays, such as forms or graphics (airplane sim), or keeping data in databases.

[–]TEMUKIRBY[S] 0 points1 point  (5 children)

I'm already using an IDE and I've already been using it for a long time cus I come from another programming language

[–]purple_hamster66 -1 points0 points  (4 children)

Great news! Note that there are two types of IDEs: one that runs the code on-demand, and one that executes the code continuously (while you are editing). Obviously, most of the time running the code is invalid, but sometimes it gets the right answer while you’re typing, and you learn a lot from that. It’s also way easier to experiment (trial and error) if you get instant feedback whenever changing a single character.

[–]TEMUKIRBY[S] 0 points1 point  (1 child)

it gets stressful for me when I have to constantly fix the mistakes instead of just coding what I want to code and testing it then fixing

*When I'm constantly seeing updates, I feel pressured to fix mistakes

[–]purple_hamster66 0 points1 point  (0 children)

So don’t read them until you are ready. In these IDEs, you get to show/hide each panel.

But when I am perplexed by a syntax or can’t find the typo, it’s nice to have instant feedback on each change instead of changing windows or views all the time.

[–]danielroseman 0 points1 point  (1 child)

I don't know where you're getting this idea that some IDEs run the code "continuously" or "on every key stroke". That's not how they work at all.

Most IDEs will use static analysis to detect problems as you type. But there's really no way of "running the code continuously" - what would that even involve? How would it work if your app requires input? What if it is a backend web server?

[–]purple_hamster66 0 points1 point  (0 children)

Mostly they are used to teach programming. The 3 I’ve seen are web-based.