This is discrimination, pure, simple, and fresh-squeezed.
Apparently this isn't their only issue in attempting to prevent infections.
He's right. Man-boobs or GTFO.
Posted by Soulskill on Monday April 20, 2015 @09:11PM
from the i-don't-remember-that-episode-of-The-Wire dept.
I think the editor beat them to it.
Script: The Next Hope
Prologue: In a nearby star system, the local senate is embroiled in discussions over a housing and property dispute. Little does anyone know that more sinister elements are afoot...
That's a terrible analogy. An accurate one is two runners - one with a red shirt, the other with a green one. Since red is an energizing, aggressive color, the green shirt must obviously be better because they wore a shirt that relaxed them. Right?
The red shirt must be a better runner because they were looking at the relaxing green shirt. Who pays attention to their own shirt color during a race?
That's a bit draconian. Try this instead:
- Write a program to unlock this box.
- If you can unlock it, you can get your smartphone out of it.
- You can't use your smartphone until you get it out of there.
- A person typically goes insane without smartphone use in 7 hours, and comatose in 14 hours. Shorter for teenagers.
- Good luck.
It's actually Evergreen Terrace, but hey, it's all good.
Let's assume I am a billionaire who commutes mainly via private helicopter. It doesn't bother me at all to throw a few thousand dollars toward a local road-improvement project. For a struggling single parent to do the same would be a significant hardship, even though they would be far more likely to actually use and benefit from the improved road.
Billionaire: Why are you late getting here to fly me to work?
Pilot: Hit a pothole and got a flat.
Billionaire: Why can't we take off?
Pilot: Fuel truck hit a pothole and got a flat.
... functional, readable, testable
From the maintenance perspective, when you can't make the code meet some standard, comments describing what you missed and why (time, spec conflicts, didn't care enough) are helpful. This hints to the next maintainer that modifying a piece of code that missed some good-practices target has additional considerations or hidden pitfalls, or that it can be fixed/extended/replaced with impunity.
they'll switch over to information kiosks narrated by an asexual monotone computer. And if that turns you on, well, I don't know what they'll do.
If that happens, you'll have passed Turing's other test.
Maybe they'd get more callbacks with this approach.
So, let's say that hire and train those who would otherwise be hired as booth babes so that they're useful temporary representatives of products and companies. Let's say they show up dressed in business or business casual attire.
Seriously, when you first went to one of these conferences, wasn't your first assumption to walk up to them and ask about the vendor's product; and then when they didn't know anything about it, say to yourself, "Why would they just come here and hang around at a vendor's booth when they can't talk to people about the product? Couldn't they get paid just as well doing something less stultifying?"
Even that may not be sufficient. After this story, I would:
- personally pay to install cable internet for the existing owner
- call their real estate broker
- have them download a preferably large nightly build for some project
- have them run md5sum.exe on the nightly build, provide the result, and compare it to mine
A little paranoid, but it's a minor inconvenience compared to having to do without broadband at all.
If nothing sticks to it, why couldn't you just refill it?