wat up /g/?
i am a semi-beginner programmer who was originally studying social sciences, but then made one of those radical decisions and decided to switch to programming instead. currently trying to finish my bachelor's degree even though i give 0 fucks about it, but it is still better than being a simpleton with just a high school diploma.
i initially started programming with hlsl a couple of years ago, i know it's fucking weird just don't ask. also took some java courses in school (they were mostly using acm library, didn't really java but still) these days i am trying to learn python from different sources. i started with coursera but it was not enough. i personally don't like being a pseudo-programmer by reading 200 pages long dumbed-down programmer books and stackoverflowing every single fucking thing. so i made some research and discovered mark lutz's python books. the guy is a little bit retarded but his writing is really comprehensive which is the way i like it. currently i am reading learning python 5th edition and i am halfway through.
so i have some questions to masters of /g/:
0. which theoretical subjects would be really beneficial for the learning process along the way?
1. is there any comprehensive resources you know of for python? i really want to learn the language, its backbone, what makes it tick etc. basically i want to python for real, i want to come near the dangerous borders of autism of python without transcending beyond them.
2. my current plan for my future arsenal is this:
implementation level-wise,
mid-to-high: python, some html and js for web stuff
mid-to-low: c++, r
which ones would you add/modify if you were aiming to be a backend developer? especially have no fucking clue about sql and web development.
shoot.
>>59188180
>its backbone, what makes it tick etc. basically i want to python for real, i want to come near the dangerous borders of autism of python without transcending beyond them.
You're gonna want to look up python idioms. There are lots of books, videos and online articles about them. Basically stuff like you should x instead of y because it will save memory. That kinda stuff. Python is so abstract that it's difficult to get very deep but you can definitely learn about good habits vs "don't ever do this even though it's allowed"
>Effective Python: 59 Specific Ways to Write Better Python
is a pretty good book
>>59188180
>originally studying social sciences, but then made one of those radical decisions and decided to switch to programming
>>59188180
That book isn't suited to be read from cover to cover. Reading it that way is a surefire way to end up in a padded room or end up kysing yourself.