Forgot your password?
typodupeerror

Comment: Re:No calculators (Score 1) 870

by Grey Haired Luser (#33570068) Attached to: Preventing Networked Gizmo Use During Exams?

> Pfffft. The only correct answer is to wake up or stop haullcinating, because there's no such thing as a
> perfectly smooth (frictionless) surface.

You must not have met many physicists... frictionless surfaces, two dimensional
potentials, spherical horses... I could go on and on. And this is during real
work, not just exam questions.

Knowing _which_ parameters you can idealize is one of the things which
separates a good physicist from a bad one! ;-)

Comment: Re:From: "PC Folk" (Score 1) 1067

by Grey Haired Luser (#32235288) Attached to: Steve Jobs Says PC Folks' World Is Slipping Away

>>> Didn't we despise Microsoft because of how successful they were?

>> Maybe you did, but my objection to them was for the multiple crimes they committed, and >>the dismal quality of their products.

>Now Apple is doing the exact same thing MS did back in the 80's and getting a free pass.

Really? Apple is a convicted unlawful monopolist? Where was this court case?
I think I missed it.

Comment: Re:Perspective from a Juror on this Case (Score 5, Insightful) 982

by Grey Haired Luser (#32010864) Attached to: Terry Childs Found Guilty
Jury nullification consists precisely in ignoring that particular instruction: that you should only apply the law and not judge the law itself. Duh. This notwithstanding, if you say you agreed with the law, and thought it had broken it, well, then, obviously you did the right (moral) thing and have a lot more info on the case than random slashdotters. Well done.

Comment: Misses the point: fix bugs for the future too! (Score 1) 201

by Grey Haired Luser (#31654254) Attached to: The Economics of Perfect Software

If you're trying to ship quality software, you don't just _fix_ bugs,
you treat each one as a learning experience, a mini-laboratory of
"what went wrong" here. You don't just fix _this_ bug; you adjust
your processes/standards/whatever else so that this bug can never re-occur.
You also find out where _else_ this bug may have manifested; often
in slightly different ways. It's unlikely to be the only exemplar of
this type of bug in your system.

Just doing a cost/benefit analysis saying: nah, unimportant, don't fix
it is stupid. _This_ bug may be unimportant, but it may exist somewhere
else where it is important, or someone may write the same bug tomorrow
where it will be important.

Comment: Pointless in Vegas (Score 5, Insightful) 597

by evel aka matt (#29766149) Attached to: Computer-Based System To Crack Down On Casino Card Counters

Las Vegas has made card-counting a non-factor. Between high deck-count shoes, variant games with unfavorable rules ("Super Fun 21"), and early shuffle thresholds, even a player keeping a perfect count cannot create a significant edge. And the million people who show up to try their hand at it and fail far make up for the cost of the few who can eek something out anyway.

Comment: Re:Scratch (Score 1) 962

by Grey Haired Luser (#26071727) Attached to: Best Introduction To Programming For Bright 11-14-Year-Olds?

I second this. I've got both my sons, aged 8 and 12, totally hooked.
The 12 yr old is off writing games where sharks chase divers collecting
pearls, with 3 lives and game over, the whole 9 yards. It's incredibly
easy and intuitive, and teaches a distributed, message passing programming
style.

Enjoy!

No amount of genius can overcome a preoccupation with detail.

Working...