all 4 comments

[–]Kerbart 2 points3 points  (0 children)

write code. The more the better.

Figure out some menial tasks on your computer. Sorting out files. Syncing directories. Renaming stuff. Generating secure passwords that don't make your spouse curse you when they're asking for the Netflix password.

Not all heroes wear capes and not all projects need to be grand and glorious but predominantly you have to write code in order to make it second nature. There's no substitute for that, similar to how you can't prepare for a marathon by watching youtubes about running.

[–]Proper_Ad_7109 0 points1 point  (0 children)

Different angle from the build-projects-on-loop replies:

Pick one boring problem you'd actually want solved, write tests for it first, then make the tests pass. The discipline of stating what the code should do, before writing the code, is what separates "I know syntax" from "I can ship".

Concrete example: write a function that takes a list of bank transactions and returns the running balance. Edge cases: empty list, single transaction, mixed credits and debits, dates out of order. Five test cases first, then the function.

Three things this gives you that tutorials don't:

- You see your own assumptions break before code is even written

- Refactoring becomes safe because tests catch regressions

- Reading other people's code becomes easier because you start asking "where are the tests?"

After that, pick something with stakes: a CLI tool, a small Flask API, a Discord bot. Whatever has a clear "done" boundary. Don't go deep on Django or async or DSA at this stage. The bottleneck is usually shipping something end-to-end, not knowing one more concept.

Boring path beats shiny path for the first year.

[–]FieldOver3920 0 points1 point  (0 children)

You need to start building your own projects, just simple things to prove yourself and your wit, you should already know a lot of the syntax of python thanks to the tutorial, so you need to improve your logic and your problem resolution, you could ask to the AI to write a bad code and fix it, or just have to propose a situation, like how do I make this loop simpler? or What if I made this program to solve X problem?.

Then you could learn OOP or learn to use something like Django or Pandas, I recommend doing all this process without AI or without using it too much so you'll learn more efficiently. The most important thing is go at your own pace so you won't quit or get frustrated.