afs35mm

Scraping webpages is extremely useful and this would seem to combat this. It's also extremely useful by... oh yes... Google. And I'm sure they would find a way to whitelist their scrapers to index pages, but archive.org? Oh you're SOL.

What's really amazing about this whole thing is that it's more a guide as to not give bad (nit-pickey, overly critical, discouraging) code reviews, than how to give good ones. I think that alone should give us an idea about the state of code reviews in our current industry as a whole.

Here's one question that's always bugged me - What's stopping a malicious user from sending an HTTP request from any API client like Postman, or even Curl from the CL? Something like a post with: {transferTo: myAccountId, amount: 1000000000}?

Obviously in any nontrivial web app it would fail because of authentication issues, but if a server doesn't do ANY sort of security checking, that should work, no? Does that mean that the onus is on the server developer of mybank.com? And if so, what would stop the malicious request from working on any server developed before the existence of CORS?

Hi Don! Are you hiring engineers in NYC by chance for this new opportunity? :)

Agreed. As someone in the interview process once again, and being a bit more introspective this time, it's just really amazing how BS the entire whiteboard/share-scree "code this out for me" is. It seems to be a better indicator of how many of type X problems you've seen before, and employers seem to care more about if you know how to do something cold vs work through a problem to an adequate solution.

I was like this, to an extent, as well in my early twenties. What I realized was that I _didn't_ want to be like this, and like anything - it takes practice.

I consider myself smarter than the average Joe off the street, and you do too. Otherwise you wouldn't be reading HN :) So social cues, reading a crowd, and being engaging, it all takes practice. Yes, some people develop this naturally and don't need to consciously practice, but others don't. So just like programming, stop saying "No, I just don't get it", and instead reason why you don't and next time nail it.

"Don’t argue with me, don’t call me names, don’t tell me that I can’t stop you, don’t say I’m a racist pig, don’t threaten that you’ll sue me and take away my badge. Don’t scream at me that you pay my salary, and don’t even think of aggressively walking towards me."

Maybe it's the rebellious spirit still lingering, but there is only one hard cold fact in there. We DO pay their salary! The rest of the things I wouldn't say to my worst enemy. However I find it funny that when talking about law enforcement stating that specific fact turns into a threat...

I'm not entirely sure this is an accurate analogy. vendor prefixes solved a need. Why should we be developing to the lowest common denominator?

I think we should also watch out for link-bait SEO headlines such as "Why Webkit is the New IE6 (The Trap of Vendor Prefixes)"...

This seems like a complete paradigm shift from the Jobs-days of so closely holding and protecting their brand. Refusing to dilute it with Home Simpson and poorly drawn Golden Gate bridges...

...Or maybe they could just want to increase accessory sales.

Woz wrote BASIC from scratch and I'm having trouble with call and apply...

What platform did you use for deployment? When I dove into Node awhile back it seemed the most difficult part was finding a stable hosting solution...