Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lessons Learned from Two Years as a Data Scientist

dawndrain.github.io

Post reply on HN
Print view View original

81–89 of 89 posts

Re: Lessons Learned from Two Years as a Data Scientist

#81

Post by int_19h »

listenallyall wrote: post #63

This reads like a pretty "wet-behind-the-ears" professional who doesn't know what he doesn't know. > There's no Java awfulness like ... instead it's just `cars = []` I mean, there's very good reasons for static typing. And if he was using Kotlin, he could specify whether the variable `cars` was itself immutable and whether the list was immutable (`val/var cars : List /MutableList ` > notebooks yea, Jupyter kernels ex…

Modafinil is literally known as "the Wall Street drug", and it's not because the old people there use it.

Re: Lessons Learned from Two Years as a Data Scientist

#82

Post by int_19h »

ekianjo wrote: post #58

> reading programming books is a waste of time Erm... How about no? Unless you read useless books.

"Useless" accurately describes the majority of published books in the industry these days. So you can spend a lot of time finding the right book... or you can just dive straight for the spec.

Re: Lessons Learned from Two Years as a Data Scientist

#83

Post by rejectedandsad »

ZephyrBlu wrote: post #74
rejectedandsad wrote: post #72

Earlier quoted context omitted.

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.

I don’t know if that’s true - I’m very skeptical of the idea $300k is anything but the very low end of Dartmouth grads.

Re: Lessons Learned from Two Years as a Data Scientist

#84

Post by eointierney »

thom wrote: post #21

I felt like this article was a bit light on data scientist specific advice, and while I am not one, I do herd them for a living, so thought I'd put some random thoughts together: 1) Quite often you are not training a machine to be the best at something. You're training a machine to help a human to be the best at something. Be sure to optimise for this when necessary. 2) Push predictions, don't ask others to pull them…

Thank you for superb advice. Like all good advice it is clear, general, based on experience, and anthropocentric.

It may not be earth-shattering, but that's probably a good thing.

I especially like numbers 1 and 10. If I was looking for a job I'd like to work with you.

Re: Lessons Learned from Two Years as a Data Scientist

#85

Post by systemsignal »

comp_throw7 wrote: post #20
kbenson wrote: post #7

Earlier quoted context omitted.

Almost definitely Warren Buffett, who went so far as to make a very public bet that index funds performed better than hedge funds (and thus most active investing). You can see details on the deal and outcome here https://www.investopedia.com/articles/investing/030916/buffe... Also, he's got tens of billions. Edit: Or maybe not on reflection about the "faster than anyone" bit. I dunno.

Sam Bankman-Fried, unless I miss my guess.

yeah think that's right, esp considering their background at FTX

Re: Lessons Learned from Two Years as a Data Scientist

#86

Post by thom »

eointierney wrote: post #84
thom wrote: post #21

I felt like this article was a bit light on data scientist specific advice, and while I am not one, I do herd them for a living, so thought I'd put some random thoughts together: 1) Quite often you are not training a machine to be the best at something. You're training a machine to help a human to be the best at something. Be sure to optimise for this when necessary. 2) Push predictions, don't ask others to pull them…

Thank you for superb advice. Like all good advice it is clear, general, based on experience, and anthropocentric. It may not be earth-shattering, but that's probably a good thing. I especially like numbers 1 and 10. If I was looking for a job I'd like to work with you.

Thank you for making such a kind comment!

Re: Lessons Learned from Two Years as a Data Scientist

#87

Post by ekianjo »

int_19h wrote: post #82
ekianjo wrote: post #58

> reading programming books is a waste of time Erm... How about no? Unless you read useless books.

"Useless" accurately describes the majority of published books in the industry these days. So you can spend a lot of time finding the right book... or you can just dive straight for the spec.

> or you can just dive straight for the spec.

in practice its not even following the spec, its just copy pasting stack overflow answers.

Reading a book at least gives a more sustainable structure to what you learn.

Re: Lessons Learned from Two Years as a Data Scientist

#89

Post by jingw222 »

alcoholic_byte wrote: post #88
jingw222 wrote: post #62

Ironic that someone who works on VSCode at Microsoft does not use the notebook in VSCode but instead Jupyter

Have you tried running Jupyter-notebooks inside of VSCode? The performance and ressource-usage is abysmal.

Of course I have. Being able to integrate everything into a single software would be great. Every couple of months I tried using notebooks in VSCode I switched back. It’s so bittersweet
Post reply on HN