In NYC, we have "dedicated lanes" for some of our buses. But there are no spikes in the ground and when someone parks in one, the bus doesn't actually smash the car out of the way. So we're back to the mercy of traffic.
849 karma · joined April 6, 2009
In NYC, we have "dedicated lanes" for some of our buses. But there are no spikes in the ground and when someone parks in one, the bus doesn't actually smash the car out of the way. So we're back to the mercy of traffic.
> When I assure him I’m after the whole story, he softens.
And yet, is not blaming almonds exactly what the author proceeds to do?
I'm not saying they aren't to blame, but this seems a bit dishonest.
There isn't a large group of stupid people loudly calling themselves "gay". Nor is "gay" the only widely-known English word for stupid.
The word "cracker" has no traction whatsoever. Partly because it sounds like something you put cheese on and partly because prominent crackers refuse to embrace it.
I'm not saying the current situation is ok, I'm just saying the fight is hopeless.
You can also shape culture using rules. For example, at Google SRE, there was a rule that after any outage a post-mortem was to be written. It described why the problem happened, why that happened, etc. and how to prevent each level from re-occurring. Things like "it was person X's fault" or "we will be more careful" were forbidden. Fault and fixes had to be in technology or procedure, not people. It helped shape a culture of coming forward with problems and of looking for solutions. It didn't work perfectly, but it helped.
Most won't, but with 64k plaintiffs, most of them long-winded, it'll still need to be a patient judge.
return ERRCODE;
Would have produced the exact same bug.When I was at MS, we usually used the command line to change settings. It was horrible. It used GUIDs. Literally GUIDs. But it was a stable target. You didn't have to relearn it every nightly build. And you could script it.
We sort of assumed that if the control panel would sit still we could learn it easily enough, but that assumption couldn't be tested until it was too late.
For example, if BlackGirlsCode produces a generation of black women who are perfectly capable programmers but believe that they're only capable "for black girls" and not by the tougher standards of asian men, that's backfiring. Such graduates will not go on to found startups or even apply for jobs at the best companies. They will probably have less overall life success than if they hadn't entered the program.
Or if the graduates are fine, but it's a resume stain, because everyone who hears about it thinks "These are people who need special help. I don't want to work with people like that. I want to work with self-sufficient people." So the graduates can't find jobs or investors. That's a backfire.
Or if it works well for the small number of people directly touched, but the much larger number of people peripherally touched become more likely to think that programmers are divided into "black" and "nonblack" and subconsciously act on that. It's a smaller effect, but a larger group of people and could easily be a net loss. That's a backfire too.
How much you can spin the seat without those movements causing problems is an open question.
Airplanes are an encouraging precedent. They often make quite sharp turns at extremely high velocity, but tilt into them such that there's almost no perceived lateral acceleration.
Not Something Positive :)