Re:Polly.js – Record, replay, and stub HTTP interactions
by lhorie on Thursday June 14, 2018 @11:41AM
(#17312472)
In my company (uber), it's actually not a whole lot of hoops. Basically a light legal review that checks the license, a code review to ensure there aren't references to closed source software and infrastructure, and approval from the team manager, who is usually already on board with the desire to open source.
Re:Polly.js – Record, replay, and stub HTTP interactions
by captain_perl on Wednesday June 13, 2018 @11:54PM
(#17309160)
I'm sure the first project took some time to setup, but Netflix has released dozens of projects since. So very low hoops.
Re:Polly.js – Record, replay, and stub HTTP interactions
by staticassertion on Wednesday June 13, 2018 @09:43PM
(#17308610)
Netflix seems to also have a really strong culture around this though, so I wouldn't be surprised if it's a lot less hoopy than you'd imagine.
Re:Polly.js – Record, replay, and stub HTTP interactions
by error54 on Wednesday June 13, 2018 @10:55PM
(#17308895)
Not to shamelessly plug but if you're in the Bay Area on June 28, we're giving a talk that's a bit about performance, a bit about Netflix engineering culture: https://jstalks2018.splashthat.com/.
Re:Polly.js – Record, replay, and stub HTTP interactions
by MaxLeiter on Wednesday June 13, 2018 @11:56PM
(#17309168)
If I’m a student can I sign up to attend?
Re:Polly.js – Record, replay, and stub HTTP interactions
by wesleytodd on Thursday June 14, 2018 @05:20PM
(#17315469)
Sure! (at least I don't see why you wouldn't be able to)
Re:Polly.js – Record, replay, and stub HTTP interactions
by koopa184 on Wednesday June 13, 2018 @11:39PM
(#17309101)
Exactly. They had engineers dedicated to creating an open source latency/fault tolerance library called Hystrix. Not too surprising they’re dedicating resources to other projects, too.
Especially at large corps like Netflix I'm sure there's a lot of hoops to jump through.