Not us! That other group did it!
"There is a sentiment within teams that 'someone had to pay for the UK's Post Office farce.'"
Um, so was it Fujitsu Ireland handling that project?
1059 publicly visible posts • joined 27 Oct 2009
It would seem some equivalent of the Heisenberg Uncertainty Principle would apply.
Somethings met and there was a 'blip'. You don't know how big they were (and are now) because the energy released would be partly determined by incidence angle. You don't know where they came from because you weren't measuring before the 'blip'. You can't measure where they then go because you still can't see them.
Sounds like all you'll get are frequency statistics - how many 'blips' per unit time per unit volume.
Hmm, might as well put up a STOP sign, wait for a bit, and count the holes.
Is this the article and research about 'revelation' 4 ?
* Google researchers deal a major blow to the theory AI is about to outsmart humans (at businessinsider.com)
* Pretraining Data Mixtures Enable Narrow Model Selection Capabilities in Transformer Models (at Arxiv)
My S8 is dying, but so have my hopes for a decent new phone. Thinking about it last night, replaceable batteries are gone, expandable memories are gone, earphone plugs are gone, etc. etc.
Are they really thinking I'll spend BUCKs just to get a new battery? Cuz that's all the 'good' they're offering _me_.
"I'm sorry Dave, I'm afraid I can't do that."
.
Arthur Conan Doyle, after writing so much apparently intelligent text, asserted fairies were real. Willingly fooled by children. I can't think of a better cautionary tale. Can you?
Google news recently re-did their home page. With 80 pixels of blank dead space on the left side. No reason for that. It never contains anything but dead space.
I look at that and wonder - which of several negative conclusions about Google am I supposed to imagine?
↑ This ↑
I've had glimpses of the "foundation stories" of several coworkers. They didn't grow up with *any* experience of 'normal'. They are still flailing with real life and sometimes we (the bystanders) catch the blows.
Pick a particularly failing coworker - ask them what number marriage they're in. Or, conversely, ask them how many step-parents they have.
Yah, but that's the weekly summary of commentary delights. The *original* comment cannot be found by Google. Hmm, perhaps they have retroactively instituted "history off" against ElReg?
Thought I'd drop in this oldey, from El Reg comments, from 2010 (but I can't Google the original article? Hey, ElReg?!?)
Arrests were made after an argument over stolen cake led to a fight among scientists studying sea birds on an Arctic island, in a muffin stuffing Baffin puffin boffin biffing cuffing.
Glad that their product evolution has been of service to you. My oldest order is dated 2000/12, for Linux and Windows products. I even bought a copy for my brother-in-law in 2009 to save him boots to DOS for some software he was reviving.
But what brings me here is: "The company started life serving developers with a desktop hypervisor so they could more easily test their work in multiple environments."
And so I last bought VMware in 2014, when with lack of support, dropped features, and inflation of prices they left this developer behind.
I understand that it's a cutthroat world out there. And the stock market demands more and more revenue/profit. But this developer customer thought I was supporting the company. Instead we were the throw-aways on the road to victory.
On the other side, looking at other people's code is finding out how 'standard' APIs really work. Sometimes, *if* they really work. Heck, *if* they are really utilized by anyone!
Programming blindly gets you pokes in the eye. I don't trust documentation to call out the pain points and gotchas in real world usage. Do you really think you can duplicate years worth of painfully discovered production oddities in your pitiful few 'tests'? I'll search through the code of successful mature projects to find "here be dragons" warnings. Long time ago reading jQuery source convinced me R.O.U.S. exist!
I'm not trying to copy their code, just avoid their gray hairs.
An AI helping at improving organization seems likely to fail, when such organization doesn't already exist.
My "to wish for" standard of meeting notes looks like this: [CSSWG] Minutes Telecon 2023-01-25 [css-nesting] [css-text] [css-pseudo] and like this: www-style@w3.org from January 2023 by date
But that requires people being organized when coming to a meeting and a commitment to actually making progress. If not already true in your environment, new 'magic' won't work.
It's hard to implement a magic bullet when your company is more into political paint ball tournaments.
"... would mean intentionally draining the batteries of users' devices without their consent."
This "negative testing", what would it prove? How would it be evaluated? I'm at a loss to understand.
Would it be thus: person was using our app daily for X hours a day, and now they use our app less, and less often? Do you *ever* *want* to turn off your users?
Apoptosis: a form of programmed cell death. (Sometimes hoped for in anti-cancer treatments)
Shouldn't they have started with a list of functional requirements from existing extensions, especially the most visible?
You can keep saying you've thought of everything, but you're not actually doing any checks against reality. You're just moistening your finger and sticking it up where you won't feel a breeze. Pull it out, your design stinks!
"dubbed Operation Safeguard"
With a new admin password BarnDoorClosedCorrectly?
There will be a delay while Microsoft tries to figure what number to use next. Even more people would work to avoid Windows 13. They might opt to name it Windows 12bis?
If Microsoft sales dept goes with 13, I'm betting it will be released in 2026. They have three different Friday the 13th's to announce on.
I too find it hard to believe that requiring 50000 people to actually care about honesty and competence within their company is a bad thing.
A few epics of woe from dozens of non-C-level execs unfairly penalized by shenanigans at the top will ensure the SEC has a steady back-channel of information from inside in the future.
Where's the status page that says NoScript will work on V3? How about AdBlockPlus? How about the other extensions we need to defend ourselves?
It would have been so simple and much more useful for him to have said "We don't know what's coming up soon with the economy and so we need to step lightly for awhile."
But instead of saying "we don't understand" he says "you don't understand". Click-head.
There are multiple places that track this issue. Retraction Watch is one such example and here's an example that specifically calls out image problems. "An institutional investigation has concluded that Figs. 1b and 2e are unreliable and that much of the additional data in the paper cannot be reliably verified from records."
Whether data problems result from sloppiness, time pressure, or simple dishonesty, research and academia *must* better their vigilance.
I could wish our industry had capable appraisers also.
How strange. ElReg has accidentally stuffed the same article twice into the front page, using different URLs.
Retbleed fix slugs Linux VM performance by up to 70 percent
Retbleed fix slugs Linux VM performance by up to 70 percent
I *was* seeing double
Yes, someone's very confused here. Launches 'til now were to ~550 km region. SpaceX had previous approval for launches to an additional 1100-1300 km region, but had not done any yet (?). The new request was to allow the additional (?) satellites instead (?) to target (oops) the original ~550 km range. But (IANAE) I am not an enthusiast, so this may deviate from the ring of truth.
I'm amazed no one has mentioned "Indian Love Call". It figured rather prominently in a movie about failing heads...
Proprietary this, patent that, all high tech stuff to be sure.
Yet the resemblance for me is to the art world. People ooo and ahh about some new artist and their 'vision'. Suddenly large amounts of money flow to the recent unknown (and gallery owners).
Later, sometimes much later, some slob pipes up with questions: doesn't this piece look derivative from X Van Y's charcoal sketches of 16xx? And that piece looks copied from something by a little-known photographer. And then things blow up.
When 'experts' tell you the newly flung is bling, how are the lawyers supposed to object? Until the subterfuge is revealed, it's all about reputation (and insider placement).
This is a very confusing or incomplete description. If I understand correctly, this is not just the Object prototype pollution problem, which has been known for ever. Saying it is an object prototype pollution problem is misleading.
Rather (reading between the lines) it is miscommunication/misdirection, stuffing admittedly bad information into Object that is then looked at by other software. That software is not verifying that the information came from the expected place, package.json say, but picking it up from the Object prototype.
Oh dear, does reading JSON not use a clean Object.create(null)
object?
Anyway, the helpful notes in the NPM package situation mentioned would be - here are all the parameters you must fill in in package.json or else some software may be pulling answers out of a hat.