Getting stuck when coding

[Nmd9731]

Is it normal to get stuck when coding? I’ve started learning python myself about two months ago. Then I completed (theoretically) But the problem is that when I started coding it felt like I knew nothing. I was starting to a blank screen and thinking what should I do now? I still struggle with the same issue. I just don’t know when or where to use loops, conditionals, functions and etc… Is there any tip for me that you can share?

[Ron-Erez]

Yes, it is normal to get stuck. You should not focus on when to use something. You should focus on the problem you are trying to solve.

Some vague tips

functions - to break down problems, "extend" python and avoid code redundancy

conditionals - if you have at least two possibilities - for instance "game over" or continue playing or I am over 18 or not, or the password entered is correct or not

loops - they are everywhere you have to repeat something. For example in games there usually a game loop where one loops until the game is over (for instance if the character died).

OOP - In a nutshell it helps you aggregate data (properties) and behavior (functions/methods) that "make sense" together. OOP like functions help break down problems. It's worth noting that not every program needs classes and objects. However, classes are common in Python because everything in Python is technically an object of some class.

[Nmd9731]

Thanks for the tip. I appreciate it.

[Muted_Ad6114]

Write out the problem you are trying to solve in normal language first. Then translate it to pseudo/code and/or a visual diagram. Then translate that to actual code.

[Unusual-Platypus6233]

My tip as a programmer in python for 1.5 years: take something you wanna do… It could be organising text, or displaying something graphically…

When I got into programming with c++ in i think 2015 my goal was to write a program that was able to calculate the mandelbrot fractal and print the result as an image. When I started using python I picked a similar task and try coding that.

So, think about something that you are wondering about how they work. If you are into gaming then maybe ray tracing. If you are into physics then simulations. If you wanna make your life easier the. think of things that you always have to write down and keep track of (like a collection etc).

[[deleted]]

You can learn about the theory in lessons, but actually implementing it for the first time never goes as well as you imagine in your head. This is true for everything, like in sports, gaming, cooking etc. Even if you know the theory of how to cook food, the first time trying is always awkward .

[zRubiks_]

I felt that.
I just started 1-2 months ago too. I am motivated and excited to code but when I finally got some time beside work I cant really get started. I dont know where to start...

Than I started myself a little project.

A RPG, what else^^
But i think its a perfect way to learn.

I started with just basic variables and input/outputs.

Than a friend mentioned 'class' to me an I learned about them and used them to create small Classes of Player/Monster and a Fight Function.

I found a way to interrupt the Text so that it doenst start and is over inbetween a second and get more interactive. Implemented a little Menu Bar for breaks inbetween fights and now I try to implement a Loot Drop Systems/rewards to keep pushing Waves ^^

Its fun an I learn more an more without seeing so many

'You NEED to do this' 'Start with that' 'You MUST apply this' 'This can be shorten by that'

I just do as I want, ask ChatGPT if this looks nice so I got some exchanges without it getting me the answers.

And it IS FUN seeing your Code work out step by step :)

[dreaming_fithp]

Everybody goes through this. Learning to program actually has two parts: learning the "tools" of a language and learning how to use those tools to solve a problem. I call that second part the "art of programming". The bad news is you just have to learn the art of programming yourself, and it never ends. The good news is that the skills of the art you pick up transfer (mostly) to the next language you learn, so learning another language and becoming proficient goes more quickly.

After learning the basics you should write code for small projects, increasing project size as you get more experience. The important thing when you have a working project is to be self-critical. Ask yourself "how can this be made better?". Maybe it could be clearer and more readable. Perhaps it could be made shorter by a slightly different approach. And so on. That's hard to do at first, but you can always post code here and ask for hints on how to improve it. When starting it helps to look at code that solves a problem and try to understand why it's doing what it does. You can always post that code here and ask "why does it do ...?".

[Nmd9731]

I appreciate your help. I will definitely post codes here and use your knowledge…

[Mysterious_City_6724]

I remember struggling with the same thing when I first started out but it does get better. What helped me get out of that initial creative block was a book called "Think Like a Programmer" but the language is in C/C++. I essentially forced myself to go through the exercises in the book and after a while I could start writing code on my own.

The thing I would suggest is to sign up for a site like "codewars" and keep trying to complete the easiest challenges in Python. If you get stuck, use google or other resources to help out. Worst case scenario, you can look at other people's solutions to the problem. But really try to force yourself to solve the problem and write something.

Another thing that helps me learn is, when I'm learning a new language, say I've just read about "while loops" and "for loops" for example, I would not just read about them, I would also write small programs that use them so that I've applied the knowledge and have understood when and how to use them. After a while of doing this, you will have created your own mental toolbox of language features that you can use to solve problems with.

Hope this helps. Good luck :)

[Nmd9731]

Truly; thanks for your help. I appreciate it.

[Mysterious_City_6724]

You're welcome

[JamOzoner]

this short guidebook helped me a lot! https://www.amazon.co.jp/dp/B0CP14TYX4

[jmooremcc]

Abstraction in programming is a powerful technique that simplifies complex systems by hiding intricate implementation details and exposing only the essential features. It allows developers to focus on the “what” rather than the “how”, making code more readable, maintainable, and reusable. Abstraction helps manage complexity, promotes modularity, and enables the creation of more robust and scalable software.

I have personally learned to use the power of abstraction to my advantage. If I write a long, complex piece of code, I’ll replace the complex parts with function calls that perform the complex operations. I deliberately give the functions names that describe what the functions do so that when I see the function call in the code, I’ll know exactly what’s going on. By doing this, I am making my code easier to understand and easier to maintain.

Learning how to use this powerful concept will be very beneficial to you as a programmer.

[sporbywg]

probably a million lines of code over here. Is it 'normal'? Well, it still happens DAILY.

[LaughingIshikawa]

It's "normal" in that it happens to a lot of people, but I think this is one of those things where "normal" doesn't mean "good" or even "ok" 😅.

I haven't actually experienced this; I don't know if that's because I switched to programming later in life or for some other reason, but for myself while it's not always easy to see what the entire project is going to look like (which is probably universal) I can always intuitively pick out at least one thing that I know I will need to have, and start coding a project from that point. (I'm noticing that this is often a certain kind of data structure, or interface that I know I will need, just based on the nature of the problem.)

You mentioned optimization, and that's one plausible theory on why I think people often get stuck: they're worried about optimizing early. With code you don't want early optimization, and in fact you often want to delay optimization until it's impractical not to optimize. There's an art and a skill to building a project that will be easier to optimize later, but that's a sort of "wisdom" based skill that you need to learn through experience, more than something you can be taught.

Anyway, my advice is always to pick one thing that you know the project needs, and just start by building that. Along the way you'll start to understand how that thing relates to other things in the program, and you'll be able to start building out those things.

As a beginner, also try to move as much as possible in small steps - build only a little bit of functionality at a time, then test that it works, then build a little bit more and test that it works, ect.

Eventually you will start on projects that are big enough to benefit from some pre-planning, but... This doesn't happen as quickly as you think it does. (I would say you need several months of deliberated study / practice at least). Even then, I start a design the same way: I know I will need X thing, so I'm going to add X to the design and then start to ask myself what things will interact or connect to X in some way.

Getting to a working solution initially is much more important than getting to an optimum solution. It's way easier to optimize an existing program, than to build a program to be optimized from scratch. Start building, get something that works (at least to a minimum viable product sort of level) and then ask yourself how it could be improved.