elq

I've had this plan for a bit over a year. No nights and weekends free. I don't even think there is free in network calling, but I'm not sure.

It's really not a good plan if you use a lot of minutes, but for people like me, it's great.

Yes. It is quite a deal. I pay .10 per minute after the small allocation is used up, but I've only use all 100 minutes twice in the last year I've had this plan.

If I were less lazy and needed more minutes, I'd setup grooveip (or something similar) with my google voice account.

Well, to be fair, it's officially a walmart plan - http://see.walmart.com/t-mobile/

The still have that plan - http://prepaid-phones.t-mobile.com/prepaid-plans it's just a bit hidden.

A perfectly acceptable answer to me is "I don't know, but this is what I would do to find out", go on to describe what books you'd refer to, what google searches, etc.

I'm under the impression that app engine is heavily used inside of google and its use is being evangelized.

This leads me to believe that it won't be killed

Netflix is, more or less, looking to minimize cost per hour. Network TV is looking to maximize advertizing share.

Netflix's cost per hour goes down as long as the content is available on the service.

The notion of what makes a flop is quite different in the netflix model vs normal TV.

You'd be surprised how overwhelmingly common and effective very simple methods like logistic regression and basic decision trees are for such systems.

Further, RBMs and other deep learning tools require a significantly more sophisticated mathematical background than algebra and a much broader understanding overall.

yes. it looks really barren to me -

http://i.imgur.com/W3enB7s.jpg

Perhaps the glassdoor data is poor. Perhaps people are choosing their total compensation rather than base salary.

Probably both.

I took a half dozen or so pictures of the sagrada familia, all have gps data in exif. Only one of my pictures contained the famous spirals, the rest were closeups of exterior detail. Only the picture of the spirals showed up in the query.

It's very impressive.

I'm pretty sure Netflix doesn't completely own the rights to HoC - MRC[1] does.

[1] http://en.wikipedia.org/wiki/Media_Rights_Capital

From my limited experience - I'm at best on the periphery of dealing with AWS support; I can characterize aws support as such -

Free tier - occasionally get answers. answers are generally vague. questions to forums. Paid tier - always get answers. answers are generally vague. you get a support portal. Top tier paid - always get answers. answers are generally vague. amazon employees will fly out to your site to give vague answers.

I know of at least one person that wrote a fairly significant chunk or erlang at netflix, but this was years ago just as we were moving into the cloud and now, as jedberg wrote, erlang would have a hard time working with the rest of the netflix stack.

I've used go at netflix before to hack up a quick load test, but recently the vast majority of my non java/c++ code at netflix has been python for writing glue to interact with our ops infrastructure and julia, which recently supplanted python/pandas/scikit, for my my research oriented stuff.

But overall go is a really neat "systems" level language.

my problem with this library (well, actually the internal version, I haven't looked much at the code in github) is that it was written from the perspective of an edge service - the netflix API. The needs of that system are quite different from the needs of middle-tier systems.

The API has a hell of a lot more surface area but is trivial in complexity compared other systems at netflix, and therefor this library has some huge gaps in design.

The two biggest issues IMHO are putting the throttling/fallback handling at the outermost edge of an external service rather than at the lowest level (i.e. the actual rpc) and a very C/errno like method of handling errors.

I'm also quite unhappy with the API. It require creating boilerplate classes to implement the commands. Yuck. A bit of magic with annotations or code gen would've been much cleaner and much less prone to errors caused by programmer fatigue or boredom.

I've had the "pleasure" of using the predecessor of this library at work.

The code written by someone who's just completed reading the GoF book feels remarkably similar...

Reed's point is, I assume, that Amazon is paying/will pay approximately $1B to license content for prime streaming, not ppv content.

Is the availability of prime streaming a factor in you choosing Amazon PPV vs, say, Apple?

Very well articulated. I recently had a series of frown filled meetings with my manager where the best I could come up with was essentially "you're giving solutions to implement rather than problems to solve"

I'm certain that book is well known to the development team :D

They left messages in the draft folder - no traffic analysis possible, at least from the messages themselves.

AFAIK Niantic is a internal google "startup", from what I've heard their real product/project (that I haven't seen) will be released soon-ish.

Think throughput...

Lots of cache memory and very fast buses to very large external disk arrays. An old mainframe trick was to use the previous generation hardware as the IO controller for the current generation...

No.

It looks like they've changed it. I added quora to my list of blocked domains in google immediately after noticing the blurred responses... I don't think I'll remove them.

As someone whose team used the beta of this product - No.

http://movies.netflix.com/ or http://dvd.netflix.com/

A question... what's the difference between free aws support for standard accounts and the highest paid level of support for aws?

Free aws support is evasive and opaque on http://status.aws.amazon.com/

When you pay for support you get evasion and opacity on the phone and in person.