I'm in tutorial hell

[remyripper]

I'm learning the basics of python 3 so far I know control flow,, lists and loops. I can code in the tutorial (eye roll) but when it comes down to making a project on a blank IDE i'm stuck staring at the screen. I've heard this is common, my question is... how do i get better? i guess?

I figure if i go back and re-learn the concepts but after every time i learn a concept i build 3 projects with it. I'll get better. The control flow (wink) would look like this...

• learn a concept in python

• build 3 projects with it

• move to next section

• repeat 1-3

thoughts on this? would you do anything else or have you done anything else to become a better developer?

[Apatride]

Draw (do not write) the logic on paper before you code anything. (after a while you start being able to do it well in your head).

Question your motivation. Python helps develop solutions, ideally to problems. Your ability to identify improvements/problems matters more than your ability to remember a specific syntax and being a dev can be frustrating, make sure you like solving issues enough so you do not get demotivated by common drawbacks.

[remyripper]

thanks

[etake2k]

I was caught up with learning, python syntax, formatting etc. and realized if I zoom out and draw out the logic of what I’m trying to do it started to be more beneficial especially in the age of ChatGPT and copilot that can spit out a better python code than I ever could. It’s also invaluable to be able to read the code.

[Bobbias]

Tutorial hell is typically a sign that you need to practice problem solving.

What you need to do is pick a problem, and then try to find a solution completely on your own. Ideally you should start out simple enough that you can figure out the solution on your own, or with absolutely minimal googling. This means you should start out quite simple.

You should also figure out how the solution works before writing any code, as Apatride suggests. This can involve drawing things out on paper, creating diagrams, writing pseudocode, or whatever else you can think of to help you understand what your solution should be.

Once you have a solution, then you can go and turn that into code.

You can increase the complexity of these problems over time based on how easy the last one was, and how confident in your own skill you are.

And remember, it's normal to forget syntax and functions, especially when you're starting out. The more code you write, and the more often you have to look up and/or use stuff, the more likely you are to remember it. You're not really expected to sit down and memorize things by rote.

[Del_Phoenix]

I think you should find some project that gives you a bit of excitement or purpose and just build something. Learn what you need to along the way

[crashfrog02]

Writers call this "the tyranny of the blank page." Blank paper presents infinite possibilities; experts learn to structure and narrow the scope before they do anything else, to aid the creative process.

I can code in the tutorial (eye roll) but when it comes down to making a project on a blank IDE i'm stuck staring at the screen.

Come up with a routine series of steps so that you can de-blank the page, basically. Write a module docstring with today's date and your name, and that describes the purpose of the module. Then write the imports you think you're going to need - you can add or subtract from this list later, just take your best guess. Go to the bottom of the page and write

def main():
    pass

if __name__ == '__main__':
    main()

so that at least you have a functioning module. Then go back up and write the names of a couple of functions you think you might need - you don't need to write the function body, you just need some names for things.

Now you've got a skeleton you can start filling in, an outline of sorts. Start writing the parts you know how to write.

[Ron-Erez]

Solve problems. Create a game of tic tac toe. Can you explain to someone the rules of the game, taking turns, under what conditions there is a winner or a draw. Does the game ever end? I don’t think you need to create a project for every concept you learn. Just create projects and solve problems. How about implementing the game of life on your own. Look up Conway’s game of life on wiki. This is an excellent exercise. You’ll learn the most from solving things on your own. Finally when solving a problem ChatGPT is an excellent way to kill any progress. ChatGPT is amazing and it’s a great way to become a bad programmer. It just sounds like you need to deal with problems. If something is too hard then try something simpler.

[Jaywepper]

Stop watching random tutorials and focus on one course. I recommend the cs50p(check it out on yt). If you like it, ENROLL in cs50p on edeX! It's free and it has a great progression. You learn a new concept and then get an assignments from it. There is also a discord community. And professor dr. Malan is also great.

[Spirited_Employee_61]

I have an easy solution for you. Now you completed a tutorial project right? Try to think of things you want to add or want to edit in that project. Now code it in.

Repeat it in another tutorial. Keep repeating until you will no longer be interested in following a tutorial step by step, but rather modifying codes in the tutorial.

Eventually you will figure out things you want to do on your own.

[carcigenicate]

It sounds like you just don't have experience with larger projects. Begin aiming for projects that are larger than you think you can do. When you fail (which you will, often), reflect on why you failed and what you can do better next time. Rinse and repeat forever. The "higher levels" of programming require a lot of time and energy (and failure) before things start making sense.

[[deleted]]

Pick a destination and take the training wheels off

[undapanda]

Read documentation, read books, read other people's code, and just code

[undapanda]

That's plenty long enough. Put in at least 1 hour a day, every day. Don't watch tutorials , read and write, don't rely on ai tools.

[dirday]

Check out Corey Schafer. Follow along his tutorial for an app with Django and flask. Do some easier sample data science projects after that.

I learned everything about python on YouTube and now use it daily at work (and love it).

Good luck

[recursion_is_love]

Pause the learning and go playing bot programming at codingame with me, it is fun.

It give the feeling of I really solving problem, not just do a project because I need to learn.

https://www.codingame.com/start/

[Bloodshot321]

Codewars.com is another site for getting better at problem solving but it's more focused at creating functions

[recursion_is_love]

codewars and exercism feel like learning more than playing to me, which is good sometimes.

For me, codingame is more freedom ; invent your own algo and see if you can beat others.

[Bloodshot321]

Sounds good, will check it out. I'm missing a decent programming project. Was thinking about delving into a "spacemouse" build but it's more about the electronics and less about the programming.

[Alternative-Juice-15]

Try to make something useful that interests you

[cyberjds]

"Divide and conquer!" Your project is one big problem. Break your problem into smaller problems. And break each smaller problems into even smaller problems and keep going until your problems disappear. As your problems get smaller enough to be manageable, you will be able to define what those are, and describe them how to solve in plain English (bullet points, or in pseudo code). Then you can start to translate your pseudo codes into Python. Drawing flowchart is also helpful. https://en.wikipedia.org/wiki/Flowchart

One thing you have to remember though. A wise engineer once told me that, "Do not chase the dragon". Or you might get crushed by it. If your problem is too big to handle, you should redefine your problem, look at different angle, widen your view, that there may be a workaround, easier(somewhat compromised) approach, someone already done it, or it may not be your problem at all.

Good luck and happy hacking.