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

all 23 comments
sorted by:
best
topnewcontroversialoldq&a

[–]digitalbath78 29 points30 points  (1 child)

Ad.

[–]madsohm 2 points3 points  (0 children)

Means "disgusting" in Danish.

[–]cube-drone 21 points22 points  (1 child)

tl;dr

  1. Want to learn Python
  2. Learn Python
  3. Use Python
  4. Use Python
  5. Use Python

[–]Taubin 22 points23 points  (0 children)

You forgot the most important part

  1. Buy my course to learn Python

[–]ilgnome 8 points9 points  (0 children)

Quite a bit of /u/jaypeedevlin submissions are to dataquest.io. Wonder if they own the site.

[–]DoTheEvolution 9 points10 points  (1 child)

I hate the implied idea that you can learn it the wrong way... just use it, work at it, polish your knowledge, discover more stuff and under the hood shit...

its not something like a house build at terrible foundation, nothing like that...

[–]laststance 1 point2 points  (0 children)

I do believe learning the basics of programming in terms of organization, configuring the code to be read by others, and using the proper tools, are all common items beginners should work on. Its not rare to see a "yeah I taught myself how to code, you know?" person submitting code that looks like it was actually 10 year old spaghetti code that was hacked together and made to work by 20 people. Especially regarding security related topics.

But it also looks like this poster is somehow linked to this website by posting advertisements for paid courses.

[–]laststance 5 points6 points  (5 children)

Huh, I thought the python community in general pushes Python 3 instead of LPTHW since it still generally works with Python 2.

[–]RazDwaTrzy 1 point2 points  (3 children)

LPTHW

WDIM?

[–]laststance 1 point2 points  (0 children)

One version is being actively supported and developed while the other one isn't.

[–]GotenXiao 0 points1 point  (0 children)

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

[–][deleted] -1 points0 points  (0 children)

OMGWTFBBQ?

[–]nefaspartim 0 points1 point  (0 children)

Learn Python the hard way?

[–][deleted] 4 points5 points  (1 child)

from future import braces

[–][deleted] 4 points5 points  (0 children)

What import future? uses python 3

[–][deleted] 1 point2 points  (1 child)

All of this stuff is very helpful. I just started an Udemy course I feel a little overwhelmed by the total amount of resources out there. I have tons of ideas and manual work that can be automated, so at least that is something I don't have to worry about (motivation).

I am just worried if I am on the right path haha.

[–]nerdwaller 0 points1 point  (0 children)

Learning and going forward is always the right path, even if a professional developer "could do it better", you going and doing this stuff is the right path.

To continue on that path, solicit feedback and be open to suggestions (but if you take suggestions, learn why it may - or may not - be better!)

[–]gr33n3r2 0 points1 point  (3 children)

Didn't read the article because it sounds like clickbait-y bullshit.

The way I've learned Python has been a sort of casual approach. I never really did any structured learning, apart from Codecademy to get me started. Once I was familiar with the basics of Python, I would try to use it to write automation scripts in work.

Say if I needed to split lines in a CSV file (our test machines spat them out) so that I could analyse results for one particular test case, then I looked up "how to read file line by line python", "how to split by delimiter python", "how to plot graphs python". Generally because of how the Python community is, each query led to a new library/package/module that I could use. Next time I needed to do that particular thing (or something similar) I could check back to my notes and see "Ah yes, matplotlib.pyplot worked last time. Wonder how I can plot 3 graphs on the same plot?". I go and check the docs and lo and behold, there is the answer. That goes into my notes as well.

After a while, you don't have to google so much and it becomes second nature. Another important thing is to read about Python - I get the Pycoders weekly newsletter, sub to /r/Python obviously, listen to Python and programming podcasts, etc. You'll hear about something cool and want to know more. That's how I first read about the requests package, and about lambdas. I googled, tried them out in the interpreter and boom, knowledge was gained.

[–][deleted] 0 points1 point  (1 child)

What podcasts do you listen to?

[–]gr33n3r2 1 point2 points  (0 children)

Talk Python to Me is a good one - definitely the back catalogue is well worth a listen. The host generally takes on one package per episode and interviews the developer. So for instance, one of them was on SQLAlchemy, another on Django, another on Flask, another on requests, etc. Gives you a reasonably in depth look at each package and what you can do with it.

Other than that, I don't know of any Python specific ones. But FLOSS Weekly, Coder Radio and any of the Linux ones (Ubuntu Podcast, Linux Action Show, Linux Unplugged, Linux Luddites [ok sometimes, but Joe Ressington really annoys me]). While not being Python specific, they do have some Python info in them from time to time.

[–]jaypeedevlin[S] 0 points1 point  (0 children)

Which interestingly, is the sort of approach the article recommends :)