310 karma · joined August 31, 2010
I have very redundant data. I often see 10:1 compression. It's a lot less when I have hashes, addresses and timestamps.
It was a great deal then.
https://www.youtube.com/watch?v=xZbwTCrnktY - Cassidy - I'm a hustler
https://www.youtube.com/watch?v=sv6CbP4kVno - Lil Wayne - Hustler Muzic
For presentation, I toss the data on Excel. Bold the headers. Change the number type (pct, $, etc) to the correct one.
I would say that it has made my life a lot easier. There is one repository where the data is held. If I mess up, I go back to the master tables. In Excel, I would usually start over. Joins are easy. Excel can do some things better. When it can, then I use it. It's not a one or the other. It's ok to use both.
No updates. Fast inserts.
You can only join two tables at a time, but the joins can be chained to deal with this limitation.
I tried Monet. It wasn't very stable for me. I didn't stick with it long enough to judge it. ClickHouse has backing of Yandex. I think that makes a huge difference.
I have used Clickhouse for the past year. Thrown 3000 column by 120 million row tables on it. It worked where PostgreSQL came to a halt. Different use cases really.
I fits my use case perfectly. Large amounts of data with no updates and tons of aggregations. It's lighting fast.
R is not inferior to Python. Perhaps for general programming, but for stats and visualization, R is the gold standard.
The level of the problem doesn't matter. Working at Google is an elite job. We could go a level lower to Stanford. Asians are under represented at Stanford. We could go down a level to an elite California High School. Asians are still under represented. Blacks and Hispanics are really under represented at this level. It only gets worse for them the lower you go at elite institutions.
I use the general population because that is where the workers are coming from. If the pool of qualified applicants does not match the general population, then somewhere the qualification process failed.
> about 2% of employees would be black, 5% Hispanic, 30% white and 63% Asian.
These two comments say the same thing. Mine is standardized.
Your take away from all this is a little strange. The Google numbers say that Asians are 25 times more likely to be hired than blacks. That has happened in real life. No one complains about that. I have read that Google is too Asian though.
People harp about less-talented people not deserving to be there, but that is already the case. From a statistical point of view, Whites are over represented at the expense of Hispanics and Asians with a higher IQ. Real life is messy, but you get the idea.
This battle has been fought already and enough people at Google were convinced that there was a bias in their hiring practices. So, now they are in the process of correcting.