Re: Cynicism? It's just another word for experience
"I'm not a cynic. I'm a realist."
A pint to you and a round for all who keep fighting, even knowing how futile is all can be.
61 posts • joined 9 Mar 2011
He missed the trick, then.
"That. Uh. That was totally supposed to happen. Totally. Planned test to destruction. Success!"
There's very good precedent. NASA did it with SLS.
That's my theory. Franchisees are supposed to do everything the "McDonald's Way", but enforcement is variable. Maybe the franchise's management thought they could skate on a demo version (not listening to any professional IT support they may have had).
Franchise operators are notorious for pushing the envelope in favor of profits in ways that company stores are never allowed to even think about.
Not as severe as "rm -rf", but I rebooted the production server thinking it was the test server.
I was at the test server console. But I was reusing a terminal window that I didn't realize was SSH'd to the prod server. First inkling I had a problem is when the test server didn't shut down its display. SSH closing was the second. The dismayed phone calls from the prod server's user community was the last.
Consultative Committee for Space Data Systems (CCSDS) Recommended Standard 702.1-B-1 IP Over CCSDS Space Links (https://public.ccsds.org/Pubs/702x1b1c1.pdf)
Supports IPv4 and IPv6 over existing uplink/downlink/crosslink communications protocols. Which SpaceX will have to use if they're not going to roll up their own ground facility network. Existing teleport facilities and COTS use CCSDS protocols.
Techies usually argue technical characteristics. Which is great, if you're arguing with fellow techies.
Beancounters, executives and politicians, though? None of those downsides affect any thing they care about, and you're not going to be able to make them care. And the argument they don't care about is the one they'll ignore, and get mad at the techie if they persist.
> Endpoint Protection Client. Yeah.
The endpoint that can't boot is the endpoint which can't be attacked or compromised. Mission Accomplished.
> This kind of situation is always hilarious - when you're not among the ones affected, that is.
“Tragedy is when I cut my finger. Comedy is when you fall into an open sewer and die.” -- Mel Brooks
People expect it to mean "Good, desirable, enjoyable User Experience."
None of those qualifiers are actually present. Only in the heads of the unenlightened and irrationally optimistic.
Bad User Experience? Still "User Experience".
"Hellish, Kafkaesque, want-to-slit-my-wrists User Experience?" Yup, still counts.
So yes, it's all well-designed User Experience. After all, if it puts you off from bothering Customer Service, the costs of Customer Service goes down. Mission Accomplished. The best Customer Service department is the one that costs absolutely nothing to operate because no one can figure out how to Experience it as a User. It's just more subtle than "Go Away And Stop Bothering Us" User Experience.
Working as designed.
Most likely, but specific testimony in this case wouldn't be about European networks, since FCC rulemaking and bandwidth allocation has nothing to do with Europe.
Assuming 5G uses the same spectrum world 'round, EUMETSAT's Meteosat family have downlink frequencies in the same place as NOAA's satellites (in the frequency band under discussion or immediately adjacent), used for the same reasons. So same problem as NOAA's rightfully complaining about.
Not just weather sats, though: all current satellite navigation systems use adjacent frequencies in this same frequency band, so if 5G gets deployed big expect GPS/GALILEO/GLONASS to get harder to use or slower to lock.
I remember discovering this as a kid doing my own little electrolysis experiment.
Wires for electrode, 9v battery, a couple of test tubes from my chemistry set, nice glass of water to be electrolyzed.
I couldn't find the box of baking soda (as recommended by the directions I was reading) to make the water conductive at 9v, but I figured table salt would work.
It did, brilliantly, but when I did the "glowing splint in the anode gas" test (ember should have flared into flame in the concentrated oxygen), it extinguished instantly and then I got a diluted whiff of chlorine gas. That was an eye-watering wakeup.
Now banks of batteries off-gassing elemental chlorine into an enclosed metal tube full of sailors... that would be really unpleasant.
Apple used to be famous for "we invented it first and best, even if someone invented it before us." They've exhibited that attitude less lately, probably due to the gradual erosion of the RDF since the ascension of Saint Steven of Cupertino.
Now we know where that arrogance went: 9 miles down the road, to Mountain View.
I'm just amazed ULA is allowing itself to be scapegoated* for schedule problems caused by Boeing's development issues.
*I mean, the last I looked ULA hasn't pushed back. Maybe they think "it'll all be worth it when they pay us, and we don't want SpaceX getting this business just because we objected out loud and made the customer look bad."
Cheers, Dabbsy, for all the wonderous 1980s memories.
Except for that one unfortunate year.
“It was terribly dangerous to let your thoughts wander when you were in any public place or within range of a telescreen. The smallest thing could give you away. A nervous tic, an unconscious look of anxiety, a habit of muttering to yourself—anything that carried with it the suggestion of abnormality, of having something to hide. In any case, to wear an improper expression on your face (to look incredulous when a victory was announced, for example) was itself a punishable offence. There was even a word for it in Newspeak: facecrime, it was called.”
If a hell-desk minion rotated into my perfectly stable work ticket queue and disrupted it by actually fixing a harmless luser issue... well, I know that Simon's and PFY's response would involve a roll of carpet and a dumpster, not impotent fuming.
"They changed the caption on all the software's acknowledgement buttons from the stolidly neutral "OK" to the inappropriately Tiggerish "GREAT!". It is not GREAT! when I am forced to admit to yet another rout. Nor is it GREAT! that I have completed the challenge to get a Bronze Mystery Box and special badge, or the other ridiculous trinkets now annoyingly added to the game."
I heard every single one of those "GREAT!"s in the voice of Thurl Ravenscroft, AKA Tony the Tiger.
Cool fact: Thurl Ravenscroft was from the US "Midlands": Norfolk, Nebraska.
United States Space Command already existed, from 1995 to 2002.
It was stood down because it was redundant. The mission itself was being accomplished by other commands and agencies, including US Strategic Command. Which inherited the space mission after USSPACE was disestablished.
This isn't even a proper half-measure to a "Space Force." This is just a feeble excuse to bump up the number of general officer billets.
My immediate conclusion is that Koreans are as bad as the French at making tea. As anyone in the civilised world knows, tea must be prepared using boiling water
As anyone in the civilized world knows, tea must be prepared using water approximately 25 degrees below boiling. One does not boil civilized tea. (I.e., green tea. Thus saith the civilizations that invented the stuff, including the Koreans.)
Only poseurs pretend wilted oxidized tea is better.
with a degree of gratitude to PFY. When you stare into the abyss long enough, the abyss reaches up and drags you into it. It really sounded like Simon had fallen into a fugue state, mentally trapped in the Support Maze. And PFY retrieved him, yanked him back into reality, with the best tool for the job.
'Course, Simon will also zap PFY when he's not expecting it (any more), because you don't get away with that kind of s**t without consequences.
An AV tool that can't accept the Meltdown patch is an AV tool which has been silently exploiting the Meltdown vulnerability for as long as it's been "drill[ing] deep into the kernel's internals in order to keep tabs on the system."
In other words, the AV software have been the exploiting malware we've all been worrying about, and have been for years.
"The feature won't behave perfectly in every case – but that, Bambas wrote, is because some pages are simply badly written. An ill-designed page that uses Google's Page-Hiding Snippet, for example, might load as blank for a few seconds, and if a developer is sufficiently inept to refer an API of an async tracking script from a sync script, a race condition is set up."
Never ascribe to stupidity that which can be adequately explained by greed. If malvertisers can hold content hostage behind tracking and advertising, don't you think they will? Prioritizing content on the browser-side conflicts with prioritizing monetization in the page design, and guess which wins? (Unless the browser user is sane and uses anti-malvertising technology like uBlock.)
He has been properly treacherous when opportunity arose. Promotion in the IT department is by assassination, like in all proper hierarchies.
Trusting PFY to tidy up BOFH's audit trail as well as his own can't possibly be the only plan. I really hope there's a devastatingly good Plan B, like past experience has shown. It's critical to my conception of The Man that he's thinking at least three moves ahead of every other player.
They're not Anti Open-Source.
They're Anti-competition. They're against Open Source when they think they'll be competing with it. They're completely in favor of it when they can use it to lower their internal costs or enhance their offerings. (Like as the underpinnings of their dedicated DBMS hardware.) The kind of thing that allows them to sell (and make money) while reducing the money they have to spend.
It's not about for-or-against Open Source. It's about for-or-against Oracle.
Even if FreeNAS whatever continues to be free-as-in-beer and more or less free-as-in-freedom (BSD license and all), the extra capability -- unneeded in most current use cases -- increases complexity and correspondingly decreases reliability. If the VM or Container capability is useless to you (because it's just a NAS, dammit), that's still X thousands of lines of code that can knock down the machine unless you brutally and thoroughly neuter it from the installed configuration.
Extra unneeded capability is not a benefit, no matter what iXSystem's roadmap says.
" And a person must be responsible for the consequences of her actions. There you go."
Alas, the Patent Office Corporation Person would be a Government Person, and therefore damn near immune to the consequence of its (official) actions. (Per sovereign immunity (https://en.wikipedia.org/wiki/Sovereign_immunity_in_the_United_States). If the PTO was acting in accordance with their official policy and direction, they're untouchable.
Must be nice to be a Corporate Government Person.
Biting the hand that feeds IT © 1998–2020