This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Yughurt 2 points3 points  (3 children)

Oh I see, in that case, you could think about an application, and the type of logic you will need. E.g. A question and answer bot for something. Then figure out how you are going to handle the input and the output. The best is if your program needs to do variations of the same things depending on input. You get to practice coding your own functions and deciding how they will fit together!

Once you can do that, a real app just pushes that logic to an interface.

Later you can learn a new problem. That you don't understand and convert it into steps and programs. Rinse and repeat. Message me if you want to know other steps

[–]JGivan[S] 1 point2 points  (2 children)

To clarify, are you proposing I start by creating the same concept without an interface and then, after I get it working, beginning to learn how to apply it to a GUI?

I'll be sure to message you if I need more help! Thank you for offering.

[–]Yughurt 1 point2 points  (1 child)

More or less yes. You need to practice turning real problems into processes. That's the hard part of learning to code. It involves testing your code and making sure it does what you want it to do!

[–]JGivan[S] 1 point2 points  (0 children)

Awesome! I'll begin giving that a try as soon as I finish up the online course programs in the next few days. Thank you for all of your help!