Live data from Hacker News

Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

sportingnews.com

351–360 of 986 posts

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#351

Earlier quoted context omitted.

that’s totally unacceptable for live sports which people are able to bet on

I have bad news for you. This is how it works already for “live” sports

Yep. Having actually worked on this sort of stuff I can confirm.

Your ISP doesn't have enough bandwidth to the Internet (generally speaking) for all users to get their feed directly from a central location. And that central location doesn't have enough bandwidth to serve all users even if the ISP could. That said, the delay can be pretty small, e.g. the first user to hit the cache goes upstream, the others basically get the stream as it comes in to the cache. This doesn't make things worse, it makes them better.

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#352

Hopefully they fix it because they are hosting two Christmas NFL games this year and if you want to really piss people off you have buffering issues during NFL games lol.

Maybe this was a stress test for the NFL games?

I'd expect the NFL games to have a largely American audience, but today's boxing event attracted a global audience.

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#354

I'm an engineering manager at a Fortune 500 company. The dumbest engineer on our team left for Netflix. He got a pay raise too. Our engineers are fucking morons. And this guy was the dumbest of the bunch. If you think Netflix hires top tier talent, you don't know Netflix.

Curb your enthusiasm had a good segment of episodes that were a parody on Netflix and how they shifted hiring from merit to other criteria.

Curb did? What season/episodes?

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#355

I'm an engineering manager at a Fortune 500 company. The dumbest engineer on our team left for Netflix. He got a pay raise too. Our engineers are fucking morons. And this guy was the dumbest of the bunch. If you think Netflix hires top tier talent, you don't know Netflix.

> I'm an engineering manager at a Fortune 500 company. The dumbest engineer on our team left for Netflix. He got a pay raise too. Apparently he was smart enough to get away from the Fortune 500 company he worked at, reporting to yourself, and "got a pay raise too." > Our engineers are fucking morons. And this guy was the dumbest of the bunch. See above. > If you think Netflix hires top tier talent, you don't know Net…

> failed as a manager to elevate...

Managers aren't teachers. They can spend some time mentoring and teaching but there's a limit to that. I've worked with someone who could not write good code and no manager could change that.

Most people I've worked with aren't like that of course (there's really only one that stands out), so maybe you've just been lucky enough to avoid them.

I do find it unlikely that all of his engineers are morons, but on the other hand I haven't worked for a typical fortune 500 company - maybe that's where all the mediocre programmers end up.

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#356

I'm an engineering manager at a Fortune 500 company. The dumbest engineer on our team left for Netflix. He got a pay raise too. Our engineers are fucking morons. And this guy was the dumbest of the bunch. If you think Netflix hires top tier talent, you don't know Netflix.

I don't understand why nobody here believes you.

There's no reason to doubt what you say, probably people identify with the mistreated one. Why?

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#357
post #303

Earlier quoted context omitted.

Static files have been pretty much the standard streaming protocols for both VOD and live for the last 15 years ago. Before, it was Adobe Flash (RTMP). With the way that they are designed, you can even use a regular CDN.

You can push these files to all the edges before you release the content which will protect your origin. Livestream all your edge servers are grabbing content from the origin unless you have another tier of regional servers to alleviate load.

Sure but that’s why your edge servers do request collapsing. And there are full blown CDN companies that will write an enterprise contract with you that can do this stuff with ease. Akamai is like 25 years old now.

Scale has increased but the techniques were figured out 20 years ago. There is not much left to invent in this space at the current moment so screwing up more than once is a bit unacceptable.

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#358

Earlier quoted context omitted.

I don't spend much time streaming, but I got a glimpse of the Amazon Prime catalog yesterday, and was surprised at how many titles on the front page were movies I'd actually watch. Reminded me of Netflix a dozen years ago.

> Reminded me of Netflix a dozen years ago. It's been pretty rough the last few years. So many great films and series, not to mention kids programming, removed to make way for mediocre NeTfLiX oRiGiNaLs and Bollywood trash.

is this specifically in India? I never see bollywood stuff in the US but half the catalogue is dubbed/subbed korean dramas

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#359
post #43

Earlier quoted context omitted.

I think they have to refund the fees for a month to anyone who streamed this fight. That's the only thing that seems fair. It has been pretty useless. At the moment seems to be working only when running in non-live mode several minutes behind. So if there are 1 million trying to stream it, that means they would lose $15 million. So.. they might only give a partial refund. But people should push for an automatic refun…

Is it really that big a deal if you are watching a few minutes behind? I've watched ball games on streaming networks where I can also hear a local radio broadcast, and the stream is always delayed compared to the radio, sometimes by quite a lot. But you'd never know it if you were just watching the stream.

well it's live sports, watching live is the big deal. Also people are gambling on the outcomes so watching a few minutes behind is a big deal

Re: Netflix buffering issues: Boxing fans complain about Jake Paul vs. Mike Tyson

#360
post #145

I'm an engineering manager at a Fortune 500 company. The dumbest engineer on our team left for Netflix. He got a pay raise too. Our engineers are fucking morons. And this guy was the dumbest of the bunch. If you think Netflix hires top tier talent, you don't know Netflix.

I hope to never have a manager who is mentally stack ranking me and my coworkers in terms of perceived dumbness instead of in terms of any positive trait.

I'm not a manager and I don't stack rank people, but I am 100% capable of knowing when one of my co-workers or predecessors is a fucking moron.

The trick is to use my massive brain to root cause several significant outages, discover that most of them originate in code written by the same employee, and notice that said employee liked to write things like

    // @ts-nocheck
    // obligatory disabling of typescript: static typing is hard, so why bother with it?
    async function upsertWidget() {
      try {
        // await api.doSomeOtherThings({ ... })
        // 20 line block of commented-out useless code
        // pretend this went on much longer
        let result = await api.createWidget({ a, b, c })
        if (!result.ok) {
           result = await api.createWidget({ a, b }) // retries for days! except with different args, how fun
           if (!result.ok) {
             result = await api.updateWidget({ a, b, c }) // oh wait, this time we're updating
           }
        }
        // notice that api.updateWidget() can fail silently
        // also, the three function calls can each return different data, I sure am glad we disabled typescript
        return result
      } catch (error) {
        return error // I sure do love this pattern of returning errors and then not checking whether the result was an error or the intended object 
      }
    }

    function doSomething() {
      const widget = await upsertWidget()
    }
...except even worse, because instead of createWidget the name was something far less descriptive, the nesting was deeper and involved loops, there were random assignments that made no goddamn sense, and the API calls just went to an unnecessary microservice that was only called from here and which literally just passed the data through to a third party with minor changes. Those minor changes resulted in an internal API that was actually worse than the unmodified third party API.

I am so tired of these people. I am not a 10x rockstar engineer and not without flaws, but they are just so awful and draining, and they never seem to get caught in time to stop them ruining perfectly fine companies. Every try>catch>return is like an icy cat hand from the grave reaching up to knock my coffee off my desk.

Post reply on HN