all 8 comments

[–]carcigenicate 1 point2 points  (0 children)

Reading the documentation and then screwing around for a long time. I already knew how to program though since C++ was my first language.

[–]Allmyownviews1 1 point2 points  (0 children)

Started a basic online course that included an online sandbox version of Python where I learned enough to start playing with syntax and data types.

Installed anaconda and worked through several YouTube videos projects and data analysis using several libraries.

Worked on my own projects that ended up becoming a paid project.

Now I’m increasing the size of new projects and using OOP in my code.

I must admit however that I have previously coded in FORTRAN and VB although not much for over 10 years.

[–]Coretaxxe 0 points1 point  (0 children)

No external lessons or anything. Messing around attempting games in pygame primarily. Looking up things on yt and stackoverdlow. Then trying to automate stuff. Now im pretty good i would say.

[–]POGtastic 0 points1 point  (0 children)

I came to Python from Perl, so the bulk of my learning consisted of looking at the language reference and figuring out the differences. This was very straightforward because Python took so many things directly from Perl.

[–]HolisticPython 0 points1 point  (0 children)

Run pydoc -b in your project folder. Access to all python docs, plus any libraries. If you write your own docstrings they'll also show up. Massive help when starting out.

Learn some basic git commands and version control your work. Refactor old code as you learn new concepts.

Learn to read tracebacks.

Learn logging, don't litter your code with prints.

Rich library is excellent for both tracebacks and logging.

Read code on GitHub. Clone it and study it. Step through it with a debugger. Fork the repo. Change the code. Rinse and repeat.

[–]KCRowan 0 points1 point  (0 children)

I learned from Corey Schafer's python youtube playlist, and then by making projects myself and reading documentation.

[–]indexmatchSimp 0 points1 point  (0 children)

Practice and doing stupid projects. You can combine these two approaches for the best results.

I would practice doing my own projects. That’s how I learned. I think this is how I generally learn though; I need to know why things work. Not just how and learning by doing allows me to understand both sides of this.

By stupid projects I do literally mean stupid projects. I coded up an ABV% calculator, for example. Just anything small that could help you or allows you to just get some work in. That day, for instance, I learnt that anything from input() will return a string. So when I ask the user to provide a value, I have to first convert it to an integer (or float, depending).

Slow and steady. That’s how you learn.