iamjochem

the following explains the 'why':

https://uxmovement.com/content/why-you-should-never-use-pure...

no idea to what extent, if at all, it is true. I can imagine there being a grain of truth in there but that implementing this correctly is much more difficult and nuanced than it might seem at first glance - most "digital designers"[1] probably don't get the budget/freedom to properly tackle accessibility in their commercial projects, I can also imagine that the majority of digital designers are 'young' and have close to 20/20 vision making it that much harder for them to truly put themselves in the shoes (eyes?) of people with lesser than perfect vision[2].

as someone with only a laymans' understanding of all this stuff I'm probably guilty of talking out of my **; I welcome someone with real graphic design credentials putting me straight :D

[1] "digital designer", a person working in/with visual design, who started employment, or was born, after the release of the first iPhone ;-) (alternatively someone working in the design industry who never had the privilege of buying a copy of "The Face" for the simple fact they we not born in 1985)

[2] a category I begrudgingly have to admit to being part of more and more ;-/

Callous

even if node-to-node communication in a cluster (hadoop or otherwise) itself is not secured, is it not reasonable to secure external access to the cluster itself (i.e. with a firewall)?

from an outsider perspective (I've never used/run hadoop) I cannot see much reason for exposing the cluster to the outside world - either a web-app acts as an intermediary or access can be provided via VPN/ssh-tunnel/etc

... just curious why a fully/publically exposed cluster would be a "requirement"? or does it come down to the fact that firewalling an AWS environment is as painful (if not more) than "kerberizing" a [hadoop] cluster? (I kind of assumed AWS has firewalling functionality that is fairly plug'n'play ... a quick search does really back that up though)

given that "Ruby Programmer" >= "PHP Programmer" (not necessarily true, but be honest PHP is considered pretty low on the food chain around here :)), and given that I have no CS or Math background, I whipped up an answer to this in about 5 mins:

    https://gist.github.com/4611869

Even taking into account the effect of 'nerves' in an interview setting, on the face of things the 10% mentioned seems a bit depressing.

I do wonder how relevant or helpful this particular exercise/test is with regard to accurately gauging a candidate's potential efficacy within [a|your] development team. My instinct suggests to me that being able to write an algorithm under scrutiny and/or pressure is actually a fairly low priority skill (in most development shops) when compared to the other many other skills that are required to be a successful senior developer.

I am overwhelmed and feeling somewhat inadequate, such is often the case when reading material posted on HN (I can't be the only one!).

truly a beautiful 'story', fantastic execution. bravo!