Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Comment Re:It isn't "dying"... go make new stuff... (Score 1) 64

Dark is less predictable.

It's really not.

I thought for sure tom cruise's character would die. He didn't. Totally ruined the movie for me. It felt like such a waste of time.

lol sounds like "unpredictable" isn't what you are looking for.

Time for some introspection, see who you really are. Which isn't someone seeking unpredictability.

Comment Re: was this (Score 1) 39

yes, that's exactly the problem. The CODE was rolled out slowly; but that didn't matter because that path was not in use at the time. It began getting traffic hitting that bug all at once. That should not have happened

You don't understand the problem. You can't understand it from the report (I can't understand it from the report either), because the report doesn't explain it. Your mind tried to fill in the blanks, but it shouldn't have.

"Cut in." Not my fault slashdot has no edit function

It's your fault you didn't proofread in the preview stage. Blaming others is the root of all your problems.

Comment Death of the search engine (Score 1) 22

AI is the death of the search engine. It allows SEO leeches to build websites too easily, that appear informative and match all of Google's requirements to be voted up.

This is in particular a problem because the SEO websites built by AI are often wrong. At least with a handmade SEO website like Wirecutter, the information is mediocre, but real. With the new AI-SEO, reality has nothing to do with it.

Comment Re:Slack off in mission-critical ... (Score 1) 39

Kind of hilarious that they passive-aggressively blame "business requirements" for the problem:

" Regardless of the business need for near instantaneous consistency of the data globally (i.e. quota management settings are global), data replication needs to be propagated incrementally"

Comment Re: was this (Score 1) 39

This is pretty good for an external report.

No it's not lol.

The problem here is that the code path with the bug was cut it abruptly rather than gradually;

Your sentence doesn't make sense, it's not grammatical. Furthermore the problem was not abrupt: the code was merged in May, the outage was in June.

The report is bad.

Comment Re:was this (Score 2) 39

The article is written in a way to CYA of the people involved. It spreads the blame around without being too specific, so no one knows what was going on. For example, it talks about "the null pointer" but that's the only mention of it. At best that doesn't make sense gramatically.

They also talk about "This policy data contained unintended blank fields" but leave it at that. Why did it contain unintended blank fields? How did they get in there? It doesn't say. Is it a problem? Are they hand-writing this policy data?

Are they going to take measures to ensure that the "unintended blank fields" don't happen again? No, they are not; based on what is written in their document.

Was the report written by AI? It's probably too short and concise, but the grammar and disconnectedness makes it feel that way.

Slashdot Top Deals

The study of non-linear physics is like the study of non-elephant biology.

Working...