Re: "he had clearly accidentally fired off every possible debug command at once"
Terminal text sent a packet at a time plus packet loss - which was the problem he was trying to debug.
43025 publicly visible posts • joined 16 Jun 2014
That's one that's always struck me as trying to duck the issue, pretending to ignore what it doesn't want to say but not really doing so.
In fact Dionysius seems to have been somewhat arbitrary in his designation. It's also a pity he was using Roman numerals, one reason why he couldn't incorporate a year zero which is apt to introduce either off-by one errors or make the results look odd when expressing C14 dates in both years BP [before Present] and BC. C14 dating, BTW, takes 1950 as its reference year.
For a start the one in Firefox wouldn't be much use when I'm using Palemoon (which is, BTW, set up to forget all its history when closed) and the one in Palemoon wouldn't be much use when I'm using Seamonkey and none of them on this laptop would be much use when I'm using one of the others. The separate keepassxc database can be synced as and when needed between systems.
My experience was somewhat the converse of that. Also in a telecoms company in Leeds. There was another building with some consultants working on something or other that, AFAIK, never happened but they were using Notes. According to those in our building who had dealings with them the emails coming from the Notes users were regularly infected.
This is all very well providing it doesn't conflict with a task that is more important and/or urgent, especially if the latter is something properly in your remit and the former isn't. The underlying problem usually arises from someone unable to distinguish from the importance of your proper work and their own self-importance.
It probably helps with having a professional reputation established before a change of marital status. My daughter's publications were in her married name which she kept on divorce whereas my cousin's daughter has reverted to her maiden name.
At least my daughter hasn't, at least as yet, remarried. Years ago one archaeologist, having become established in her married name (to another archaeologist) kept using it on remarriage. A journalist for the Irish Times who didn't see eye-to-eye with her on some matters referred to her in print on at least one occasion as "Mrs $CurrentMarriedName writing as $FormerMarriedName".
Compare this with the NHS system for recording a negative lateral flow test which doesn't actually require that the test was negative nor, indeed, taken. All that's required is the serial number of a test strip.
As regards personal ID I read in another place that the much vaunted Estonian electronic ID system has been reamed out to the extend of about quarter of a million ID photos.
If companies have to pay over the odds to get workers in their cosen locations they should have been asking themselves some hard questions long ago - and if they disn't their shareholders should have done. If you're fixing the pay by where the worker works rather than on their value to the business you're doing it wrong, no matter how much handwaving goes into explaining otherwise.
In the Couchbase world, a database is a "bucket," a schema is a "scope," a table is a "collection," a row is a "document," and the column is a "feed."
Oh, wonderful. Marathon/Informix went through three lots of vocabulary for the same concepts over a very few years about 4 decades ago. Will Couchbase also end up using the industry standard?
I keep getting pinged by SMS spam, allegedly by my GP, to go to a site to enter ethnicity data. A phone call to the GP confirms that this if kosher within a very restricted sense - it's the NHS that requires it and I suspect it's they rather than the GP who are doing the pinging. There are a lot of issues with it, not the least is that the URL goes to a site (of which I'd never heard) and includes a code that goes straight to a page which greets me by name.
Yes, that old, crusty, noob security hole. I've no idea how sparse the code space might be but it looks likely that a bit of experimentation with variations would pull up someone else's details - what details there might be I don't know because I haven't pursued beyond the greeting page for my own code let alone trying anyone else's.
I'd have hoped that these days the work experience child responsible - surely nobody more experienced would have done this - would have been quietly advised by an intern to have another go and do better, but no, it's released for use. Perhaps there's scope for a bit of investigative journalism here. Hint.
I used to carry a spare fan-belt back in the 70s although, AFAICR I only had to replace it once. OTOH I had a Sierra with an alleged 180k on the clock (alleged because the 60k when I bought it was suspiciously exact).
The thing is that failure modes now are different and more frequent. I've had two Subarus which had warning lights come on due to a switch failure in the gear selection. It may well have protected the engine in the event of some sort of fault but whatever that might have been the sensor failure was more frequent (for a small sample) than whatever it was protecting against.
On my current car I've had two wheel sensor failures in about 40,000 miles.
The modern failures might not be show-stoppers but not only are they likely to be costly to fix they don't leave one with confidence that they actually would protect against a show-stopper.
Perhaps the farming equipment manufacturers will learn the valuable lesson of making their equipment user repairable when farmers go out of business sue them for the consequent losses
FTFY
Rather than campaign directly for right to repair maybe they should campaign for legislation to ensure contract clauses weasling their way out of liability are not enforceable.
It's more likely that elsergiovolador's proposal would work by obliging vendors to fix things. And, of course, with BSD and Linux the users have the ability to access the source ode anyway. Of course there's always the possibility that the vendor might opt to provide entirely undocumented and incomprehensible source code.
"If it takes a kWh to do a job then it will, give or take, proportionally more time to do it with less Watts. You save nothing."
In fact, you'll be worse off. Depending on the quality of the insulation it loses heat whilst it's above room temperature. During the elongated time to boil it will be losing moreheat which will take more energy to replace.
You omit to mention nuclear power. For the whole of my long adult life we've been shoving far more fossil fuels up power station chimneys than need be, not because their were adequate available renewables to replace it for most of that time but because of opposition to nuclear put us far behind the curve, both in terms of supply and of technology development.