But, the writers can't come up with a relate-able peril scene to set the emotional stage for abandoning the crew member without a powerful storm that put the ship in jeopardy.
The Martian was a great movie, as long as you didn't think about it.
If someone is capable of servicing, let alone programming, a robot s/he would not be working at McDonalds in the first place.
But that's all about to change...
Also, I worked at a couple of fast food restaurants when I was 16-17 years old, and even did some really brain-dead data entry work when I was halfway through getting my Master's degree in computer engineering. Just because somebody has really great capabilities does not mean that the world is going to give them opportunities to use those capabilities.
I'm thinking that every 100 or so hours of robot work will require some pretty serious (like 2 hours of) maintenance. If you replace a full restaurant staff with a single store manager and robots, you'll still need a guy who comes in every night, or maybe every other night, to rotate through and service each robot in turn. That lucky SOB is probably also going to be changing out the fry vat oil, detail mopping the floors and doing all the other crap work that the robots can't (yet) for decades to come.
If there's equivalent employment behind the robot arms, they will cost too much to be economically viable.
That's the thing, some people will move on to better paying careers, many will just be out of work.
And we'll all reap the reward as the fast food places lower their prices - right?
Absolutely - no such thing as too much fast food in the world, is there? Sadly, the people no longer employed by the fast food places will likely be a major component of their customer base. After all, with gross Bob not spitting in the fries anymore, they might actually be O.K. to eat?
O.K. sad to say, I haven't been in my local McD's, ever. I know when _I_ was in high school, _I_ worked in about 3 different food service jobs (2 fast, 1 hotel restaurant), and all were 90% staffed with high school kids - low 20-somethings for management, and since the roast beef "chef" had to handle a sharp knife, he was an 18+ year old loser dude living 6 up in a trailer... Of my high school friends who had jobs (maybe 30% of kids in my classes) over half were in fast food.
We do go to Wendy's quite a bit, and employees in the Wendy's we patronize are a mix, some definite high school especially in one particular suburb area, lots of younger people, and much more 40+ than I remember from when I was working there.
McDonalds et. al. are about a predictable customer experience - God knows not an excellent one, just predictable. Robots should deliver that much better than high school kids.
Hopefully some of those ex-employees go to school, learn to build, program, maintain, and recycle the robots. Most of those jobs should pay better than $15/hr.
As for the rest, they can spend their time lobbying for UBI.
If code is repetitive enough, there should be an app (developed) to do that.
Nobody follows patterns as well as a program. And, if the pattern needs changing, change the program that writes the code - it will rewrite the code for you in the new pattern in milliseconds.
The "whoosh" for me in this is that I develop the solutions to the hardest parts of my software problems when I am far far away from the keyboard. Sitting down and grinding out code is one thing, but elegant solutions to tough problems rarely come while staring at the screen.
Hearing the "8 to 12 hours to stop" reminds me of MRIs and their superconducting (lossless) magnets that take a really long time to start. There should be some kind of low loss energy storage potential in superconducting electromagnets. Lots of problems there, but moving parts (in the major energy pathways) isn't one of them.
One of the original natural resources of Phoenix was pollen free air - invaluable for people with allergies. Ironically, the successful development of Phoenix, largely based on this resource, has destroyed the resource just as surely as a coal mining town mines out a seam - get enough people in a city and they're sure to plant grass and flowers in their yards.
They had too much security and stability - all that security made them more difficult to use, and they lost market share to the likes of Facebook. As for stability: I'm still at a loss as to why mass market users seem to prefer buggy crashy platforms, maybe it makes them feel more like "cutting edge hackers."
I'm complaining about extremism in the service offerings. There's service for the masses, and service for the 0.5% - and, frankly, service for the masses sucks.
Titanic days had it better - multiple classes, if you want to travel steerage class, that's available for very very cheap - but if you want something a bit better, that's also available for something less than the champagne, caviar, and personal servants attending your every need at a moment's notice price.
I agree with your assessment of computer drivers, in solo competition. In (non-cooperative, limited inter-driver communication) competitive situations, I think computer drivers would have a hard time besting a pack of humans - such as you might find in NASCAR, or on the commute to work.
Google is already reaching the conclusion that: a computer driven car (mixed with human controlled cars) can only be safely operated below 30mph. The same could be said for human driven cars.
Water soluble glue?
But, the writers can't come up with a relate-able peril scene to set the emotional stage for abandoning the crew member without a powerful storm that put the ship in jeopardy.
The Martian was a great movie, as long as you didn't think about it.
UBI - Universal Basic Income: money for nothing.
If someone is capable of servicing, let alone programming, a robot s/he would not be working at McDonalds in the first place.
But that's all about to change...
Also, I worked at a couple of fast food restaurants when I was 16-17 years old, and even did some really brain-dead data entry work when I was halfway through getting my Master's degree in computer engineering. Just because somebody has really great capabilities does not mean that the world is going to give them opportunities to use those capabilities.
I'm thinking that every 100 or so hours of robot work will require some pretty serious (like 2 hours of) maintenance. If you replace a full restaurant staff with a single store manager and robots, you'll still need a guy who comes in every night, or maybe every other night, to rotate through and service each robot in turn. That lucky SOB is probably also going to be changing out the fry vat oil, detail mopping the floors and doing all the other crap work that the robots can't (yet) for decades to come.
If there's equivalent employment behind the robot arms, they will cost too much to be economically viable.
That's the thing, some people will move on to better paying careers, many will just be out of work.
And we'll all reap the reward as the fast food places lower their prices - right?
Absolutely - no such thing as too much fast food in the world, is there? Sadly, the people no longer employed by the fast food places will likely be a major component of their customer base. After all, with gross Bob not spitting in the fries anymore, they might actually be O.K. to eat?
O.K. sad to say, I haven't been in my local McD's, ever. I know when _I_ was in high school, _I_ worked in about 3 different food service jobs (2 fast, 1 hotel restaurant), and all were 90% staffed with high school kids - low 20-somethings for management, and since the roast beef "chef" had to handle a sharp knife, he was an 18+ year old loser dude living 6 up in a trailer... Of my high school friends who had jobs (maybe 30% of kids in my classes) over half were in fast food.
We do go to Wendy's quite a bit, and employees in the Wendy's we patronize are a mix, some definite high school especially in one particular suburb area, lots of younger people, and much more 40+ than I remember from when I was working there.
Will they support "standard" IO hats, like the sense modules with accel, gyro, etc.?
I think not for a very long time - which makes many of the interesting apps not interesting at all.
So, what we need now is work for the 90% of displaced employees who are _not_ getting jobs building, maintaining, and recycling the robots.
McDonalds et. al. are about a predictable customer experience - God knows not an excellent one, just predictable. Robots should deliver that much better than high school kids.
If there's equivalent employment behind the robot arms, they will cost too much to be economically viable.
That's the thing, some people will move on to better paying careers, many will just be out of work.
In the 1980s, $3ish minimum wages were also not living wages.
Hopefully some of those ex-employees go to school, learn to build, program, maintain, and recycle the robots. Most of those jobs should pay better than $15/hr.
As for the rest, they can spend their time lobbying for UBI.
Code, much like art, cannot be judged because of this.
Code, much like everything else in life, will be judged - whether you think it is fair or not is irrelevant.
If code is repetitive enough, there should be an app (developed) to do that.
Nobody follows patterns as well as a program. And, if the pattern needs changing, change the program that writes the code - it will rewrite the code for you in the new pattern in milliseconds.
The "whoosh" for me in this is that I develop the solutions to the hardest parts of my software problems when I am far far away from the keyboard. Sitting down and grinding out code is one thing, but elegant solutions to tough problems rarely come while staring at the screen.
As long as they don't develop the control software in Ruby, we should be safe.
Hearing the "8 to 12 hours to stop" reminds me of MRIs and their superconducting (lossless) magnets that take a really long time to start. There should be some kind of low loss energy storage potential in superconducting electromagnets. Lots of problems there, but moving parts (in the major energy pathways) isn't one of them.
One of the original natural resources of Phoenix was pollen free air - invaluable for people with allergies. Ironically, the successful development of Phoenix, largely based on this resource, has destroyed the resource just as surely as a coal mining town mines out a seam - get enough people in a city and they're sure to plant grass and flowers in their yards.
They had too much security and stability - all that security made them more difficult to use, and they lost market share to the likes of Facebook. As for stability: I'm still at a loss as to why mass market users seem to prefer buggy crashy platforms, maybe it makes them feel more like "cutting edge hackers."
The longer people look without finding increases confidence...
That's more or less the basis for CryptMT...
I'm complaining about extremism in the service offerings. There's service for the masses, and service for the 0.5% - and, frankly, service for the masses sucks.
Titanic days had it better - multiple classes, if you want to travel steerage class, that's available for very very cheap - but if you want something a bit better, that's also available for something less than the champagne, caviar, and personal servants attending your every need at a moment's notice price.
I agree with your assessment of computer drivers, in solo competition. In (non-cooperative, limited inter-driver communication) competitive situations, I think computer drivers would have a hard time besting a pack of humans - such as you might find in NASCAR, or on the commute to work.
Google is already reaching the conclusion that: a computer driven car (mixed with human controlled cars) can only be safely operated below 30mph. The same could be said for human driven cars.