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

The August 17 outage

github.blog

Post reply on HN
Print view View original

381–390 of 804 posts

Re: The August 17 outage

#381

Post by tverbeure »

dadadad100 wrote: post #220
Aachen wrote: post #93

Earlier quoted context omitted.

I always add some jitter but never actually had a problem where it would have been relevant. Recently I added it to a project where others also see it (not just a hobby thingy but something at work) and I was wondering if it would look silly, like premature optimisation. I looked on Wikipedia for how established the practice is and it barely gets a sentence... with no reference. Do you know of a documented instance w…

It’s a fundamental property of Ethernet[1]. Does that count? [1] https://en.wikipedia.org/wiki/Exponential_backoff#Example

It’s the first thing that came to mind!

Re: The August 17 outage

#382

Post by hirvi74 »

mey wrote: post #308
noir_lord wrote: post #289

Earlier quoted context omitted.

That was the final straw that stopped me using it. I didn’t/don’t want the AI, I didn’t like the telemetry but it could be turned off but the cavalier disregard to just yeeting shit into a tool used by that many people no thanks.

What do you use now and what is your primary use case?

I always advocate for the "boomer" editors when possible. It doesn't matter which one you choose. People can say what they want about them, but very little software survives almost 60 years. I sure as Hell hope VS Code doesn't.

Re: The August 17 outage

#383

Post by katbyte »

mey wrote: post #308
noir_lord wrote: post #289

Earlier quoted context omitted.

That was the final straw that stopped me using it. I didn’t/don’t want the AI, I didn’t like the telemetry but it could be turned off but the cavalier disregard to just yeeting shit into a tool used by that many people no thanks.

What do you use now and what is your primary use case?

I use jetbrains editors, but mostly goland which might be more stable then others

I recently tried zed but it ddos’d my nas over an smb share lol

Re: The August 17 outage

#384

Post by hirvi74 »

TomBombadildoze wrote: post #250
ACCount37 wrote: post #208

Earlier quoted context omitted.

"You can't seriously tell me that the unhappy leg of the code path has no test coverage." Sometimes I forget how ignorant HN can be of real world software development and the bar of corporate code quality, and then bangers like this remind me of it.

[flagged]

At least they aren't creating new problems at scale either.

Re: The August 17 outage

#385

Post by antiframe »

mikert89 wrote: post #351
jeremyjh wrote: post #292

Earlier quoted context omitted.

Tell me about the time that an app at Meta grew at 10% a year for a decade and then began doubling every few months.

its probably happened on half the core teams, idk what you want me to say, it sounds like you dont have alot of experience

Don't dodge the question and attack the asker, that's rude.

Re: The August 17 outage

#386

Post by ethagnawl »

aesthetics1 wrote: post #189

> Since April, monthly commits have grown from 1.4 billion to 2.9 billion Bonkers. You can tell the entire industry is in a "productivity panic" and here's more proof. There's a velocity zealot crying tears of joy somewhere.

Bonkers is right.

Where in those ~12 billion commits is the software, products and "innovations" which are supposed to be making our lives better? Software and apps in particular are getting worse, normies hate AI more than ever because they're even less likely to get their desired outcome when calling their doctor or trying to get their online order refunded when chatting with a cutely named chatbot, wages for (most) knowledge work are being driven through the floor, artists are being squeezed more than ever, etc., etc. That's to say nothing of the existential threats to the economy, environment and critical thinking which are growing daily. I really think we've lost the plot, folks.

Re: The August 17 outage

#387

Post by bearjaws »

Centralized source code hosting is going to end up looking like the three credit bureaus in terms of security. It's only a matter of time before the first big hack, when everyone shrugs and says, "Oh well, everyone's source code leaked lol too big to fail."

Re: The August 17 outage

#388

Post by Dylan16807 »

bbarn wrote: post #212
ACCount37 wrote: post #208

Earlier quoted context omitted.

"You can't seriously tell me that the unhappy leg of the code path has no test coverage." Sometimes I forget how ignorant HN can be of real world software development and the bar of corporate code quality, and then bangers like this remind me of it.

Exactly this. I've seen production level trading systems grind to a halt over a simple bug and no matter what tests you have in place, it happens.

> Exactly this.

It seems to me like you're saying nearly the opposite of them. You're saying "no matter what tests you have in place, it happens", while they're suggesting low standards and few tests.

Re: The August 17 outage

#389

Post by psunavy03 »

hirvi74 wrote: post #382
mey wrote: post #308

Earlier quoted context omitted.

What do you use now and what is your primary use case?

I always advocate for the "boomer" editors when possible. It doesn't matter which one you choose. People can say what they want about them, but very little software survives almost 60 years. I sure as Hell hope VS Code doesn't.

At some point, esoteric UIs may have been needed in the 70s, but that ship has long sailed. I don't need to give myself carpal tunnel syndrome trying to quit vim. If anything, a lot of that is also a problem that continues to plague software to this day: devs who go "well if it works for me, it's good enough for anybody, and if you don't like it, you must not be a Real Developer!"

Re: The August 17 outage

#390

Post by Dylan16807 »

grim_io wrote: post #205
jdm2212 wrote: post #200

Earlier quoted context omitted.

Exponential backoff is the wrong answer in a highly available system in the typical case where (a) failure is expected and (b) you have nodes you are supposed to fail over to.

Why? You can retry, but there is nothing wrong with increasingly waiting slightly longer if we fail many times.

"exponential" and "slightly longer" are very different backoff patterns.
Post reply on HN