The vast majority of those killed aren't lily-white innocent.
And that's why we have courts, and judges, and juries.
As long as guns exist anywhere, criminals will have guns too.
And yet countries with effective gun control laws have way fewer murders, as well as suicides with firearms (2/3 or all gun killings are suicides) than the US.
Why do you think the answer to everything is "cop should kill first, ask questions later?" There are places where cops killing people are far lower. Maybe you should take some lessons from them. A cop wearing body armour, armed with pepper spray and a taser, should not be reaching for their gun unless the other person also has a gun.
Do you think they'd be so trigger-happy if everyone wore the equivalent of google glass? Streaming everything all the time? It's eventually going to come to something like that, so cops that don't turn on their body cams aren't going to have any evidence to show things from their point of view.
You can catch outstanding warrants when you stop someone for cause. No need to waste billions of dollars (because you know it will be billions) on "AI body cams" that still won't do the job if they can be turned off, or "oops, the battery died".
How about a body cam with no off switch? Or a drone to follow them around all day and catch everything, because these killings happen in public? Or just post a bounty for the first camera to capture a police shooting? That should have a bit of a deterrent value.
Either that, or everyone is going to have to start wearing body cams.
Why work tech in Idaho? On of the poorest and least educated states in the union? Because in the land of the blind the one-eyed man is king.
Bullshit. In the land of the blind the one-eyed man is considered to be delusional. He's also pretty f*cked when it goes dark or in a cave or indoors.
Try this experiment the next time you have a power failure at night. Close your eyes. People's instinct is still to try to see in the dark, even when they can see that they can't see. Close your eyes, and you'll find it much easier to navigate. And that's without practice. Imagine a lifetime of practice, for everyone. The one-eyed man comes along and most of what he's saying about "seeing" sounds more like new-age crystal crap.
Absolutely correct. Hence all the disclaimers of liability. So now we have the whole industry running software on software stacks with no legal accountability. Takata would have loved to be able to make air bags with the same disclaimer of liability. Dow Corning would not have gone bankrupt if their silicone breast implants had no liability attached. Ford Pinto?
Software is a product. The vendor should be legally liable for defects. Sure, it would take longer, but there'd be less tendency to push it out quickly, and maybe fix it later.
My original UID was in the 43000 range, under my old name. But when I legally changed my name and sex, I couldn't just change the user name, so I had to get another account to prevent incongruity.
I never said that ANYONE always "gets it right." In fact, mistakes are the best teachers. You need to make a ton of mistakes to gain any level of proficiency. Problem is, most people make a mistake, google for the fix, and move on without gaining any insight as to WHY it's a mistake. Programming by google and rote is just wrong.
I resent that remark. I am NOT a "decent person." I have my faults, same as everyone else. The only difference might be that I'm very much aware of them. Same as I'm aware that as time goes on, I'm continually having to challenge my basic assumptions because I can't just ignore new evidence. People who don't do this seem much happier.
Considering that there was a history of programmers who had attempted the job, then started polishing their resumes to jump elsewhere when they realized they couldn't do it, putting a warning in for the idiots who, for example, insisted on putting #include windows.h in FreeBSD code is the prudent thing to do. Ditto for morons who are too stupid to keep track of resource allocation (and to design in a modicum of simplicity so that it's possible to keep track of it in the first place) so they end up having to use "smart" pointers.
f the company has ANY connection with your new state of residence (customers perhaps) you can argue for a change of venue. After all, they're doing business there, they're already bound by the laws there.:-)
When part of the requirements is to be as heavily optimized as possible in a resource-poor environment, you'll do things that people who haven;t been looking at the problem might think are wrong, even though they're just the most efficient way to do something. Problem is, most people will look at it and try to "fix" it. And in doing so, they fuck it up.
So I warn them. Same with "there be dragons here" for code that has desired side effects that aren't readily apparent but necessary for proper operation.
I'm not a lawyer, but the devil is in the details....
The will be a race to the courthouse in that case. If the employer files suit in Idaho first, the employee is screwed. If the employee challenges the Idaho non-compete provision in say, California, by filing in a California courthouse, the employer is screwed.
No - the employee can ask for a change of venue, since they now live in California - and California will likely grant it, especially if the company has ANY business presence in California (for example, do they ship to California? Have a distributor in California?).
The RAH isn't doing anything about it. Maybe because they don't know... so posting a link might just bring it to their attention. And if they aren't pursuing it because it's not that important to them, well, if they don't care, neither should you.
The karma cap is 50 points. Once you hit it, positive mods do nothing, but negative mods will still affect it. For example, if you're at the cap, get 10 + mods, then subsequently get 10 - mods, you're down to 40 points. If a few people with 15 mod points decide to mod-bomb you, you can quickly find yourself at zero.
Wrong. I wrote a multithreaded server that had zero memory leaks, never had to restart a thread to reclaim memory, and could run for years with no faults and no slowly chewing up extra ram. It took 2 years to get it perfect. Most places wouldn't give you 2 years to do that. They want "good enough".
Of course, a year after I left, someone modified the code and it started eating up ram. When they called me, I told them to put the code back the way it was, because even the source said "this may look wrong - but it's not. DO NOT TOUCH". They reverted to my old code, and everyone was happy.
Any smart teacher will slip in a mistake once in a while to see if anyone is paying attention. Then again, I'm not saying all, or even a majority, are smart.
Slashdot Mirror
The vast majority of those killed aren't lily-white innocent.
And that's why we have courts, and judges, and juries.
As long as guns exist anywhere, criminals will have guns too.
And yet countries with effective gun control laws have way fewer murders, as well as suicides with firearms (2/3 or all gun killings are suicides) than the US.
Why do you think the answer to everything is "cop should kill first, ask questions later?" There are places where cops killing people are far lower. Maybe you should take some lessons from them. A cop wearing body armour, armed with pepper spray and a taser, should not be reaching for their gun unless the other person also has a gun.
You have a sick culture. Fix it or die.
Do you think they'd be so trigger-happy if everyone wore the equivalent of google glass? Streaming everything all the time? It's eventually going to come to something like that, so cops that don't turn on their body cams aren't going to have any evidence to show things from their point of view.
Live streaming to "da cloud", with read/copy access by family and friends. Cops are going to turn everyone into glassholes.
They can't stop the offering of a bounty for those capturing police wrongdoing on video.
Use their "do you have something to hide?" right back at them.
"The company will be sued out of existence." Really? How many cities have been sued out of existence by cops killing people?
Want to reduce the number of killings? Rein in the cops. They kill more than 4x the number of civilians than total police killed by civilians..
You can catch outstanding warrants when you stop someone for cause. No need to waste billions of dollars (because you know it will be billions) on "AI body cams" that still won't do the job if they can be turned off, or "oops, the battery died".
How about a body cam with no off switch? Or a drone to follow them around all day and catch everything, because these killings happen in public? Or just post a bounty for the first camera to capture a police shooting? That should have a bit of a deterrent value.
Either that, or everyone is going to have to start wearing body cams.
"Sir, please step out of the vehicle. You have 20 seconds to comply."
That's 19 second more than some people get now ... or you're an Australian woman who calls the police to report a possible sexual assault, and they kill you - and of course their body cameras are off.
We already know what their excuse will be - "I felt threatened so I shot her."
It's the crappy apps you're installing, not Android itself. When you want something for free, did you really believe that it would be without cost?
Why work tech in Idaho? On of the poorest and least educated states in the union? Because in the land of the blind the one-eyed man is king.
Bullshit. In the land of the blind the one-eyed man is considered to be delusional. He's also pretty f*cked when it goes dark or in a cave or indoors.
Try this experiment the next time you have a power failure at night. Close your eyes. People's instinct is still to try to see in the dark, even when they can see that they can't see. Close your eyes, and you'll find it much easier to navigate. And that's without practice. Imagine a lifetime of practice, for everyone. The one-eyed man comes along and most of what he's saying about "seeing" sounds more like new-age crystal crap.
Because some people don't know how to do memory allocation properly without them, which means they have to use C++ and the STL. That's what. Duh!
Absolutely correct. Hence all the disclaimers of liability. So now we have the whole industry running software on software stacks with no legal accountability. Takata would have loved to be able to make air bags with the same disclaimer of liability. Dow Corning would not have gone bankrupt if their silicone breast implants had no liability attached. Ford Pinto?
Software is a product. The vendor should be legally liable for defects. Sure, it would take longer, but there'd be less tendency to push it out quickly, and maybe fix it later.
My original UID was in the 43000 range, under my old name. But when I legally changed my name and sex, I couldn't just change the user name, so I had to get another account to prevent incongruity.
I never said that ANYONE always "gets it right." In fact, mistakes are the best teachers. You need to make a ton of mistakes to gain any level of proficiency. Problem is, most people make a mistake, google for the fix, and move on without gaining any insight as to WHY it's a mistake. Programming by google and rote is just wrong.
I resent that remark. I am NOT a "decent person." I have my faults, same as everyone else. The only difference might be that I'm very much aware of them. Same as I'm aware that as time goes on, I'm continually having to challenge my basic assumptions because I can't just ignore new evidence. People who don't do this seem much happier.
Considering that there was a history of programmers who had attempted the job, then started polishing their resumes to jump elsewhere when they realized they couldn't do it, putting a warning in for the idiots who, for example, insisted on putting #include windows.h in FreeBSD code is the prudent thing to do. Ditto for morons who are too stupid to keep track of resource allocation (and to design in a modicum of simplicity so that it's possible to keep track of it in the first place) so they end up having to use "smart" pointers.
f the company has ANY connection with your new state of residence (customers perhaps) you can argue for a change of venue. After all, they're doing business there, they're already bound by the laws there. :-)
When part of the requirements is to be as heavily optimized as possible in a resource-poor environment, you'll do things that people who haven;t been looking at the problem might think are wrong, even though they're just the most efficient way to do something. Problem is, most people will look at it and try to "fix" it. And in doing so, they fuck it up.
So I warn them. Same with "there be dragons here" for code that has desired side effects that aren't readily apparent but necessary for proper operation.
I'm not a lawyer, but the devil is in the details....
The will be a race to the courthouse in that case. If the employer files suit in Idaho first, the employee is screwed. If the employee challenges the Idaho non-compete provision in say, California, by filing in a California courthouse, the employer is screwed.
No - the employee can ask for a change of venue, since they now live in California - and California will likely grant it, especially if the company has ANY business presence in California (for example, do they ship to California? Have a distributor in California?).
The karma cap is 50 points. Once you hit it, positive mods do nothing, but negative mods will still affect it. For example, if you're at the cap, get 10 + mods, then subsequently get 10 - mods, you're down to 40 points. If a few people with 15 mod points decide to mod-bomb you, you can quickly find yourself at zero.
Wrong. I wrote a multithreaded server that had zero memory leaks, never had to restart a thread to reclaim memory, and could run for years with no faults and no slowly chewing up extra ram. It took 2 years to get it perfect. Most places wouldn't give you 2 years to do that. They want "good enough".
Of course, a year after I left, someone modified the code and it started eating up ram. When they called me, I told them to put the code back the way it was, because even the source said "this may look wrong - but it's not. DO NOT TOUCH". They reverted to my old code, and everyone was happy.
Any smart teacher will slip in a mistake once in a while to see if anyone is paying attention. Then again, I'm not saying all, or even a majority, are smart.
It is. The civil eat ended personal slavery. Corporate slavery is still legal.
I don't think they drove the slaves to extinction by eating them. Corporations, on the other hand, will eat you alive.