TFA says "At least 10". That likely means something like "We saw 10 people do it, so it was AT LEAST that many...but we're missing 600 gallons of gas."
All your math shows is that since 60 gallons a car is improbable, we're probably looking at 20, 30, or more. If these were average cars filling up, probably 40 ish.
Yes, it is a crime. It meets the criteria of exceeding authorized access under the Computer Fraud and Abuse Act. Any reasonable person will understand that just because some bonehead set everybody's password to the same thing, that doesn't mean you have been given permission to access everyone's email. Should whoever caused all the passwords to be given out get a new job? Yeah, probably. That person isn't necessarily an admin, though. Sometimes admins are required to do things they know aren't a good idea.
They set ALL the passwords to the same thing, then told EVERYBODY the password, and that meets their definition of "working fine"? That meets my definition of fundamentally broken.
The best way to prevent ID theft is to stop pretending it's a real thing. Identity theft should be treated as not having anything to do with the consumer whose identity has been "stolen" at all. It's fraud between the criminal and the financial institution or lender. It should immediately end, as far as the consumer is concerned, with a statement that the consumer didn't open the account.
Aerodynamic craft like airplanes can handle that easily, and I see little reason the hyperloop (which will also likely be aerodynamic, for technical reason) would be much different.
No plane anywhere routinely handles anything like a sudden 1,400 mph headwind. Gradual acceleration to 1,400 mph, yeah. Back of the envelope, the train's hitting a 20 PSI wall.
Nah, I disagree, it's all about backups. If I were that developer, I'd curse the software a bit, be annoyed that I have to restore 3 months of my work, kick off the restore, go make a cup of coffee and the restore would be done when I get back. His rant reads like he actually has to start over an redo 3 months of work.
A repo on the same box saves you from accidental deletion. Backups save you from most possible mishaps, including user carelessness.
I'd put as number 1 on my list not to follow anything called a "Best Practice"...unless you know WHY it's a best practice and that the conditions under which it's actually the best thing to do correctly describe your company/environment.
Hardly. She worked for 2 companies. She likes one of their products more than the other. Of the things I'd judge her for (failing to turn Yahoo around and taking the job at all come to mind), her comment is irrelevant.
There are a lot of old cars on the road today because old cars are cheaper. The car I drive to work is 16 years old. Would it cost less to operate an electric vehicle? Sure it would. But I'd have to buy one, and the cost of buying an EV is around 3 times the cost of buying gas for the car I have now.
Personally, I like the idea of electric vehicles and I want one someday, but the notion that all fossil fuel vehicles will be gone in 8 years is really pretty ridiculous.
I don't see how you can blame Microsoft if $OTHER_COMPANY uses their software in a way Microsoft doesn't support. IMO, you should be blaming Hitachi here, not Microsoft. As far as critical and irreplaceable goes, anyone who builds critical, irreplaceable services on commodity, consumer grade software, has no one to blame but themselves. Put another way, they may have accepted the risk that this would happen when they stood the service up. The risk has now materialized.
Either way, I think that things like that are good gateways into appreciating others' work.
True, that. I just personally think if we're going to spin people up about something, coding is really not the thing we should bother with. Financial or scientific literacy would be a good place to start. Basic infosec would be nice (and a lot of people who do it are not coders). Just yesterday I had a dentist's office ask for a SSN. The fact that they did that tells me they aren't getting overwhelming numbers of people saying "WTF? No!"
We need a lot more of that, and we need it a lot more than we need someone else who can write buggy toy programs.
It absolutely takes more than one "coding" class for people to stop saying stupid shit. Plenty of well paid developers say stupid shit on a regular basis.
I'm actually gradually changing my opinion on things like this. People who think they're going to "learn to code" in an hour or a course, or people who think they're going to teach someone to code in a similar time are delusional. That's no more realistic than saying someone's going to "learn science" in an hour or a course. What they're going to do is get some exposure. They might inspire a few to learn more. Maybe 1 in 100+ will go on to a productive career in software development who otherwise wouldn't.
If THAT'S the goal, then great. For anyone who thinks you're going to teach the general population to code, hahahahahaha no.
Pressure at 30,000 feet is about 1/4 that of sea level, so while it's not "the vacuum of space", it's closer to vacuum than it is to ground level. Even taking in cabin pressurization, it's about 1/3 the pressure outside the cabin vs in.
A lot of people forget that restrictions like password masking came about because we DIDN'T used to do that, and guess what happened?
Some gimp in a hoody was standing behind people and just reading their passwords.
In ye olden days, literally that kind of thing was happening. At least, it happened when people didn't just sticky note their password to the monitor so they didn't have to remember it, and in case anybody else needed to use the system.
Personally, I really favor giving people an example of a real problem we're working on and asking how they'd solve it. We've made excellent hires of people who didn't come up with solutions, but had a solid approach to getting one. I don't think having someone show me they remember how to code a trivial algorithm I almost certainly will never want them to code is going to tell me anything about them I care to know.
If you have local administration rights then you take responsibility for being the admin, good and bad.
That simply doesn't work. Do this, and most likely before you've granted admin rights to two users, you'll have one who says "Ok, sure, I'll take responsibility for all that.", and subsequently never, ever acts as if they're responsible.
Then, when something bad happens because they've done something nutty with admin privs, IT finds out they have absolutely no teeth with which to enforce accountability.
...this article argues most of these tech companies "faced structural business issues too significant to be addressed through celebrity branding and artistic energy."
Do you know what doesn't address structural business issues? At all? Hiring a celebrity.
That's a roughly parallel statement to "the patient became more sick because they faced medical issues too significant to be addressed through Cheetos."
Slashdot Mirror
TFA says "At least 10". That likely means something like "We saw 10 people do it, so it was AT LEAST that many...but we're missing 600 gallons of gas."
All your math shows is that since 60 gallons a car is improbable, we're probably looking at 20, 30, or more. If these were average cars filling up, probably 40 ish.
That's exactly what percentages are for, so it's not disingenuous at all.
It's a start, though. It's a short step from that viewpoint to "no backdoor can be made secure" to "I guess we shouldn't do that."
Yes, it is a crime. It meets the criteria of exceeding authorized access under the Computer Fraud and Abuse Act. Any reasonable person will understand that just because some bonehead set everybody's password to the same thing, that doesn't mean you have been given permission to access everyone's email. Should whoever caused all the passwords to be given out get a new job? Yeah, probably. That person isn't necessarily an admin, though. Sometimes admins are required to do things they know aren't a good idea.
They set ALL the passwords to the same thing, then told EVERYBODY the password, and that meets their definition of "working fine"? That meets my definition of fundamentally broken.
Somewhere, someone just deleted a voluminous bit of text, replaced it with "Mostly harmless.", and went on listening to Vogon poetry.
The best way to prevent ID theft is to stop pretending it's a real thing. Identity theft should be treated as not having anything to do with the consumer whose identity has been "stolen" at all. It's fraud between the criminal and the financial institution or lender. It should immediately end, as far as the consumer is concerned, with a statement that the consumer didn't open the account.
I'm curious what technology we have that can actually drill into a magma chamber at all.
No plane anywhere routinely handles anything like a sudden 1,400 mph headwind. Gradual acceleration to 1,400 mph, yeah. Back of the envelope, the train's hitting a 20 PSI wall.
Counting files as a measure of productivity is terrible. Don't do that.
Nah, I disagree, it's all about backups. If I were that developer, I'd curse the software a bit, be annoyed that I have to restore 3 months of my work, kick off the restore, go make a cup of coffee and the restore would be done when I get back. His rant reads like he actually has to start over an redo 3 months of work.
A repo on the same box saves you from accidental deletion. Backups save you from most possible mishaps, including user carelessness.
I'd put as number 1 on my list not to follow anything called a "Best Practice"...unless you know WHY it's a best practice and that the conditions under which it's actually the best thing to do correctly describe your company/environment.
Hardly. She worked for 2 companies. She likes one of their products more than the other. Of the things I'd judge her for (failing to turn Yahoo around and taking the job at all come to mind), her comment is irrelevant.
I think you're talking about games.
I'm curious what your counter-argument is. Because no one can define a black-and-white line between the two, anything goes?
Here's my argument why the author is nuts.
There are a lot of old cars on the road today because old cars are cheaper. The car I drive to work is 16 years old. Would it cost less to operate an electric vehicle? Sure it would. But I'd have to buy one, and the cost of buying an EV is around 3 times the cost of buying gas for the car I have now.
Personally, I like the idea of electric vehicles and I want one someday, but the notion that all fossil fuel vehicles will be gone in 8 years is really pretty ridiculous.
I don't see how you can blame Microsoft if $OTHER_COMPANY uses their software in a way Microsoft doesn't support. IMO, you should be blaming Hitachi here, not Microsoft. As far as critical and irreplaceable goes, anyone who builds critical, irreplaceable services on commodity, consumer grade software, has no one to blame but themselves. Put another way, they may have accepted the risk that this would happen when they stood the service up. The risk has now materialized.
True, that. I just personally think if we're going to spin people up about something, coding is really not the thing we should bother with. Financial or scientific literacy would be a good place to start. Basic infosec would be nice (and a lot of people who do it are not coders). Just yesterday I had a dentist's office ask for a SSN. The fact that they did that tells me they aren't getting overwhelming numbers of people saying "WTF? No!"
We need a lot more of that, and we need it a lot more than we need someone else who can write buggy toy programs.
It absolutely takes more than one "coding" class for people to stop saying stupid shit. Plenty of well paid developers say stupid shit on a regular basis.
I'm actually gradually changing my opinion on things like this. People who think they're going to "learn to code" in an hour or a course, or people who think they're going to teach someone to code in a similar time are delusional. That's no more realistic than saying someone's going to "learn science" in an hour or a course. What they're going to do is get some exposure. They might inspire a few to learn more. Maybe 1 in 100+ will go on to a productive career in software development who otherwise wouldn't.
If THAT'S the goal, then great. For anyone who thinks you're going to teach the general population to code, hahahahahaha no.
This is fairly moronic and ignores decades of perfectly legal model aviation.
Pressure at 30,000 feet is about 1/4 that of sea level, so while it's not "the vacuum of space", it's closer to vacuum than it is to ground level. Even taking in cabin pressurization, it's about 1/3 the pressure outside the cabin vs in.
A lot of people forget that restrictions like password masking came about because we DIDN'T used to do that, and guess what happened?
Some gimp in a hoody was standing behind people and just reading their passwords.
In ye olden days, literally that kind of thing was happening. At least, it happened when people didn't just sticky note their password to the monitor so they didn't have to remember it, and in case anybody else needed to use the system.
Personally, I really favor giving people an example of a real problem we're working on and asking how they'd solve it. We've made excellent hires of people who didn't come up with solutions, but had a solid approach to getting one. I don't think having someone show me they remember how to code a trivial algorithm I almost certainly will never want them to code is going to tell me anything about them I care to know.
That simply doesn't work. Do this, and most likely before you've granted admin rights to two users, you'll have one who says "Ok, sure, I'll take responsibility for all that.", and subsequently never, ever acts as if they're responsible.
Then, when something bad happens because they've done something nutty with admin privs, IT finds out they have absolutely no teeth with which to enforce accountability.
Just think about this:
Do you know what doesn't address structural business issues? At all? Hiring a celebrity.
That's a roughly parallel statement to "the patient became more sick because they faced medical issues too significant to be addressed through Cheetos."