30 karma · joined July 22, 2010
Well, I work for a Hadoop distribution, so I may have some biases showing through in my setup. I like to use spark in conjunction with Hadoop; I've never actually used it stand-alone before, honestly. For relational data, I'll ingest into Hive as that allows me to pivot to the right tool for the kind of analysis that I need to do whether it be simple SQL via Hive, something more suited for Pig via HCatalog or Spark via SparkSQL. I'll often do my analysis on a Hortonworks Sandbox for small data like this.
For larger data and a more professional setting, I like to do prototyping/ad hoc investigation/etc in python with pyspark inside of jupyter. Generally that transitions either to Java or just plain python (depending on the degree to which it's difficult to transition).
Anyway, hope that helps! Happy to answer any other questions you might have too. :)
I think that our relationship with vacation has to change to one where we consider it a vital part of being a professional. When that attitude shifted for me, I became a pretty big fan of the unlimited vacation policy.
I figure that the worst case scenario, I'll get denied the vacation and I can choose if I want to move on or stay..no harm done.
http://hortonworks.com/blog/announcing-hdp-2-1-tech-preview-...
As it was, they just didn't act, treated the suffering as a badge and pretended they were in the foxhole with us. If they could handle it, why couldn't we? Why were we bitching so much? They were right there next to us! Needless to say, I don't work in those kinds of places anymore.
Second would be that there is something about your non-technical skill-set that is sending up red flags. What feedback did google UK give you after the rejection? Was it a bad fit technically or culturally?
I've been asked this before in post-interview negotiation, so evidently this is somewhat common practice. I always respond with, "I'll tell you that if you give me a salary breakdown of your engineering positions by experience level." They always back off at that point.
Anyway, you're absolutely 100% correct about problem sets. Good problem sets go a VERY long way to making a good textbook.
Anyway, nice paper..and thanks for making me think of category theory again. Maybe I'll pull out my old copy of "CT for the working mathematician" and give it (and haskell) another go.
Edit: I came across this: http://www.amazon.com/gp/product/0521422264/ref=pd_lpo_k2_dp...
Anyone gone through this book?
Edit: Sorry if I sound bitter, but I've been down the category theory route multiple times in the past, starting in graduate school (in Math) and I've always given up before I "got" the divine revelation that others have talked about.