https://medium.com/backchannel... This, as well, is a story about health care computer systems, which means it's 60% likely they're talking about MUMPS.
You mean they've come up with a reliable way to distinguish DDoS attacks from real traffic they were unprepared to handle in the wake of mass upheaval at Reddit? Color me impressed! Also, why have they chosen to waste this clearly magical talent on a startup?
The point is to take a bunch of individuals' knowledge and experience and combine them into something greater and consumable by the inexperienced. There's much lost in the translation, and the dangers of cargo-culting is well-known, but that's the purpose of digging into patterns.
I think GNOME has evolved on this point into a more-cohesive experience than KDE once had. GNOME 3 is where they said they were going to do that, but I moved far away from all that around that time. So, now, I suspect the article is probably right: GNOME project undertook a major philosophy shift, and now we're seeing the benefits of it. KDE kept doing what they were doing, and now they're here.
Do you think Hitler or Lenin weren't compassionate for those groups of people they were trying to help? If everyone hates you, nobody is going to follow you.
Herbert was exactly writing about hydraulic despotism, which is a common thing for varying definitions of "hydraulic". Oil is the big one right now, but water is showing all signs of being the next. As for revolution, anyone compassionate enough to be a good leader will have to face the choice that what path they are embarking upon will lead to death and destruction. Playing a race card is just shock value clickbait...
It's still a matter of scale. At scale, it's cheaper to ship water around than it is to collect it from the atmosphere. The scale of an offworld colony will be miniscule by comparison.
Using human pilots to "transition the flight from one automated task to another" is not self-flying, and the person above you linked the NG X-47B which is only capable of semi-autonomous flight.
Scale, and an explicit transaction. The carpool club's manager doesn't get a cut for facilitating the carpool club. Someone can't facilitate a dozen carpool clubs and take a percentage. That's why Uber is a taxi company and not a carpool club.
I'd much rather hire and keep good T2 and T3 support personnel. When T2 support has to deal with an unending cavalcade of "Oh, it wasn't plugged in, thanks for the help!", they are going to leave right quick.
It sounds like what you need for your situation is metrics, not eliminating T1 support. The point of tiered support is that the higher-level support people are supposed to be using their time that isn't answering the phone fixing the underlying problems that the support system is perhaps only mitigating. They can't do that while they are answering the phone. Surprisingly, people are only capable of concentrating on one thing at a time.
And I frankly don't give a shit if you feel like you're dumb because a T1 support answered your problem. The entire world does not exist to cater to your feelings. Maybe stop acting like an idiot would make you stop feeling like one. Or maybe stop trying to feel superior to T1 support whose job it is to help people, even blowhards like you.
I am an IT professional, and even I make simple mistakes sometimes. There is a reason rubber-duck debugging is a thing. Tier 1 is a rubber duck. Deal with it, you self-important asshole.
Most people younger than me know exactly shit about how their black monoliths (with brightly colored protective cases) actually work.
My team produces libraries that other teams use, and I keep having to tell my coworkers this: It is not our users' job to fix our documentation (though we can ask them to point out where our documentation is inadequate). Wikis are where documentation goes to die.
Good documentation starts with the author of the code.
Specifying what I want leaves it open for interpretation (by whom?). Or, worse, reveals what I am actually looking for (making a targeted coverup easy). Allowing police the ability to make judgement calls as to what to give when an FOIA request comes in, or outright deny a request that they can consider unreasonable, is no safety against police misconduct, which is the entire point this exists.
Yes.
Yes.
https://medium.com/backchannel... This, as well, is a story about health care computer systems, which means it's 60% likely they're talking about MUMPS.
Free Speech costs money. Reddit was no longer willing to pay the bill. That is the way of these things. Reddit won't be the last instance of this.
You mean they've come up with a reliable way to distinguish DDoS attacks from real traffic they were unprepared to handle in the wake of mass upheaval at Reddit? Color me impressed! Also, why have they chosen to waste this clearly magical talent on a startup?
The point is to take a bunch of individuals' knowledge and experience and combine them into something greater and consumable by the inexperienced. There's much lost in the translation, and the dangers of cargo-culting is well-known, but that's the purpose of digging into patterns.
I think GNOME has evolved on this point into a more-cohesive experience than KDE once had. GNOME 3 is where they said they were going to do that, but I moved far away from all that around that time. So, now, I suspect the article is probably right: GNOME project undertook a major philosophy shift, and now we're seeing the benefits of it. KDE kept doing what they were doing, and now they're here.
Do you think Hitler or Lenin weren't compassionate for those groups of people they were trying to help? If everyone hates you, nobody is going to follow you.
Herbert was exactly writing about hydraulic despotism, which is a common thing for varying definitions of "hydraulic". Oil is the big one right now, but water is showing all signs of being the next. As for revolution, anyone compassionate enough to be a good leader will have to face the choice that what path they are embarking upon will lead to death and destruction. Playing a race card is just shock value clickbait...
It's still a matter of scale. At scale, it's cheaper to ship water around than it is to collect it from the atmosphere. The scale of an offworld colony will be miniscule by comparison.
Using human pilots to "transition the flight from one automated task to another" is not self-flying, and the person above you linked the NG X-47B which is only capable of semi-autonomous flight.
The article says "semi-autonomous operation", not "fully autonomous".
Nah, by that time we'll have quantum teleporters.
If this software can bring down a rocket safely, could it bring down a plane safely? Could completely self-fly planes be in the wings?
Of course it's going to cost more than rail. Rail isn't dead in the US because it's expensive, it's dead because the US does not like it.
Scale, and an explicit transaction. The carpool club's manager doesn't get a cut for facilitating the carpool club. Someone can't facilitate a dozen carpool clubs and take a percentage. That's why Uber is a taxi company and not a carpool club.
But it is a "regulated market", the regulations of which Uber is explicitly not following.
I'd much rather hire and keep good T2 and T3 support personnel. When T2 support has to deal with an unending cavalcade of "Oh, it wasn't plugged in, thanks for the help!", they are going to leave right quick.
It sounds like what you need for your situation is metrics, not eliminating T1 support. The point of tiered support is that the higher-level support people are supposed to be using their time that isn't answering the phone fixing the underlying problems that the support system is perhaps only mitigating. They can't do that while they are answering the phone. Surprisingly, people are only capable of concentrating on one thing at a time.
And I frankly don't give a shit if you feel like you're dumb because a T1 support answered your problem. The entire world does not exist to cater to your feelings. Maybe stop acting like an idiot would make you stop feeling like one. Or maybe stop trying to feel superior to T1 support whose job it is to help people, even blowhards like you.
I am an IT professional, and even I make simple mistakes sometimes. There is a reason rubber-duck debugging is a thing. Tier 1 is a rubber duck. Deal with it, you self-important asshole.
Most people younger than me know exactly shit about how their black monoliths (with brightly colored protective cases) actually work.
http://modernperlbooks.com/boo...
It's funny that both sides are blaming the other for this. They're both fucking you.
bigint has been around for a while. Is that not what you want?
My team produces libraries that other teams use, and I keep having to tell my coworkers this: It is not our users' job to fix our documentation (though we can ask them to point out where our documentation is inadequate). Wikis are where documentation goes to die.
Good documentation starts with the author of the code.
Let's call it what it is: An aid when giving presentations, which are themselves also not documentation. There is no substitute for documentation.
Specifying what I want leaves it open for interpretation (by whom?). Or, worse, reveals what I am actually looking for (making a targeted coverup easy). Allowing police the ability to make judgement calls as to what to give when an FOIA request comes in, or outright deny a request that they can consider unreasonable, is no safety against police misconduct, which is the entire point this exists.