Last place I worked simply did a 0 wipe. If a drive was too dead to wipe, we just used an electromagnet over it. Dunno what it's real purpose was, but basically, plug it in, hit the button, get a powerful, undulating, pulsating, magnetic field. Pass it over the drive a few times and toss it into the box.
Currently, we just toss the drives into boxes marked "...eventually".
For storage in devices like printers, etc., where there might be a large amount of storage to facilitate print queuing, etc., I can see how something like this coul be useful. For instance, one of the options on these devices is to self-wipe on power cycle. For companies worried about security, this might be worthwhile in their printers, where the storage itself might be for the purpose of convenience, but they would rather be safe than sorry, and data destruction is of ultimately no consequence because the source for that data is found elsewhere. That way, they can dispose of their printers in relative peace of mind, because if someone powers on the printer to see what it has on it, then poof, no more data. Or even do the "unknown host" thing, and then all you have to do is make it clear to IT that you don't want the valid host (the printer) to survive the disposal process, so if they want to play with some baseball bats in a field to the point of smashing the drive controller... then that's fine with corporate.
Wrong. When someone sends you a fax (instead of just riding it over on a dinosaur), and your fax sends the confirmation that it received it, but there's no printed copy yet (either because you need someone with access to that line to log in to view/print it, or because it was in the queue), you're legally screwed if you wipe out that data.
All you need is a 3 column database for fuck's sake. Zip code. Tax rate. Effective date.
Wrong. You also need to know this for every category of merchandise, and you need to know which categories each item of your merchandise is in in every state and locality. Furthermore, zip code and tax authority boundaries often do not coincide. There are likely other complications as well.
All Amazon needs to do is put forth a basic effort and let the customer handle any discrepancies on their (get this!) tax forms. If someone in California is mad that they were charged tax on their 1000 pack of slim jims, then they can claim it on their tax forms. If Amazon wants to please these customers, they can add it in.
And remember son, zip codes have NINE digits, not 5. They're more than good enough to appease any tax collector.
So there could be no good jobs if they charged $10 for the cable? Somehow amazon can sell cables at a fair price, I bet they have some good jobs to offer as well.
Seems like Sen. Durbin didn't like the way Amazon treated his state. Now we'lll all get to pay tax on everything. Thanks a lot Amazon.
Not just taxes, but higher prices. Setting up these tax tables is not an easy task. Some states tax specific items (such as clothing) while others don't. Some counties - and even some cities - add a % to the 'local' sales tax. Some states tax delivery fees. I could go on and on...
These costs will be passed on to the consumers. And let's not forget that the sellers will be required to supply some sort of tax information to the consumers just in case the consumer needs to prove they paid the sales tax on their purchases (or didn't pay taxes because they are tax exempt in their own state). The states will need to perform long-distance sales tax audits on the sellers (and sales tax audits are a time consuming endeavor for the sellers).
Horse shit. Setting up the tax tables is trivial. It's a lot of work to input the data and maintain it every year, but that's what data entry monkeys are for.
All you need is a 3 column database for fuck's sake. Zip code. Tax rate. Effective date. (You need the date for historical shit since you'll want to process returns/refunds, generate old sales slips, etc.) This database already exists from various vendors. They'll even keep it up to date for you for a moderate fee. If Amazon were to buy an existing product, it would result in about a $0.0000001 cent increase per item. If Amazon was feeling frugal, they would just offer it up as a problem on their own Mechanical Turk service and let India handle it.
It's not a new tax. It's not a tax increase. It's a new attempt at the enforcement of an existing rule. I predict that we'll have just as much compliance under the new enforcement as we do under the current honor system. As long as "zero" is a valid input for taxes owed on any form, people will put it in.
You are mistaken, a new federal law could make enforcement trivial. The feds could simply say you must collect the tax and pay it to the state, or the feds could allow a state to sue a company even if the company had no physical presence in the state.
I think the Supreme Court would have something to say about such a law. Or at least I fucking hope it would.
The fact that you think this is a viable option is a testament to how fucking ignorant people are regarding the most basic separation of state and federal roles.
It's stupid commentary about how 48fps films require twice as much film compared to 24 fps films of the same length (meaning Kodak gets twice as much money). Kubrick shot it retarded formats all the time to be intentionally pretentious. He also shot in great excess, to invariably throw the bulk of it out. The people he bought his film from profited greatly from his behavior.
Not to mention that 60FPS is overkill - the human eye can't see any faster than 50FPS. Making 60FPS a complete waste of data.
48FPS is an unfortunate choice because it isn't a smooth 50FPS, meaning that it'll have weird pulldown issues on all TVs, but at least it's not throwing away frames the human eye is flat-out unable to see.
This statement again? I thought we fucking left that shit back in the Quake 2 days.
The human eye absolutely can and does see shit faster than 50 fps. Faster than 60 fps. Faster than 100 fps.
The human eye can definitely see things such as lightning, sparks, blinking LEDs, muzzle flashes, bullets, flying shrapnel, etc.
There is no hard limit on what is or what is not perceivable in terms of "frame rate". What matters most is WHAT we're looking at, not how fast it is. Beyond that, whether you're consciously aware of seeing it or not is an entirely separate issue.
Racism? Indians are usually considered caucasian not that I have much time for race classification myself. So what are you getting at? He was stating a personal opinion. Not racist. Not even bigotted. And not all Indian food is 'hot'. A lot of it is spicy - as in, using a lot of spices which are flavourful but not necessarily 'hot'. And yes some of it is hot.
Indians are considered Indian. They want to be considered Asian, because they want to duck the negative prejudice and stereotypes while still being thought of as up and coming in the tech sectors. Their argument is that India is in Asia. Well, so is Russia, and nobody affords them the luxury of choosing to be Asian.
Regardless, there's no way they're considered caucasian.
I can tell you didn't RTFA, or even RTFS. TFH is fucking misleading.
There is very little to do with open source, or openness in general.
Some guy is simply trying to get various players to buy into his system, with money and data, so he can then go back and run a few queries, maybe make a little graph, etc., and sell that data to others (for the price of money and more data).
It's basically stone soup, but he demands money as well as all the work. (And if he's not demanding money now, just wait until the date draws nearer.)
But this will never happen. The reason these companies are so tight lipped with their data is not because they don't see a benefit in sharing and accessing data, but because they don't dare let others see their dirty laundry, lest they expose themselves as liable for their fuckups.
Battery technology is progessing in slow motion. What's the point of bigger processors if you can't use them to their full potential because the battery won't last?
On the other hand, terminals and telegrams have progressed nicely. What's the point of having lines longer than 50 characters wide, wrapping, etc. if you're not going to use them?
Bonuses where I work are actually introduced as a sort of "market adjustment" -- our bonuses are calculated quarterly as a percentage of the profits of the company divided out per man hour across all employees, including salaried employees (who still punch the clock for purposes of calculating their bonus) but excluding upper management. Upper management does not receive a bonus. It's routinely on the order of $3-5/hour, unless we've had an exceptionally good or bad quarter.
But bonuses are never guaranteed. The reason that bonuses exist in the first place is to offer incentive for employees to get behind whatever initiative the company has in a given quarter and is not part of their base salary.
Google could just as easily take away bonuses from the other teams altogether.
Bonuses are guaranteed when you're a fat cat in the financial sector being bailed out by the taxpayers to the tune of trillions of dollars. Bonuses are not guaranteed when you're in the education sector and NOT getting bailed out to the tune of mere millions.
We DO still program in COBOL. And we DO still use SQL. And we do so because it works.
Not only does SQL work, it is the best at what it does.
The only people who hate on SQL are the people who don't understand databases. Generally, these are the same people who like labels, tag clouds and ruby on rails. They produce a lot of high level hand waving with regards to the actual code and endless amounts of "herp derp I dunno" when asked why their shit performs slower than the 10 year old system it's supposed to replace. These are bad people.
What really pisses me off is that everyone fucking agreed with me until Android came out, then suddenly Java was cool, the performance was considered "good", and the quality of code and coders that it tends to bring about is now the acceptable norm.
Slashdot Mirror
Last place I worked simply did a 0 wipe.
If a drive was too dead to wipe, we just used an electromagnet over it.
Dunno what it's real purpose was, but basically, plug it in, hit the button, get a powerful, undulating, pulsating, magnetic field.
Pass it over the drive a few times and toss it into the box.
Currently, we just toss the drives into boxes marked "...eventually".
"How do you design a form of Twitter, how do you change the retweet system, so that Twitter will end up gathering a body of reasoned debate?"
Might as well ask the Postmaster General how he plans to increase the number of Bigfoots they have as mail carriers.
Contingency plan: It's a desert.
Ru Paul is a tranny, but at least get his name right.
For storage in devices like printers, etc., where there might be a large amount of storage to facilitate print queuing, etc., I can see how something like this coul be useful. For instance, one of the options on these devices is to self-wipe on power cycle. For companies worried about security, this might be worthwhile in their printers, where the storage itself might be for the purpose of convenience, but they would rather be safe than sorry, and data destruction is of ultimately no consequence because the source for that data is found elsewhere. That way, they can dispose of their printers in relative peace of mind, because if someone powers on the printer to see what it has on it, then poof, no more data. Or even do the "unknown host" thing, and then all you have to do is make it clear to IT that you don't want the valid host (the printer) to survive the disposal process, so if they want to play with some baseball bats in a field to the point of smashing the drive controller... then that's fine with corporate.
Wrong.
When someone sends you a fax (instead of just riding it over on a dinosaur), and your fax sends the confirmation that it received it, but there's no printed copy yet (either because you need someone with access to that line to log in to view/print it, or because it was in the queue), you're legally screwed if you wipe out that data.
This one is way cooler.
It actually releases acid into the hard-drive platters:
http://www.deadondemand.com/products/enhancedhdd
If they've implemented this properly then you could send a remote command wirelessly that would wipe the hard-drive.
I'm pretty sure this is a forensic investigators nightmare...
But is it RoHS compliant?
My organization is "going green".
Absolutely not.
Not without a physical presence in the state.
That's like saying the cops can search your house if you call them pigs. It's just so fundamentally wrong.
Wrong. You also need to know this for every category of merchandise, and you need to know which categories each item of your merchandise is in in every state and locality. Furthermore, zip code and tax authority boundaries often do not coincide. There are likely other complications as well.
All Amazon needs to do is put forth a basic effort and let the customer handle any discrepancies on their (get this!) tax forms.
If someone in California is mad that they were charged tax on their 1000 pack of slim jims, then they can claim it on their tax forms. If Amazon wants to please these customers, they can add it in.
And remember son, zip codes have NINE digits, not 5. They're more than good enough to appease any tax collector.
Did you miss the last 100+ years of Congress collectively making the "jerk off/roll eyes" gesture whenever the issue of Constitutionality is raised?
Did you miss the 60s?
You probably did.
So there could be no good jobs if they charged $10 for the cable?
Somehow amazon can sell cables at a fair price, I bet they have some good jobs to offer as well.
https://www.mturk.com/mturk/welcome
Enjoy your future profession.
Seems like Sen. Durbin didn't like the way Amazon treated his state. Now we'lll all get to pay tax on everything. Thanks a lot Amazon.
Not just taxes, but higher prices. Setting up these tax tables is not an easy task. Some states tax specific items (such as clothing) while others don't. Some counties - and even some cities - add a % to the 'local' sales tax. Some states tax delivery fees. I could go on and on ...
These costs will be passed on to the consumers. And let's not forget that the sellers will be required to supply some sort of tax information to the consumers just in case the consumer needs to prove they paid the sales tax on their purchases (or didn't pay taxes because they are tax exempt in their own state). The states will need to perform long-distance sales tax audits on the sellers (and sales tax audits are a time consuming endeavor for the sellers).
Horse shit.
Setting up the tax tables is trivial.
It's a lot of work to input the data and maintain it every year, but that's what data entry monkeys are for.
All you need is a 3 column database for fuck's sake. Zip code. Tax rate. Effective date. (You need the date for historical shit since you'll want to process returns/refunds, generate old sales slips, etc.) This database already exists from various vendors. They'll even keep it up to date for you for a moderate fee. If Amazon were to buy an existing product, it would result in about a $0.0000001 cent increase per item. If Amazon was feeling frugal, they would just offer it up as a problem on their own Mechanical Turk service and let India handle it.
It's not a new tax. It's not a tax increase. It's a new attempt at the enforcement of an existing rule. I predict that we'll have just as much compliance under the new enforcement as we do under the current honor system. As long as "zero" is a valid input for taxes owed on any form, people will put it in.
You are mistaken, a new federal law could make enforcement trivial. The feds could simply say you must collect the tax and pay it to the state, or the feds could allow a state to sue a company even if the company had no physical presence in the state.
I think the Supreme Court would have something to say about such a law.
Or at least I fucking hope it would.
The fact that you think this is a viable option is a testament to how fucking ignorant people are regarding the most basic separation of state and federal roles.
It's stupid commentary about how 48fps films require twice as much film compared to 24 fps films of the same length (meaning Kodak gets twice as much money).
Kubrick shot it retarded formats all the time to be intentionally pretentious. He also shot in great excess, to invariably throw the bulk of it out. The people he bought his film from profited greatly from his behavior.
I remember when Flash animation went frameless.
No thanks.
Not to mention that 60FPS is overkill - the human eye can't see any faster than 50FPS. Making 60FPS a complete waste of data.
48FPS is an unfortunate choice because it isn't a smooth 50FPS, meaning that it'll have weird pulldown issues on all TVs, but at least it's not throwing away frames the human eye is flat-out unable to see.
This statement again?
I thought we fucking left that shit back in the Quake 2 days.
The human eye absolutely can and does see shit faster than 50 fps.
Faster than 60 fps.
Faster than 100 fps.
The human eye can definitely see things such as lightning, sparks, blinking LEDs, muzzle flashes, bullets, flying shrapnel, etc.
There is no hard limit on what is or what is not perceivable in terms of "frame rate". What matters most is WHAT we're looking at, not how fast it is. Beyond that, whether you're consciously aware of seeing it or not is an entirely separate issue.
Racism? Indians are usually considered caucasian not that I have much time for race classification myself. So what are you getting at? He was stating a personal opinion. Not racist. Not even bigotted. And not all Indian food is 'hot'. A lot of it is spicy - as in, using a lot of spices which are flavourful but not necessarily 'hot'. And yes some of it is hot.
Indians are considered Indian.
They want to be considered Asian, because they want to duck the negative prejudice and stereotypes while still being thought of as up and coming in the tech sectors. Their argument is that India is in Asia. Well, so is Russia, and nobody affords them the luxury of choosing to be Asian.
Regardless, there's no way they're considered caucasian.
I can tell you didn't RTFA, or even RTFS.
TFH is fucking misleading.
There is very little to do with open source, or openness in general.
Some guy is simply trying to get various players to buy into his system, with money and data, so he can then go back and run a few queries, maybe make a little graph, etc., and sell that data to others (for the price of money and more data).
It's basically stone soup, but he demands money as well as all the work. (And if he's not demanding money now, just wait until the date draws nearer.)
But this will never happen. The reason these companies are so tight lipped with their data is not because they don't see a benefit in sharing and accessing data, but because they don't dare let others see their dirty laundry, lest they expose themselves as liable for their fuckups.
Technically correct. The best kind of correct.
Seriously.
This ain't your run of the mill table salt.
Battery technology is progessing in slow motion.
What's the point of bigger processors if you
can't use them to their full potential because the
battery won't last?
On the other hand, terminals and telegrams have progressed nicely. What's the point of having lines longer than 50 characters wide, wrapping, etc. if you're not going to use them?
This is just like the page rank buttons via the old Google toolbar.
They took it away because users weren't using it, and advertisers/SEOs were.
+1 will be the same.
Google's result quality will continue to spiral downward.
Bonuses where I work are actually introduced as a sort of "market adjustment" -- our bonuses are calculated quarterly as a percentage of the profits of the company divided out per man hour across all employees, including salaried employees (who still punch the clock for purposes of calculating their bonus) but excluding upper management. Upper management does not receive a bonus. It's routinely on the order of $3-5/hour, unless we've had an exceptionally good or bad quarter.
That's not a bonus.
That's profit sharing.
Actually bonuses haven't been shown to be all that effective. That well known good idea is a well known fallacy:
http://www.ted.com/talks/dan_pink_on_motivation.html
I agreed with you until you trotted out a ted talk.
But bonuses are never guaranteed. The reason that bonuses exist in the first place is to offer incentive for employees to get behind whatever initiative the company has in a given quarter and is not part of their base salary.
Google could just as easily take away bonuses from the other teams altogether.
Bonuses are guaranteed when you're a fat cat in the financial sector being bailed out by the taxpayers to the tune of trillions of dollars.
Bonuses are not guaranteed when you're in the education sector and NOT getting bailed out to the tune of mere millions.
We DO still program in COBOL.
And we DO still use SQL.
And we do so because it works.
Not only does SQL work, it is the best at what it does.
The only people who hate on SQL are the people who don't understand databases.
Generally, these are the same people who like labels, tag clouds and ruby on rails.
They produce a lot of high level hand waving with regards to the actual code and endless amounts of "herp derp I dunno" when asked why their shit performs slower than the 10 year old system it's supposed to replace. These are bad people.
What really pisses me off is that everyone fucking agreed with me until Android came out, then suddenly Java was cool, the performance was considered "good", and the quality of code and coders that it tends to bring about is now the acceptable norm.