yunong

You're forgetting the vast network of much more energy-hungry computers your laptop is connected to.

I've used "waterproof" in-ear headphones for years and they work great. They're not cheap but they do work well. http://a.co/dItFKD3

I'm hugely disappointed that they discontinued the shuffle. It's the best music player for workouts period. No fussing with the bluetooth pairing, just plug in headphones, clip and go.

I personally use mine for swimming. You can buy waterproofed shuffles such as this one: http://a.co/f64p74y and they work extremely well for swimming. In fact when the shuffle was discontinued I immediately bought another one as backup to my trusty waterproof shuffle that I've used for 3 years.

Has the community discussed adding cryptographic signatures to npm packages? It's generally a good idea in any case, but this outage further highlights the security risks of a public registry where packages are not signed.

Netflix | Senior Software Engineer, Edge Device Services | Los Gatos, CA, Full-time | ONSITE | https://jobs.netflix.com/jobs/861260 Ping me directly on Twitter @yunongx DMs are open!

Netflix is shaping the future of global entertainment and reinventing how people watch television. Netflix applications are among the most successful and widely used in the world across a wide range of devices, including phones, tablets, game consoles, TVs, and desktop/laptops.

Our team is passionate about building and advancing core libraries, platforms, and services that are used across our device platforms. We design systems to be reliable at scale and flexible to product innovations. The projects you work on will not only help to continually improve how we deliver a better experience to our 100+ million members but also boost the productivity of over 200 engineers.

Challenges for 2017

In the coming year, our big goal is to migrate teams to the next-generation of the Netflix API, the system which processes and orchestrates all requests from devices to backend services. We’re building a high-scale platform that leverages Node.js and Docker containers to enable UI client teams to easily write and deploy their own services to the cloud. These services will be sitting in the middle of much of the action. Every request from every device from our 100+ million users will go through this new stack.

This is a highly cross-functional project with implications for many teams at Netflix. It will make our system more usable and developer friendly as well as more reliable, scalable, and performant as we continue to grow globally. There is no shortage of opportunities to shape the future of our product.

How you will help

Build, optimize and scale our Node.js platform and infrastructure Work on first-class integration of Node.js in the Netflix cloud ecosystem Ensure full observability into the state of Node.js services and real-time analytics Collaborate with engineers to identify common pain points, develop solutions, and evangelize best practices Provide technical leadership across UI engineering and help guide the overall engineering vision Improve developer productivity through better tools, processes and frameworks

Netflix | Senior Software Engineer, Edge Device Services | Los Gatos, CA, Full-time | ONSITE | https://jobs.netflix.com/jobs/861260

Ping me directly on twitter @yunongx DMs are open!

Netflix is shaping the future of global entertainment and reinventing how people watch television. Netflix applications are among the most successful and widely used in the world across a wide range of devices, including phones, tablets, game consoles, TVs, and desktop/laptops.

Our team is passionate about building and advancing core libraries, platforms, and services that are used across our device platforms. We design systems to be reliable at scale and flexible to product innovations. The projects you work on will not only help to continually improve how we deliver a better experience to our 100+ million members but also boost the productivity of over 200 engineers.

Challenges for 2017

In the coming year, our big goal is to migrate teams to the next-generation of the Netflix API, the system which processes and orchestrates all requests from devices to backend services. We’re building a high-scale platform that leverages Node.js and Docker containers to enable UI client teams to easily write and deploy their own services to the cloud. These services will be sitting in the middle of much of the action. Every request from every device from our 100+ million users will go through this new stack.

This is a highly cross-functional project with implications for many teams at Netflix. It will make our system more usable and developer friendly as well as more reliable, scalable, and performant as we continue to grow globally. There is no shortage of opportunities to shape the future of our product.

How you will help

Build, optimize and scale our Node.js platform and infrastructure Work on first-class integration of Node.js in the Netflix cloud ecosystem Ensure full observability into the state of Node.js services and real-time analytics Collaborate with engineers to identify common pain points, develop solutions, and evangelize best practices Provide technical leadership across UI engineering and help guide the overall engineering vision Improve developer productivity through better tools, processes and frameworks

What's the CAP tradeoffs of Cosmos? It's not clear to me looking at the SLA docs.

The one advantage with these robo advisors, or any broker for that matter, compared to a mutual fund is tax loss harvesting.

By having a separately managed account of ETFs or stocks, you can sell and exchange similar stocks when they lose value and harvest the tax losses to use at a later date.

Planned obsolescence...

"one of the best recruiting tools Amazon has is if people come interview on a nice day, and people are sitting outside having lunch from a food truck."

Have they been to Seattle during the months of November to June?

we talkin' bout practice?!!

I have a project that's shrinkwrapped. I check out a new copy of the project and run `npm install`. My co-worker does the exact same thing, his fails, yet mine successfully builds. An install of a shrink-wrapped should be deterinistic, i.e. either succeed or fail, but not both.

Even more important, npm doesn't reliably reproduce builds. Different runs of the same shrinkwrapped build could either fail or succeed -- which is odd given that builds should be deterministic. Additionally, shrinkwrap is also broken in the same way.

This is the first time I've heard of ied, a little competition could go a long way!

> Canola oil is one of the worst fats one could put in their body because it contains erucic acid that damages the heart.

Terrible piece, but this comment, without references, puts the cherry on top. This guy is about as bad as Food Babe.

I'm not making any judgements on Soylent, since I am not a nutritionist. However, anyone who's actually interested in any dietary supplement, including Soylent, should read about the industry's massive lobbying to prevent regulation by the FDA. Indeed, instead of the companies having to prove that their supplements are not harmful (via clinical studies and trials), it instead falls on the 20 something FDA staff to prove that they are harmful -- against the thousands of supplements available for sale in the United States [1].

[1] http://www.marketplace.org/2016/01/19/health-care/vitamins-a...

> You don't debug a unikernel, mostly; you just kill and replace it

Curious as to how you would drive to root cause the bugs that caused the crash in the first place? If you don't root cause, won't subsequent versions still retain the same bugs?

There are bugs that can only manifest themselves in production. Any system where we don't have the ability to debug and reproduce these classes of problems in prod is essentially a non-starter for folks looking to operate reliable software.

I went and looked in the Oxford English Dictionary and did not find your definition of magic there. http://www.oed.com/search?searchType=dictionary&q=magic&_sea...

Right, I agree with this. There's nothing magic about any of this -- ultimately it's all just software, hardware and physics.

To describe something as magic in a serious context is toxic. We're not sleight of hand performers, we're engineers. It's more helpful to state something like, "this library is complicated and the internals are beyond the scope of this post". A pointer to documentation and source code on libuv would be even better. In face, this series of articles on libuv are a great start for those who are interested: https://nikhilm.github.io/uvbook/introduction.html