bookface

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.

Wow, that is, appropriately, a tortured backronym.

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?

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.

These comments are disgusting. Why are you all trying to download the data? Why are many of you trying to distribute it?

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] */
    }

I was actually asked in an interview at Google in 2011 whether pre- or postincrement was faster in a snippet of code where the expression's value wasn't used. When I said that I was pretty confident that the compiler would produce the same assembly in both cases, the interviewer insisted that pre- was faster based on the same logic you mentioned.

To her credit, she didn't penalize me for disagreeing with her and I still got the offer.

I didn't originally see the connection between MSG and Chinese food as coming from a place of racism, but you might be right. I'm still not so sure though. If somebody said to you "I got food poisoning from a Chinese restaurant last night", would you say "That's racist! An Italian restaurant could have just as easily given you food poisoning."?

It's pointless to try to tell people what is and isn't offensive. Normally, I err on the side of thinking that if somebody is offended, they must have reason to be and I should be sensitive to that, but in this case I had no idea what racism the author was referring to.

I think the main difference between the two is the intent that's being implied. "Jewish Banker Syndrome" is implying something about me as a person. It's saying that, as a Jew, I'm more likely to be greedy and corrupt. "Chinese Restaurant Syndrome" isn't really blaming the Chinese for anything, it's just noting the correlation that was observed.

Maybe a better comparison would be "Jewish Bank Syndrome", which to me sounds a lot less harsh than "Jewish Banker Syndrome".

Sorry if I'm being insensitive, but how is Chinese Restaurant Syndrome "absurdly racist"? If people were having health problems as a consequence of eating corned beef, I would, as a Jew, have no problem with that condition being called "Jewish Deli Syndrome".

Agreed completely about how awful dynamic languages can be in this respect. I've found what helps a lot is consistent naming of parameters. For example, numberOfWidgets (an integer) versus widgets (a collection) or file (a file handle) versus path (a string).

If you think tech internships are bad, you should look at literally any other field.

If this involved Apple, the article's headline would be "Apple using forced student labor to build iPhone"

Sounds to me like you're being intentionally daft. It's pretty easy to see that the /uː/ sound is associated with "oo" way more commonly than "o".

What makes you believe that Twitter isn't doing that? If you're willing to speculate that Google is creating "shadow profiles", why not Twitter?

I was going to add a line at the end of my post saying that this was all, of course, my fault, but figured it went without saying. Lesson learned.

Wouldn't another solution to this be to have an object that would mimic the dom, performing reads immediately (or reading from its own cache of written attributes), but allowing explicit control over when writes get committed? It would then be easy to have atomic (wrt dom layout) functions.

This really screwed me over this time. My developer account expired a few weeks ago and I got worried because I still had the beta installed. I tried upgrading via iTunes, but it said I was up to date, and I assumed that meant that the phone had updated itself to the release version over the air automatically or that I'd forgotten that I already updated manually. And now that phone is bricked until I get back to my computer tomorrow.

s/titled/tilted/

Just print the box titled a few degrees :-)

I had this same experience. In 2010, I decided to buy the Captivate over the iPhone 4 after reading a bunch of reviews online. IIRC, I bought it right when it was released, which almost exactly coincided with the release of Froyo. After four or so months of putting up with a laggy interface, cheap (feeling) build quality, and no software updates in sight, I sold it and finally bought that iPhone 4, which I used for the next 3 years.

Recently, I decided to give Android another try and went with the Galaxy S4 when that came out. I was pleased with how far the OS had come since Eclair, but it still felt less responsive than even my 3-year-old iPhone. As for the build quality, that's my biggest regret in buying a Samsung product again. It's hard to beat the feel of an Apple device, but at least the Nexus 4 and HTC One are trying.

I still don't quite get what that means. If you click Python, why is Ruby highlighted, but not Django?

Good read. Thanks for that.

edit: HN discussion: https://news.ycombinator.com/item?id=6243627

Quick, someone call Kevin Rose!

Every "bad interview" story that graces the front page of HN has this common theme that the interviewee is an infallible genius who aces every question.

I know there's a bias here (better engineers are probably more likely to blog in the first place and most people would rather write about an experience where they're the "victor"), but it would be nice to read an article from someone acknowledging their own failure just once.

That sounds like an interesting story. Are there any more details that you're willing/at liberty to divulge?