Python. 42% of programmers use it at work… But here’s why you should STILL NOT learn it (first) — 👇 click here for free coding advice 👇
https://aaronjack.dev
Fill out this form, I’ll send you a custom email with guidance & tips

Connect with me
https://instagram.com/aaronjack
https://twitter.com/aaronjacked
https://tiktok.com/@aaronjacked

#coding #programming #python

source

25 Comments

  1. After two years in the industry now, I totally agree with you. Python is a nice language to learn for beginners but if you want a job and you compete with someone who learned java or c# you are basically out of the race.

  2. I think it really depends on personal preferences for example my first language was java and when I wanted to learn python it felt like python was a lot harder to understand

  3. I studied Geography and GIS in college and am trying to make the switch back into the GIS space after working in Education for a while. It seems like python would be an excellent language to support GIS analyses, but some people also recommend R. I realize your thing is mostly Front End, but do you have any opinions on how one should decide between these two languages when considering a data science or data science-adjacent career?

  4. You my friend are quite wrong on a few things. First, Python as a language is not bad starting choice. Most interviews focus on logic and problem solving using code – with Python you worry about the logic and not get stuck in the complexity of the language. Say you have a timed interview that involves reading some text file and manipulating it – well with C++ and Java, you will spend quite a bit of time looking up how to manipulate IOstreams etc unless you are HIGHLY proficient in them. And even then, Python data structure flexibility means you aren't debugging C++ template errors for that HashMap (easy way to blow through an interview without actually even touching the core of it – logic). Other things you mentioned like databases, CAP Theorem etc – of course it depends on position but unless you are applying to say a distributed systems job, most SE jobs don't grill you on databases let alone theory…

  5. I agree with you when you learn a language, you need to see what are you going do with it in the filed and the job opportunity for it, If you learning for the fun of it then thats another thing

  6. Some people learn their first language just to learn to program – like when they do it as a kid. I never got around to Python, but I learned lots of languages, and Applesoft BASIC was my first language.

    I've also found that a lot of textbooks on computer science concepts use python for their example programs.

  7. Hi Guys

    I am currently hesitant between the AWS or the Python course but also the Digital Marketing which I have learned before but still looking to go deep into it.
    Could you please share your suggestions with me between the AWS and the Python.
    Thanks

  8. True, but:
    1. The same argument could be made for almost any other language.
    2. For the rest of the langs that that argument may not be made, there could be another 100 reasons to not pursue it as your first.
    3. Sh*t code is sh*t code. it doesn't matter if it's python, ruby or go or rust or whatever. So they could fall under scale/stress too.

    But I agree with JS/FE being a better alternative. At the end of the day, when finding a job it's almost just a matter of React/Vue/Angular, but there are a gazillion backend langs and each lang has its own set of frameworks 🤷

  9. I've been learning Python everyday whenever I had any free time. But unfortunately I've lost my motivation because of this video. Trying to forget this and come back to learning…

  10. I appreciate the honesty! I've already started looking into python though, so I'll stick with it until I understand it entirely. My concern is only that I'm unsure where I could actually say yes, I understand it now, I can learn something else ^^

Leave A Reply

Please enter your comment!
Please enter your name here