←back to thread

492 points storf45 | 1 comments | | HN request time: 0.239s | source
Show context
_fat_santa ◴[] No.42157053[source]
When you step back and look at the situation, it's not hard to see why Netflix dropped the ball here. Here's now I see it (not affiliated with Netflix, pure speculation):

- Months ago, the "higher ups" at Netflix struck a deal to stream the fight on Netflix. The exec that signed the deal was probably over the moon because it would get Netflix into a brand new space and bring in large audience numbers. Along the way the individuals were probably told that Netflix doesn't do livestreaming but they ignored it and assumed their talented Engineers could pull it off.

- Once the deal was signed then it became the Engineer's problem. They now had to figure out how to shift their infrastructure to a whole new set of assumptions around live events that you don't really have to think about when streaming static content.

- Engineering probably did their absolute best to pull this off but they had two main disadvantages, first off they don't have any of the institutional knowledge about live streaming and they don't really know how to predict demand for something like this. In the end they probably beefed up livestreaming as much as they could but still didn't go far enough because again, no one there really knows how something like this will pan out.

- Evening started off fine but crap hit the fan later in the show as more people tuned in for the main card. Engineering probably did their best to mitigate this but again, since they don't have the institutional knowledge of live events, they were shooting in the dark hoping their fixes would stick.

Yes Netflix as a whole screwed this one up but I'm tempted to give them more grace than usual here. First off the deal that they struck was probably one they couldn't ignore and as for Engineering, I think those guys did the freaking best they could given their situation and lack of institutional knowledge. This is just a classic case of biting off more than one can chew, even if you're an SV heavyweight.

replies(8): >>42157067 #>>42157069 #>>42157146 #>>42157772 #>>42158104 #>>42158143 #>>42158185 #>>42158359 #
JumpCrisscross ◴[] No.42157772[source]
Livestreaming is a solved problem. This sounds like NIH [1]. (At the very least, hire them as a back-up.)

[1] https://en.wikipedia.org/wiki/Not_invented_here

replies(3): >>42157965 #>>42157973 #>>42160144 #
gregorygoc ◴[] No.42157965[source]
Saying live-streaming is a solved problem is like saying search is a solved problem.
replies(1): >>42158121 #
JumpCrisscross ◴[] No.42158121[source]
> Saying live-streaming is a solved problem is like saying search is a solved problem

It is. You can hire the people who have solved it to do it for you.

replies(1): >>42158338 #
talldayo ◴[] No.42158338[source]
> It is. You can hire the people who have solved it to do it for you.

"GPGPU compute is a solved problem if you buy Nvidia hardware" type comment

replies(2): >>42158458 #>>42158558 #
1. JumpCrisscross ◴[] No.42158458[source]
> "GPGPU compute is a solved problem if you buy Nvidia hardware" type comment

You're replacing the word hire with buy. That misconstrues the comment. If you need to do GPGPU compute and have never done it, you work with a team that has. (And if you want to build it in house, you scale to it.)