Totally agree. One small correction: sociopath, not psychopath. Articles like this are just trying to making it ok/mainstream to be a sociopath, which is a TERRIBLE idea.
I agree. This worries me.
Completely agree. However, if everyone adopted this viewpoint, it wouldn't be effective. Shhh! Don't tell everyone. ;)
Go v.s. Swift's flatMap? Monoids v.s. non-monoids. Hard to compare the two.
I'm an atheist buddhist.
I have only ever been a salaried programmer since I graduated college (I graduated pretty late after screwing around for 6.5 years). I'm 32 years old now. I have been recognized as a Senior engineer for about 3-5 years…
I'd prefer to read HN and not get depressed as fuck.
Is this what HN has become? A fail-blog? :(
I have another question: Why are people still doing joins in this day and age? Big data + joins = teh suck. I'm a big fan of compressed denormalized data.
Simplistically speaking, you don't always have to do table scans. I run into this every day: "Let's use Hadoop and keep doing full table scans! It's scalable! We just add more machines!" Yeah, except continuing to scan…
I did too, mainly because S3 + Hadoop isn't going to provide the locality and speed that HDFS would. I don't think it's a fair comparison.
I knew I smelled me some Cloudera... :) HBase: I think HBase (based on the sorting of qualifiers within rows) would be suited toward the "ranking" problem, that's why I brought it up. I see this as being a map-only job…
Completely agree with everything you said. I disagree about Impala, right now. It has great potential, but I don't think it's prod-ready yet. Also, why no mention of HBase?
nice.
Totally agree. One small correction: sociopath, not psychopath. Articles like this are just trying to making it ok/mainstream to be a sociopath, which is a TERRIBLE idea.
I agree. This worries me.
Completely agree. However, if everyone adopted this viewpoint, it wouldn't be effective. Shhh! Don't tell everyone. ;)
Go v.s. Swift's flatMap? Monoids v.s. non-monoids. Hard to compare the two.
I'm an atheist buddhist.
I have only ever been a salaried programmer since I graduated college (I graduated pretty late after screwing around for 6.5 years). I'm 32 years old now. I have been recognized as a Senior engineer for about 3-5 years…
I'd prefer to read HN and not get depressed as fuck.
Is this what HN has become? A fail-blog? :(
I have another question: Why are people still doing joins in this day and age? Big data + joins = teh suck. I'm a big fan of compressed denormalized data.
Simplistically speaking, you don't always have to do table scans. I run into this every day: "Let's use Hadoop and keep doing full table scans! It's scalable! We just add more machines!" Yeah, except continuing to scan…
I did too, mainly because S3 + Hadoop isn't going to provide the locality and speed that HDFS would. I don't think it's a fair comparison.
I knew I smelled me some Cloudera... :) HBase: I think HBase (based on the sorting of qualifiers within rows) would be suited toward the "ranking" problem, that's why I brought it up. I see this as being a map-only job…
Completely agree with everything you said. I disagree about Impala, right now. It has great potential, but I don't think it's prod-ready yet. Also, why no mention of HBase?
nice.