Earlier quoted context omitted.
Not really. You just get seen as the product owner/project manager.
That's a really good point. I tend to be seen as a product lead / owner / stakeholder, so I feel like I'm being called out. lol I think one difference is the software engineers see me as someone who is helping them by making their life easier. I'm not just throwing work at them blindly. I'm working with them. Also, they like it when I include them in the data science brainstorming sessions to solve difficult problems…
We don't need data scientists, we need data engineers
231–240 of 367 posts
Re: We don't need data scientists, we need data engineers
#232Earlier quoted context omitted.
I'm not sure about crappy quants. Some people of the "quantitatively inclined trader who has learned Python" variety are never going to be good at the engineering side - it takes years to learn to be a good software engineer, and that's not a good use of time, for them, or for their employer. But they can still do useful work. The trick is to figure out how to work effectively with those people. Build infrastructure…
If they're using a dynamically typed language to do monetary calculations, it's not going to be ideal. Researchers do not need to have deep programming experience, but they have to be comfortable enough to use an environment that can lend itself itself to the problem at hand. On the quant side, unlike on the data science side, the barrier of entry on the programming side is a bit higher. To solve this problem many fi…
And yet, Q.
Re: We don't need data scientists, we need data engineers
#233My experience is in quant hedge funds, where sometimes you get some guys who develop the strategy and some guys who put it into production. Yes, I do admit there can be some specialization in terms of time spent on science vs engineering. But you really need people who understand both. Particularly if you have a strategist who thinks his job is just to dream up profitable models, he ends up carving that role out in a…
[deleted]
Re: We don't need data scientists, we need data engineers
#234I can't recommend the Data Engineer career enough for junior developers. It's how I started and what I pursued for 6 years (and I would love doing it again), and I feel like it gave me such an incredible foundation for future roles : - Actually big data (so, not something you could grep...) will trigger your code in every possible way. You quickly learn that with trillions of input, the probabily to reach a bug is ei…
I wonder how: 1. one finds organizations that have data engineering 2. gets hired to said organization with software engineering background.
Re: We don't need data scientists, we need data engineers
#235I can't recommend the Data Engineer career enough for junior developers. It's how I started and what I pursued for 6 years (and I would love doing it again), and I feel like it gave me such an incredible foundation for future roles : - Actually big data (so, not something you could grep...) will trigger your code in every possible way. You quickly learn that with trillions of input, the probabily to reach a bug is ei…
And where would you recommend someone to start a data engineering path. Any book, learning source?
Re: We don't need data scientists, we need data engineers
#236We need [brand new definition of the same, which most people are even more confused what it means and how it's different from the old]!
Re: We don't need data scientists, we need data engineers
#237Re: We don't need data scientists, we need data engineers
#238Re: We don't need data scientists, we need data engineers
#239Re: We don't need data scientists, we need data engineers
#240I can't recommend the Data Engineer career enough for junior developers. It's how I started and what I pursued for 6 years (and I would love doing it again), and I feel like it gave me such an incredible foundation for future roles : - Actually big data (so, not something you could grep...) will trigger your code in every possible way. You quickly learn that with trillions of input, the probabily to reach a bug is ei…
And where would you recommend someone to start a data engineering path. Any book, learning source?
It's shockingly difficult, and something that only experience can teach.