4 ms·
All this boils down to "an unskilled engineer will misinterpret data even if they have it". I'll assume the Go team knows what they're doing, based on their tra
by cube2222 4y ago
All this boils down to "an unskilled engineer will misinterpret data even if they have it". I'll assume the Go team knows what they're doing, based on their track record so far.
There's a lot of very simple questions you can answer very reliably, too, like "what proportion of the users are still using a certain compatibility flag".
- marginalia_nu 4y agoMy point is that scientists whose job is to interpret data and construct experiments gets this wrong on a regular basis, despite years of training in constructing experiments and interpreting data, despite peer review, despite staking their career and reputation on not making these kinds of mistakes. They still happen! A lot! Interpreting data is very hard.
- masklinn 4y ago> I'll assume the Go team knows what they're doing, based on their track record so far. Funny, I’d assume the exact opposite. After all much of the understanding of privacy and statistics at scale was developed after 1980.
- philosopher1234 4y agoNormally Hacker News is ruthless with stupid comments like this, but some sort of unexamined feelings of inadequacy make Go devs a fair target. I hate this attitude.
- remram 4y agoGo is actually well known for dubious choices they reverted later, like not using libc, their weird major version scheme, or the absence of generics. There's a good record of charging ahead against the popular wisdom and being proven wrong.