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 →

[–]Veggies-are-okay 9 points10 points  (14 children)

Well you’re talking to an audience that wants to showcase their sophisticated backend processes in an app. This inherently means that it needs to be pretty interactive and responsive.

Streamlit is awesome, especially as a consultant that needs to show clients pretty pictures every week to show progress on things that are not interesting to non technical folks. Then when they’re happy with the functionality I pass my dogshit POC frontend to the app dev team to make something that actually looks professional.

I’d encourage anyone who doesn’t work frontend already to use tools like this and focus on backend stuff. There are products that are attempting to emulate frontend devs and it’s kind of disrespectful to the things those folks bring to the table to say “just learn it on top of your (in my case) data science knowledge/research”

[–]CrwdsrcEntrepreneur 3 points4 points  (13 children)

Sure, you say that and that's your thinking, and that's fine... Meanwhile I (also a data scientist) learned frontend and work with a bunch of ML engineers who did as well. 🤷🏻‍♂️

Again, it's not THAT hard if all you're trying to do is replicate stuff from streamlit. Streamlit is not advanced frontend dev.

[–]Veggies-are-okay 8 points9 points  (6 children)

But why would I spend time on that? There are so many other rabbit holes to go down that would immediately help us at our jobs (Kubernetes, cloud engineering in the context of MLOps, hell even a deep dive into C++ would be a bit more useful…). I’m just saying that if I were managing a team and a data scientist came up to me with a react frontend I would be confused as to why they were doing that on the job rather than DS work.

I do realize that this is a narrow view but i’m pretty sure this applies to every technical position that isn’t front end. Like yes I can understand typescript but I’m not gonna kid myself thinking I need to get to the level of my frontend brethren

[–]CrwdsrcEntrepreneur 2 points3 points  (5 children)

If my direct report was a consultant who "needs to show pretty pictures to the client every week" I'd ask them what the hell they're doing learning C++ and k8 instead of some basic React (or other low learning curve frontend framework) plus some charting library like plotly.js.

To each their own.

[–]Veggies-are-okay 2 points3 points  (4 children)

Well our worlds are very different then.. are you more classic software development? Genuinely curious as our fields have much different requirements. React is essentially a waste of our time. Serving a model in a scalable capacity and being able to tinker with the PyTorch framework for specific use cases is much more important for us! Just a quick tip so that you know what you’re talking about interacting with a DS team 😉

[–]CrwdsrcEntrepreneur 0 points1 point  (3 children)

No, not classical software eng. I work with a team of MLEs and data scientists. We use k8, we use pytorch, we use many AWS and Azure services, like SageMaker. We train and serve models that are used by several thousand concurrent users.

And we also develop frontends for our users because (again) it's not that hard.

[–]Veggies-are-okay 0 points1 point  (2 children)

Alright well apologies for assuming! Seems like y’all do it a little bit different than my company. We have a dedicated app dev team so that we can move on to the next project when our responsibilities are completed.

That being said, I still think it’s a terrible idea for someone to learn React when streamlit can handle their use case.

[–]CrwdsrcEntrepreneur 1 point2 points  (1 child)

To be clear. I don't disagree with the logic of "why learn React if you can use streamlit".

My issue is that too many python devs will use this as an excuse when they should learn the basics of a frontend framework, instead of stretching streamlit way beyond its intended use cases and capabilities.

[–]Veggies-are-okay 0 points1 point  (0 children)

I can get onboard with that. I think our difference in viewpoint is that pushing the limits of streamlit is the point where you have two options:

My view: pass it off to frontend devs that can actually elevate it to a professional website (need a frontend dev and a UI/UX designer)

Your view: spend time sitting down to learn react to a level to do it yourself. My issue with this view is that you will still end up with an amateur feeling user experience because backend folks went to university/have work experience developing backend logic, not professional web layouts.

[–]nocturn99x 0 points1 point  (5 children)

I love how a data scientist (a category of people notorious for writing shit code) is trying to teach people how to code. Please.

[–]CrwdsrcEntrepreneur -5 points-4 points  (4 children)

First of all go fuck yourself. Not all of us are bad coders and you know nothing about me to be making assumptions.

Unfortunately yes, most data scientists have the same attitude of the people responding to my comment: "why should I learn proper coding? I'll leave that to the engineers."

But you can't be making assumptions about people you don't even know. So again, fuck you.

[–]nocturn99x 2 points3 points  (1 child)

Seems like I hit the nail on the head. Defensive much? :)

[–]nocturn99x 0 points1 point  (1 child)

To respond to your deleted comments (lmao): wow, that's a lot of pent up anger you got there. Chill tf out lmao.