This is really cool. I've found that learning the language is a small part of a larger battle. My new year's resolution has been to learn Python (I'm a JS / no

This is really cool. I've found that learning the language is a small part of a larger battle. My new year's resolution has been to learn Python (I'm a JS / nodeJS dev), and have been studying on and off the past few months. Biggest hurdle for me has been: - Understanding venvs. Why can't it just be like how node works? I get you need the venv so you don't use some wrong python version or install stuff into system python global space - Package management (still struggling with this - for example, downgrading packages seems to be a huge pain compared to node) - General ecosystem. If I want to trend towards AI / ML, do I need to learn pandas first, then get into jupyter notebooks, etc? Fortunately my work has an education stipend and I've bought lots of books, online courses (datacamp, realpython, manning books), etc, but I haven't found anything that felt "structured" in terms of just getting enough to know to hit the ground running in a productive way. I'm constantly re-arranging my internal course plan. - Version sensitivity. I'm used to semver conventions from JS, and python and its package ecosystem doesn't seem to practice this at all. It's really strange from my perspective that one package / project only works with python 3.7 but not 3.6 for example, or when a popular package is still stuck on a 0.x.y version