And yet, we've had very wonderful trips every year.
I couldn't have said it better. The problem is that this is likely to be a one-off response. If we started seeing a mass killing of police every time some unarmed citizen is offed by an officer, you would actually see some action. As it is right now, it's not enough of a problem for politicians to want to take on the police unions.
One of the first things you learn as a new driver is not to watch the car immediately in front of you, but rather to watch several cars ahead (and behind). This gives you more time to react to traffic changes, and you still see the actions of the nearest vehicle anyway.
Sure, Tesla's Autopilot will have a much faster reaction time. That will help, but it's not good enough - it only allows Autopilot to react to conditions that the nearest vehicle also reacts to. A deer running toward the road, looking to jump in front of you? A kid chasing a ball toward the street? The vehicle in front of you swerving out of the way of an object in the road? Autopilot doesn't handle any of them, and can't as long as it lacks the ability to see more of the environment around it.
Autopilot is dangerous to Tesla drivers and others because it removes the attention of the driver from the road. It's basically like asking a nearly blind friend with fast reflexes to take the wheel while you read a book or play games on your phone. If it's not legal for a nearly blind driver to take the wheel, Autopilot shouldn't be legal either.
Oh come on. Rails 4 has been out for over 3 years ( http://weblog.rubyonrails.org/... ) not counting beta versions. If you haven't been bothered to update your public-facing application to 4.x in 3 years then yes, you're on your own. If you were one of the volunteers donating your time to run the Rails project would you want to support every version forever? You can always feel free to pay a developer yourself to fix any security holes that may turn up in Rails 3 in the future. And heck, you could sell those patches to other laggards!
But it'll eventually get there, and we (as a society) really need to be discussing how we're going to handle that new world where most jobs have been automated.
Automation is about pushing more wealth to the ruling class and minimizing unavoidable costs. Every time a job like this gets automated, displaced workers head to another employment pool. As those pools get crowded, the salaries go down.
"Plumbers will always make a good living."
"Until the displaced security guards get minimal training by a contracting firm and there is a flood of certified plumbers."
2. Shot at in US: ~7,944:1
I'm just curious whether the odds of being shot in the USA were corrected for suicides? Otherwise you're partially determining how likely you are to shoot yourself while visiting in the USA... Probably an interesting thing to know (and standing in the TSA lines might indeed make you suicidal) but probably not quite the risk/worry that set off this whole thread
Well, I'm sure they really would have taken them, but the customs paperwork is just SO unpleasant, you know? And there is the matter of the 17% import duty on livestock, and there needs to be proof that someone will feed and house the chickens so that they don't become a burden on society. We can't have foreign chickens just coming into the country whenever they want.
Racism is making judgements and assumptions about a person based on their race (or apparent race). It's not racist to be aware of race or use it as an adjective. Ignoring those characteristics is called "color blindness" (https://en.wikipedia.org/wiki/Color_blindness_(race)_in_the_United_States) and is rather controversial. You might not like the adjective ("Black" vs "African American"), and that's valid. Just use a different adjective for the same characteristic.
Per that article, 'Martin Luther King, Jr.'s central hope was that people would someday be judged by "the content of their character" rather than "the color of their skin".' He's not saying people shouldn't recognize the color of their skin; just that they should not be judged by it.
In fact, studies have shown that children raised in a "color blind" environment develop their own judgements about their schoolmates, including juvenile observations about race, gender, height, weight, etc that are shockingly biased because they simply haven't been shown anything different. This is especially true in communities that aren't very diverse, where there might only be one or two minority kids available to base those judgements on.
For example, go ask someone who lives in Japan what they think of black people in America.
Use the appropriate adjectives to describe what you're thinking of, and don't make judgements about people simply because they exhibit some of the characteristics described by those adjectives.
The more claimed victims, the more improbable it becomes that they did not inform the authorities and seek prosecution for that activity.
Or, perhaps it means the perpetrator developed a well-refined method of getting dirt on victims, perpetrating the assault, then blackmailing them into silence.
Uber management did NOT think this through.
I think you're right and they've adopted the ego of a 900-lb-gorilla monopolist a bit prematurely in their lifecycle.
As a further example, was the game-of-chicken Uber played with the City of Austin. As an example set to frighten other cities that might try to stand up to the bully, they left Austin. But they left a community fertile with tech startups that have jumped at the opportunity to fill their vacuum. These are people / companies that NEVER would have gotten funded to compete against Uber prior to its departure. They left the factory in place, so to speak. The message to other cities looks to be that there is life without Uber.
But perhaps the biggest reason pressure triggers aren't even worth discussing in these situations is that all cargo areas on transport-rated aircraft are pressurized.
Yeah, but not to sea level. You could set your bomb to go off at 7,000 feet and be pretty sure it'll detonate at cruise altitude.
You could use an iPhone with it's internal barometer to do the job...
But our team works together. Collaboration is key to our work. And collaboration in a virtual setting is not nearly as effective. We also meet with other teams and clients
Dealing with remote teams as we have to is measurably less effective
This is one of the things I was thinking of when I said just as productive from home if the company is set up correctly for it. Over my last 3 jobs I've worked in one totally virtual, one totally physical (bullpen), and now one which was totally virtual until we got bought by a company that really wants everybody together (but my team is still virtual because we're geographically scattered). And I've worked for many years in combinations of cubes and physical offices (with doors).
In my experience, the totally virtual are the most productive. At the bullpen company, everybody had to wear headsets to drown out the noise in order to concentrate on coding. So, even though you were a few feet away from someone, you still used IM to get their attention. But meetings sucked for the person who was on the road or home sick because the assumption was that everybody would just pile into the conference room, and oh yeah, there was a phone the remote guy could dial into, but he couldn't hear that well, couldn't see, and nobody would give him a chance to talk so he might as well have just watched a recording of the meeting for all he was able to participate. And half the time he wasn't invited to any last minute meetings because people forgot about him. And of course, everybody wasted a couple hours a day driving to work when they could have been writing code.
Your case of 1 day a week in my experience is the worst.. because the majority of the time people are meeting in person, and so they don't make sure to set it up to work well for the remote people. When everybody is remote, nobody gets left out of the conversation. I'll give you an example at the current company. We had a quarterly meeting. Most of the people were physically there, but of course my team was virtual. Hey, they set up a video feed for us! Yay! Oh, the camera was pointed at the audience so we couldn't see anything written on the whiteboard. But we could see a bunch of bored people sitting there... Not very effective. But the key is, the people running the meeting didn't think about that, and didn't notice it, because they're used to just piling into the conference room. It would have been much better if everybody was just in their personal workspace using something like GTM with the speakers sharing their screens while they talked.
My team is very collaborative. I think it's faster to set up a meeting with people (you don't need a conference room) - in less than a minute you can have everybody on a joint video session, sharing screens when necessary. And you never get that guy who doesn't seem to have anything better to do than stop by your cube and distract you when you really would rather get some coding done. People don't do that "avoid work by wandering around" when it's all Slack/Skype/GTM. And when you want it quiet... it's totally, blissfully quiet. It's so much better for a coding environment. I've worked in offices with doors you can close and that's great for the quiet, but nobody knows whether your door is closed because you don't want to be disturbed or you just wanted quiet and you don't want to knock incase he really doesn't want to be disturbed, so the collaboration really suffers.
With our virtual team, since a great deal of discussion is going on (typically slack) you can always look to see what people were discussing an hour ago while you were tied up. It gives you an automatic transcript of a lot of the discussions. You can participate if you want, or you can hide that window when you really just want to concentrate on that key algorithm you're working on.
Anyway, I'll just finish by saying that if you've experienced a team where some people telecommute and some don't, you've probably seen the worst case scenario. It's probably true that all physical or all virtual is better than a mix of the two.
Asynchronous inputs are at the root of our race problems. -- D. Winker and F. Prosser