Live data from Hacker News

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

sportingnews.com

631–640 of 986 posts

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

#631
post #570

Earlier quoted context omitted.

I have this argument a lot in tech. We should always be doing (the thing we want to do) Somme examples that always get me in trouble (or at least big heated conversations) 1. Always be building: It does not matter if code was not changed, or there has been no PRs or whatever, build it. Something in your org or infra has likely changed. My argument is "I would rather have a build failure on software that is already re…

This is great, but what possible counterargument is there? We should prolong indefinitely a spooky ambiguity about whether the system works or not?

The counterargument is obvious for anyone who has been on call or otherwise responsible for system stability. It's very easy to become risk-averse in any realm.

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

#633
post #597

Earlier quoted context omitted.

I dunno, I've gone and done a "git blame" to find out who the fucking moron that wrote the code was, only to find out it was me three years ago. Sure, there's such a thing as stupid code, but without knowing the whole context under which a bit of code was produced, unless it's utterly moronic, (which is entirely possible, dailywtf has some shiners), it's hard to really judge it. Hindsight, as applied to code, is 2020…

I agree with the general sentiment ("one instance of bad code might have been me") but not the specific sentiment ("I could easily decide to catch and ignore errors through every bit of code I worked on without knowing why that was bad, and commit other, similar crimes against good taste in the same way"). The difference for me is that this is pervasive . Yes, sometimes I might write code with a bug in error handling…

Hey, that possum's name was Roger and I'm really sad that it died. I've been feeding it for weeks! There are definitely bad programmers out there who's code is only suitable for public shaming via the daily wtf.

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

#635
The arrogant Netflix! They always brag about how technologically superior they are, and they can't handle a simple technological challenge! I didn't have a buffering issue, I had an error page - for hours! Yet, they kept advertising the boxing match to me! What a joke! If you can't stream it, don't advertise it to save face with people like me who don't care about boxing!

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

#639

The arrogant Netflix! They always brag about how technologically superior they are, and they can't handle a simple technological challenge! I didn't have a buffering issue, I had an error page - for hours! Yet, they kept advertising the boxing match to me! What a joke! If you can't stream it, don't advertise it to save face with people like me who don't care about boxing!

I think you’re oversimplifying it. Live event streaming is very different from movie streaming. All those edge cache servers become kinda useless and you start hitting peering bottlenecks.

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

#640

Earlier quoted context omitted.

merriam-webster.com/dictionary/brevity

Writing APPL instead of Apple doesn’t get you any fewer keystrokes.

Ugh. Similar (huge) pet peeve about people who say "n.B." instead of "note".
Post reply on HN