Re: How many leavers.
All the more reason to do the job professionally.
40471 publicly visible posts • joined 16 Jun 2014
I assume the idea is to milk the revenue from big installations while cutting the costs of dealing with those installations which have not yet had the chance to become big. To cut those costs they'll be releasing a lot of sales staff onto the job market with their lists of potential long term big virtualisation customers. Short-termism at its finest.
Let's conduct a thought experiment.
Your phone number has been changed. How do you go about changing contact details if they want to send an SMS to the old one to verify you?
Another:
Your phone has been stolen. How do you persuade them to block it's number for verification if they want to send an SMS to it to verify it's you calling?
"Surely it is up to individual users to update their details properly when they change numbers?"
In order to do that you have to be in control of the old number - which will be used to verify you - while already knowing the new one. This isn't necessarily going to happen. OTOH it is going to happen if someone has stolen your own phone and is transferring your number to theirs.
It's rather worse for nothing on two accounts. As I've written here before, if this is being relied on then whoever has your phone or your phone number is you, even if it's not you. That opens the door to a variety of mechanisms for fraud. Secondly, it's an indication of sloppy thinking around security which should start you wondering what other sloppy thinking is going on.
Pissing off a judge whilst doing so is not a good tactic. He's failed to obey a subpoena. The word translates to "under pain", i.e. fail and you get punished. If you read the judgement linked in the article she fids for the SEC but in the final paragraph she's pretty terse - in the vernacular it translates to "Get your shit together PDQ or else I'll get it together for you."
AIUI the issue of this investigation is that he bought shares and then announced his intention to buy the company. That meant that as the share price then rose it made the shares he'd previously bought more valuable or, to look at it another way, he'd bought them for less - and the sellers got less for them - than if he'd announced that was what he was going to do.
And he hasn't been sanctioned yet if at all. At this stage he's just being investigated.
It's a total ignorance of the principle behind the concepts of interface and implementation in computing. You keep the interface constant so that consumers of the service it provides, be they human or other software, are unaffected by the implementation behind it. When this basic principle is ignored, forgotten or maybe not even learned one has to wonder about the quality of the product as a whole.
I hate the whole "hamburger" menu idea period, but it's even worse on the desktop.
If you right click on the background of the tab bar you can select Menu bar. That puts things back where they should be. I haven't worked out if there's a way to get rid of the hamburger but at least it's redundant.
"But you could build that into the Firefox browser too"
That's where it started, Netscape Communicator. Two functions (more really, when you consider what TB does) via two interfaces to one executable. It included the original social media, IRC and Usenet. Then, in their infinite wisdom, or whatever it was, they split them. The original still lives on at https://www.seamonkey-project.org/ Unfortunately this scores even worse in terms of site non-recognition although el Reg comes down on the good guy's side of the line.
It would make a great deal of sense if they were put back together as the min product with, as you suggest, some of the more recent protocols such as Mastodon added in. Failing that I wish the Document Foundation would take TB or SM under its wing, maybe Firefox as well. It would surely promote it better and add the one function it doesn't have in the office suite line-up.
"- I cannot say this loudly enough, as I see it time and again, if the UAT is overrunning, DELAY YOUR GO-LIVE. Don't stop testing and go-live anyway hoping it will all be OK. It won't. Someone has to fix all the testing issues you're now going to spot for the first time in Production, and while they do, someone else else isn't getting paid, with major impacts on their company, staff, livelihoods, etc.
- Do not build immovable go-live dates into your programme, even if it's a response to missing a previous one. It's all very well to have a budget envelope and a hard stop to aim for, but what happens when you get there and it's not ready?"
It's quite clear that Horizon faile by disregarding these two points.
"For years, the fields of information science, information retrieval, and human-computer interaction have studied how people make use of search systems and have investigated ways to improve search interfaces. The integration of generative AI chat components is a major development that may profoundly change the way users interact with search systems."
The people being studied can only make use of what's there and can't make use of what's not there. If what's there doesn't offer decent filtering facilities which respect logical operators such research can't show people making use of them. If the research shows that what people are using tries and fails to double guess what they want then obviously it will point to using AI to make even worse guesses.
Raspberry Pi, which doesn't have an onboard battery clock, failed to set the time on boot and didn't trusti the repository to download a better client because the certificate start date was apparently in the future.
Having - cough - clocked the problem it was easy enough to set the time by hand, of course.
"Then there's a round of musical office chairs as the most motivated middle managers are whittled down for allowing the most talented employees to leave."
If senior management even recognised who was the most talented of their employees it would only be because they were the most expensive - assuming they were paid more than the rest wich isn't likely.