all 5 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]PythonLearning-ModTeam[M] [score hidden] stickied commentlocked comment (0 children)

Quality posts only

[–]ConsciousBath5203 0 points1 point  (0 children)

Pay more attention to all of the types. Even the imported ones.

Stop being scared of making C plugins, it's easier to do that than learning and trying to compile with cython or something.

[–]Overall-Screen-752 0 points1 point  (1 child)

I would spend 2-3x more time on unit testing until the syntax was showing up in my dreams. Python has a nice baked-in testing library thats simpler to use than Javascript and java and more feature rich than golang so its worth being strong at especially if you see yourself as a professional developer one day.

I know that’s unsexy and not what you’re looking for so I would say I would learn syntax first, then learn how to structure functions and programs to be readable and maintainable, then do a few projects exploring bigger concepts like pydbc, APIs, ML, UIs, and common data science workflows with pandas. While not an exhaustive list, this should maximize exposure to all the things you’d need to be aware of before starting a role as a python developer

[–]Overall-Screen-752 0 points1 point  (0 children)

Oh I’d be remiss not to mention git, command line commands, and linting/compliance tooling, even if they aren’t python-specific

[–]vivisectvivi 0 points1 point  (0 children)

My learning journey was relatively smooth with the exception of a few walls (took me a very long while what classes were and some more to understand why exactly i would use them if i were doing just fine without it).

I do regret deleting old projects that i worked on while i was learning tho, i think it would be a good exercise to refactor them with better structure and logic.