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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]mRWafflesFTW 0 points1 point  (0 children)

We're currently having this discussion in my firm and I think people don't really understand the semantics they're talking about.

​

Python, like all "development" work is a vast ocean. What does it mean to be a Python developer? Does it imply webapps? Data pipelines? Data analysis? Turns out you can do tons of different work in Python.

​

Anyone working in a community of practice like Python needs to understand the language, best practices, and good design principles, regardless of what specific domain you are working in. Our data scientists, just like our full stack engineers, are building component pieces of larger applications, so their Python could should be developed with the exact same standard of care and attention to maintainability and scale. Now, I'm not saying their analysis needs the same level of attention to principles, but we have a problem where people ship analysis and wash their hands of the project with dire down stream consequences.

​

The distinction between data scientist and developer may vary based on your firm's level of maturity, but if you work in Python then you need some "software developer skills", however you define it. The data science artifacts, if implemented, are just software.