Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bento: Jupyter Notebooks at Meta

engineering.fb.com

Post reply on HN
Print view View original

131–134 of 134 posts

Re: Bento: Jupyter Notebooks at Meta

#131

Post by lclarkmichalek »

KaiserPro wrote: post #109
hnav wrote: post #77

Earlier quoted context omitted.

Doesn't sound like your type of company tbh, the flipside is that a "serious" company will often have broken bs too except now nobody is going to look at your contribution/fix.

Pfft. "your type of company" sod off. Meta is only like this because its got a massive advertising revenue stream. the sheer amount of engineering time wasted because we don't document stuff is astounding. For example, how many message queue systems do we have? how many half arsed message queues have been created because they didn't know about FOQS?

I think a fair few of them were created because they knew a bit too much about FOQS

Re: Bento: Jupyter Notebooks at Meta

#132

Post by fwip »

apwell23 wrote: post #127
3eb7988a1663 wrote: post #80

Earlier quoted context omitted.

Surely that has more to do with having a fleet of edge nodes that mirror content close to consumers? There are only so many ways to ship video bytes across the internet. Best way to save money is to move fewer bytes.

Yep its simply a money problem not some sort of tech genius by netflix. Max would be as good as netflix if they were willing to spend money on edge.

And, Netflix likely got cheaper deals than Max and others, because they were the first ones to ask for it at such a scale.

Re: Bento: Jupyter Notebooks at Meta

#133

Post by grantsucceeded »

ipsum2 wrote: post #61
grantsucceeded wrote: post #53

Earlier quoted context omitted.

Few companies experienced the explosive growth fb did, though many will claim to have done so. Hack made the existing codebase of php scale to insane levels while reaching escape velocity for the overall company to even attempt to transition away or shrink the php codebase, as i recall (i was an SRE, not a dev) zeus likewise.

You worked at FB, but you call yourself an SRE, not a PE? ;)

haha .. but i did work at google before fb.

my memory is hazy, but when i started i was called an sre. Then someone made up the term "app ops". then it was production engineering. then I called myself an SRE when i was interviewing to leave fb.

Oh, and i was called a DBA before being acquired by google.

Post reply on HN