> reading programming books is a waste of time Erm... How about no? Unless you read useless books.
Contemporary students have no appreciation for reading and that’s going to be my competitive advantage.
Lessons Learned from Two Years as a Data Scientist
71–80 of 89 posts
Re: Lessons Learned from Two Years as a Data Scientist
#72Earlier quoted context omitted.
What should the net worth of someone like OP be by 25? I really wonder how far behind I am compared to my more savvy investor peers.
Comparing net worth when you're young makes no sense. It only makes sense in 20 years after things have had time to play out, and even then you still have a lot of time left. Even if you have a far superior strategy and an equal amount of starting capital you might not be that far ahead of your peers after only a few years, and even if you are there is no guarantee your strategy will continue working. In reality the…
I don't know about that, there are lots of people around my age like OP that aren't well represented in personal finance advice columns. My net worth is only around $300k as of today, which I'd imagine is on the lower end of most of these kinds of people (Dartmouth grads, ubermensch, Google engineers etc).
Re: Lessons Learned from Two Years as a Data Scientist
#73Seems like "data scientist" is now code for "junior Python developer".
I need a person who actually knows statistics, how to integrate, what Bayes' theorem means in practice, the difference between a confidence and a credible interval, etc.
What would this person be called in 2021? (I understand that searching for "data scientist" candidates would be a waste of my time.)
Re: Lessons Learned from Two Years as a Data Scientist
#74Earlier quoted context omitted.
Comparing net worth when you're young makes no sense. It only makes sense in 20 years after things have had time to play out, and even then you still have a lot of time left. Even if you have a far superior strategy and an equal amount of starting capital you might not be that far ahead of your peers after only a few years, and even if you are there is no guarantee your strategy will continue working. In reality the…
I don't know about that, there are lots of people around my age like OP that aren't well represented in personal finance advice columns. My net worth is only around $300k as of today, which I'd imagine is on the lower end of most of these kinds of people (Dartmouth grads, ubermensch, Google engineers etc).
Mate, this is delusional.
You're taking the top 0.1% of people your age that everything went right for and comparing yourself to them.
The only purpose to this is to throw a pity party for yourself.
Again, it doesn't make sense to compare net worth when you're young. Even if they have more money right now, if you are compounding better you will win in the long term.
Re: Lessons Learned from Two Years as a Data Scientist
#75Seems like "data scientist" is now code for "junior Python developer". I need a person who actually knows statistics, how to integrate, what Bayes' theorem means in practice, the difference between a confidence and a credible interval, etc. What would this person be called in 2021? (I understand that searching for "data scientist" candidates would be a waste of my time.)
> Seems like "data scientist" is now code for "junior Python developer".
No, it isn't.
> I need a person who actually knows statistics, how to integrate...
Maybe someone with a strong mathematical education and commercial experience in research... like the author of the post? Just because they focused on some more basic SWE concepts in a blog post doesn't mean that they don't know statistics.
> What would this person be called in 2021?
Data scientist, research scientist, probably some other titles too.
Re: Lessons Learned from Two Years as a Data Scientist
#76[deleted]
Re: Lessons Learned from Two Years as a Data Scientist
#77Seems like "data scientist" is now code for "junior Python developer". I need a person who actually knows statistics, how to integrate, what Bayes' theorem means in practice, the difference between a confidence and a credible interval, etc. What would this person be called in 2021? (I understand that searching for "data scientist" candidates would be a waste of my time.)
> Seems like "data scientist" is now code for "junior Python developer". No, it isn't. > I need a person who actually knows statistics, how to integrate... Maybe someone with a strong mathematical education and commercial experience in research... like the author of the post? Just because they focused on some more basic SWE concepts in a blog post doesn't mean that they don't know statistics. > What would this person…
Forgive me, but the blog is titled "what I learned from my first two years as a data scientist", and I'd rather trust the author on their word and not speculate.
(And the experience of me working with dozens of data scientists corroborates - "data science" means basic Python programming and the kind of boring trial-and-error feature engineering tasks you'd typically assign to a junior software developer.)
I want a person who actually uses statistics and math to drive business decisions, not just someone who took some statistics courses in university before becoming a software developer.
P.S. Honest question, really. I don't want to sift through 500 resumes before finding the person I want.
Re: Lessons Learned from Two Years as a Data Scientist
#78Earlier quoted context omitted.
> Seems like "data scientist" is now code for "junior Python developer". No, it isn't. > I need a person who actually knows statistics, how to integrate... Maybe someone with a strong mathematical education and commercial experience in research... like the author of the post? Just because they focused on some more basic SWE concepts in a blog post doesn't mean that they don't know statistics. > What would this person…
Forgive me, but the blog is titled "what I learned from my first two years as a data scientist", and I'd rather trust the author on their word and not speculate. (And the experience of me working with dozens of data scientists corroborates - "data science" means basic Python programming and the kind of boring trial-and-error feature engineering tasks you'd typically assign to a junior software developer.) I want a pe…
Ha, I did maths at uni and when I first graduated, the role you described was basically my dream job.
What you call the title is up to you, “data scientist” will probably net you a lot of people who mostly want to build machine-learning models, maybe “applied statistician” or “data analyst” is a better bet? Hiring out of a local uni is possibly also a decent choice if you can deal with having to bring some maths/stats grads’ business knowledge up to scratch.
Re: Lessons Learned from Two Years as a Data Scientist
#79Am I reading this correctly?: you were hired at MS with only cursory python knowledge? I’m very jealous and thinking more and more about going into IT after I leave uni for engineering (not software engineering). I know python well, along with a few other things I’ve picked up over the years (emacs/elisp, vim/vimscript, LaTeX formatting, JS, Common Lisp, APL, bash scripting, mathematica and matlab etc.). Would this b…
She probably did an interview focused on data analysis, statistics and experimentation. Her python skills probably weren't that relevant, as long as she can use libraries.
Re: Lessons Learned from Two Years as a Data Scientist
#80Seems like "data scientist" is now code for "junior Python developer". I need a person who actually knows statistics, how to integrate, what Bayes' theorem means in practice, the difference between a confidence and a credible interval, etc. What would this person be called in 2021? (I understand that searching for "data scientist" candidates would be a waste of my time.)
You are looking for a statistician.