Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×

Comment Re:Easy fix (Score 1) 247

I find different answers as to whether they won the case or not. I'm not a lawyer, so it may be the judgement was nuanced such that interpretation by us mortals can be dicey.

By some accounts, documents of their internal tests showed that the extra plastic reduced the problem, yet they didn't act on it. It may turn out down the road in the course of history it didn't actually help in production, but their "sin" was ignoring their own best evidence of the time. They did a cost/benefit analysis internally on early test models.

Comment Re:Google: Select jurors who understand stats. (Score 1) 349

My syntax errors while coding are caught by the compiler. This is more efficient than proofreading. Other people at my company can spend their time doing documentation. I can do it, and do it well, when it is necessary. Otherwise I would prefer spending my time being productive.

Another fool who doesn't consider documentation as being productive. Also, being able to proofread has helped me spot and fix lots of bugs in other people's code, whether c, c++, php, whatever. Doing a compile just to find a typo is lame. I stopped doing that decades ago.

So keep minimizing the damage your bad reading skills bring to the table ... because stupid is as stupid does.

Comment Easy fix (Score 2, Informative) 247

I believe Ford lost the Pinto case because internal tests discovered the problem and also found an inexpensive fix: a $5 plastic wall between the gas tank and the impact zone of the tank.

In other words, the jury decided the company consciously bypassed a cheap and easy fix to shave a few bucks from manufacturing cost. It was a pretty simple tradeoff. I have to agree with Jury in that case. The car's statistical risk compared to other brands is moot (unless the other brands also discovered and skipped the easy fix, in which case, they may also be liable).

Comment 1D compression, AKA "Serialization" (Score 2) 129

Just about any dimensional space can be represented in fewer dimensions, or even 1 dimension, if you accept some lossy-ness or fuzziness. Imagine a string of digits and codes with the structure: x,y,z,type;x,y,z,type;x,y,z,type;x,y,z,type, etc... Where x, y, and z are coordinates in 3D space and "type" is the type of particle. Example single particle encoding: "3629342.3442, 4872042.3987, 193203.0482, Electron". There may need to be more "state" info about a given particle to make it workable, but you get the general idea.

Comment Re:IE 6 (Score 1) 218

You mean ignore the customers with spare cash to burn in favour of those with no (spare) cash?

Let's say old browser users spend twice as much money at your site as new browser users (typically mobile). Then the break-even point would be when you have twice as many new browser users as old browser users. Example:

IE 8 or less users:

-- 200 transactions per month.

-- Average expenditure: $80.00

-- Total revenue: $16,000

Mobile users:

-- 405 transactions per month.

-- Average expenditure: $40.00

-- Total revenue: $16,200

In this scenario, it's probably time to focus on mobile-friendly sites/apps and dump legacy IE support.

(I'm assuming your org doesn't want to re-code the same app/site for multiple browser versions.)

Slashdot Top Deals

FORTRAN is not a flower but a weed -- it is hardy, occasionally blooms, and grows in every computer. -- A.J. Perlis

Working...