Azkar

But Facebook doesn't get any cut of a sponsored post. (meaning a company paid an individual to write a post)

If the service won't be responsible for incorrectly validating the ID, what's the point? Seems like you'd be paying for nothing, really.

Why do you need to disclose your salary? It's just as easy to say "I won't accept the position for anything less than $X"

Well now when someone removes left pad from npm your whole terminal can break.

I'm happy with how the issue was addressed. No one can expect perfection from a complicated piece of software such as this. I was glad to have received the email and find the blog post with a thorough list of FAQs.

I'm glad to see proper credit given to Jordan for finding the flaw. Maybe I'm a cynic, but I'm glad that this was an open process and not a one line blog post about a critical security update. Keep up the great work.

At sea-tac the other day, I watched them completely close a screening line so that they could perform a shift change. Really? You have to shut down the ENTIRE LINE in order to change out a few people? These people need lessons in efficiency.

If time were money to them, this crap wouldn't happen.

How come the FBI isn't afraid these guys are going to sell the same exploit to foreign governments which will use them to break into US government phones?

That's kind of the spirit of this question. Things like dates are really hard, but because we use them every day they seem 'easy'

It's not that it's difficult to understand, it's about comparing apples to apples.

I don't understand why he talks about a javascript problem being solved, then goes on to show us examples in coffee script.

Exactly. The slope begins with a phone released in 2013, but it doesn't end, ever - unless we can set the precedent now that Apple doesn't have to do this kind of thing.

And most places already have a system that works and no incentive to upgrade their tech from 15 years ago.

That just makes it easier to skip reading.

I feel like there is a big difference between "right" and practical. The world isn't black and white, the authors clearly have had problems when the comment was removed, so it's probably better to just keep it there.

I personally hate when commented out code are checked in to source, but put in a situation where the "right" thing increases the likelihood human error, I'll pick the "wrong" way every time.

This really isn't a problem that's unique to the SPD. I've worked for several corporations that are resistant to change for whatever reason and it is extremely frustrating. The engineers end up being told to do X, instead of being asked to solve problems.

It really baffles me that a company will still treat customers like this. Amazon has become bigger than wal-mart because they focus on the customer, maybe other companies will catch on and follow suit. Customers are not stupid, they understand that e-books are a lot cheaper to produce/distribute than a physical book, and they should be priced accordingly.

I wonder how long we're going to see these inflated e-book prices before the publishers drop the prices to what they previously were. If this sales trend continues they'd be dumb to not drop the prices of e-books.

So you're proposing that amazon didn't bother to check that the provider was real before listing it on their website? I just don't see amazon blindly adding service providers to their website without any sort of vetting process.

There were definitely "older" devs that wanted to do those things, but they didn't have the 15 years of tenure to be able to make those decisions. I should rephrase to say that if your devs don't want to learn new things, they probably aren't in the right field.

I worked at an organization that didn't let us use stored procedures or OOP because the older devs couldn't understand them (it was a Navy contractor, so there were guys that had been there 15+ years).

If you decide not to use a technology because the developers can't or are unwilling to learn them, you've got bigger problems than technology choices.

The Poe's law is strong in this one. It had me going.

I agree. $30K/yr is a lot of money, but it shouldn't put anyone on the street. Sure, it might not allow you to live a glamorous lifestyle in they valley, but you have the freedom to move somewhere a lot cheaper to live if you're a single developer pulling $70K/yr from an iphone app. If you don't want to make that compromise, then you should be looking for a second source of income, or start living within your means.

Taubes touches on it in this article a bit: http://garytaubes.com/2011/11/catching-up-on-lost-time-%E2%8...

It's not a scientific study, but it addresses the obese people not eating significantly too much.