3 ms·

> I've written Python professionally for 20+ years. I've extended Python with C for funsies, but have never, not once, needed to do it at work. Well, different

> I've written Python professionally for 20+ years. I've extended Python with C for funsies, but have never, not once, needed to do it at work. Well, different folks have different experiences. One of the first Python-related things I had to do for my job was implementing a Python API for a custom C library that controlled some ancient hardware.

kstrauser 3y ago
Sure! That's totally a thing, and lots of people do that. But I've done tons of stuff in Flask. I wouldn't say you need to "Have a good understanding of Blueprints" to be a Python expert. Or "proficiency subclassing yaml.YAMLObject". Or "encyclopedic knowledge of Requests verbs". Or "strong opinions on Poetry vs Pipenv". Or "can use Ansible to configure a fleet of servers". Those are all common Python subjects in the areas I poke around a lot. You can be an expert data engineer without knowing any of those things. Just like you can be an expert backend engineer without having used Pandas a lot.
- Barrin92 3y ago
  >You can be an expert data engineer without knowing any of those thing Yes, but then you're exactly that, an expert data engineer, not an expert python programmer. Extensibility, in particular C interoperability is a core aspect of the language and it's to a non-trivial extent designed around it. Much of Python's utility rests on the fact that libraries exist who make use of this feature, especially in data science! You can be an expert software architect in Lisp and write many programs without resorting to macros, but if you want to call yourself an expert Lisper you'll need to know your macros.
  - kstrauser 3y ago
    I get what you're saying, but I disagree. You can write an awful lot of expert-level Python code without learning C. After all, the result of that interoperability is something that looks and acts like a Python object. It's not like users of that code have to know about C. They just write Python like usual, and it's magically (from their POV) faster than if it were also written in Python. As far as the data engineer bit, that's in the context of this article, which asserts that you need to know libraries predominately used by data engineers in order to be an expert programmer. I disagree, because Python is no more "about" data science than it's "about" web services or platform development or infrastructure management.
    - toyg 3y ago
      > Python is no more "about" data science than it's "about" web services or platform development or infrastructure management. Amen, brother. It's incredibly annoying how every new niche that Python accreted over the years, is full of people who firmly believe Python exists only for them. At one point it was LISP refugees, then markup junkies (like me), then sysadmins, then 3d artists (!), then webapp jockeys, and now it's datascience and machine learning. Every kid thinks the world is built for him, but pushing such limited worldviews can only box the community into a corner - just look at Ruby to see what happens then.

kstrauser 3y ago

Sure! That's totally a thing, and lots of people do that. But I've done tons of stuff in Flask. I wouldn't say you need to "Have a good understanding of Blueprints" to be a Python expert. Or "proficiency subclassing yaml.YAMLObject". Or "encyclopedic knowledge of Requests verbs". Or "strong opinions on Poetry vs Pipenv". Or "can use Ansible to configure a fleet of servers". Those are all common Python subjects in the areas I poke around a lot. You can be an expert data engineer without knowing any of those things. Just like you can be an expert backend engineer without having used Pandas a lot.

Barrin92 3y ago
>You can be an expert data engineer without knowing any of those thing Yes, but then you're exactly that, an expert data engineer, not an expert python programmer. Extensibility, in particular C interoperability is a core aspect of the language and it's to a non-trivial extent designed around it. Much of Python's utility rests on the fact that libraries exist who make use of this feature, especially in data science! You can be an expert software architect in Lisp and write many programs without resorting to macros, but if you want to call yourself an expert Lisper you'll need to know your macros.
- kstrauser 3y ago
  I get what you're saying, but I disagree. You can write an awful lot of expert-level Python code without learning C. After all, the result of that interoperability is something that looks and acts like a Python object. It's not like users of that code have to know about C. They just write Python like usual, and it's magically (from their POV) faster than if it were also written in Python. As far as the data engineer bit, that's in the context of this article, which asserts that you need to know libraries predominately used by data engineers in order to be an expert programmer. I disagree, because Python is no more "about" data science than it's "about" web services or platform development or infrastructure management.
  - toyg 3y ago
    > Python is no more "about" data science than it's "about" web services or platform development or infrastructure management. Amen, brother. It's incredibly annoying how every new niche that Python accreted over the years, is full of people who firmly believe Python exists only for them. At one point it was LISP refugees, then markup junkies (like me), then sysadmins, then 3d artists (!), then webapp jockeys, and now it's datascience and machine learning. Every kid thinks the world is built for him, but pushing such limited worldviews can only box the community into a corner - just look at Ruby to see what happens then.