I don't take as much issue with this happening the other way around. It's a rare opportunity for the information asymmetry shoe to be on the other foot.

> I don't take as much issue with this happening the other way around.

That seems to imply that your opposition to a person not being spooked is not a moral one. Please tell us more about it.

A manager's anxieties over losing an employee are not equivalent to an employee's anxieties over losing their livelihood. So taking less issue with it is perfectly consistent with it being a moral position.

Depends on which employee it is. If you ever worked in economically depressed regions, you'd know what I'm talking about right away.

Wow, that is, appropriately, a tortured backronym.

It's a bad backronym, but it's not misleading.

I would argue that it is.

This is exactly why I started using iTerm. You and I even use the same key combination! It is so convenient that whenever I use others' machines, I try to bring down the visor and get frustrated when nothing happens.

Terminal.app can do this with the help of TotalTerminal. I used to use that, but switched over to iTerm for the greater degree of customization.

If anybody prefers a .mobi: http://www.filedropper.com/linkers-ianlancetaylor

(If anyone has a suggestion for a good place to upload that, let me know. I don't know whether the site I found on Google is sketchy.)

Seriously? What do you think it means to be a freshman? I am getting seriously tired of this attitude in the software community that you're only a legitimate programmer if you've been doing it since you were in diapers.

What's with the hashtag?

Maybe they are implying that "big data" is trendy at the moment? As far as I've seen on HN over the last year or so, lots of people are talking about what is and what is not big data.

Or the company who made the post uses #bigdata on twitter. In case you missed the "if you got 100% send us your resume" on the last page.

Not that I know of, but javascript does.

Can anybody explain some good use cases of implicit return? When I was doing a project in CoffeeScript last year (the only time I've used it), I found myself just using the return keyword explicitly because it was more readable, and I never ran into the issue the article talks about where it can be bad to accidentally return something from a function that should return null/undefined.

When would implicit return make code better? Maybe I'm answering my own question, but I can see them being more readable to somebody coming from a Haskell or LISP background than to somebody like me who has worked mostly in C, Java, and Python.

> I can see them being more readable to somebody coming from a Haskell or LISP background than to somebody like me who has worked mostly in C, Java, and Python

Ruby also has explicit returns. The idea is, every statement is an expression, and so has a return value. You don't need to figure out about whether a statement does or not, it just always does. One less thing to have to think about.

Other things, too, but that's one that that sticks out for me.

I would imagine some of the people wanting to download the data are snapchat users who are trying to find out if they (or people they know) have data is in the file. No clue on the distribute part.

Why should General Clapper have all the fun?

I like using it when I'm filling an array with an indeterminate number of elements. I've used this pattern a few times:

    foo foos[255];
    int ct = 0;

    if (<condition for adding first element>)
        foos[ct++] = foo1;

    if (<condition for adding second element>)
        foos[ct++] = foo2;

    ...

    for (int i = 0; i < ct; i++) {
        /* do something with foos[i] */
    }

IMHO, this is more concise and readable than separating the increment and assignment into two lines.