Given that every time I try to check into a hotel I spend 20 minutes waiting for my tun then waiting for the clerk to type in the info I tell them, I doubt it will be slower. My guess is it will save me 19 minutes. Another great win for automation.
For the
A pretty trivial non-problem. Make a mutable one and just don't change anything in it.
You're not an outlier, but you did do exactly the right thing. You cancelled in person, instead of over the phone.
In my town, there's a perpetual 45-minute line of people at the comcast office. Even though the lady that works there is helpful and friendly, I'd rather talk to an idiot on the phone for 20 minutes than waste an hour or more driving to the office, waiting in line, and dealing with the issue in person.
Is the line shorter in other towns?
What kind of pockets do you have? I fit my wallet, keys, and Note all in 1 pocket.
I think that HTML5 would make it far worse. Where do most of these bad programmers start? Where the barriers to entry are lowest-- javascript. You'd be making the problem worse, not better.
I do think that there's much improvement to be made with permissions on mobile phones. But that's a separate problem, and one a lot of the Android custom ROMs do well.
Design guidelines are just recommendations. Frequently bad ones. A developer should design the best UI he can, not follow what Google says regardless of whether it fits. And most developer guidelines, Google and Apple both, are crap.
The problem is that the whole app movement has brought in a whole slew of crappy developers who's idea of coding is to search stack overflow or git for stuff to copy paste. They don't read it, don't understand how to use it right, and expect it to magically work. Worse half of the people writing that code fall into the same category, so its the blind reading the blind. If you pick a library off of github and assume it will work, you deserve what you get. Unfortunately your users don't.
These people have been around for a while (they used to be "web developers" and program by copy pasting big chunks of javascript). The problem is that on a phone they can do more damage. In a world where the number of quality programmers is fixed and far less than the demand for programmers, how do you fix it? Making it easier to program actually hurts, you end up with those crappy coders trying to do even more. Maybe its time to raise the barriers to entry for a while.
Sure they are. My school had AP classes, but not everyone in the class takes the test- those who didn't think they would pass skipped it and save the 70 bucks. In each one the teacher suggested to a few people not to take the test because they didn't think they had the understanding to pass. In at least 1 case they talked someone into taking the test when they were borderline (I think he passed).
As for financial incentive- read the article. Google was paying teachers directly. It was going to the teachers, administrators not involved. With financial incentives I can easily see the teachers telling more/all of those tweeners to take it and see if they pass.
Lets be fair- its always been boring. Nobody gives a fuck about these sports for 3.9 years out of 4. Nobody should care about them the other
You tell teachers they'll be paid if more people pass a test. So they encourage more of their students to take it. Many of those aren't ready, they're just hoping they'll pass for a payout. So the pass rate goes down, as the majority of additional takers weren't capable. Yup, statistics work.
I don't have kids, but when I was one my parents were spending most weekends taking us somewhere to do something. Watching movies was not on the agenda, at least not at home (maybe the occasional trip tot he movie theater). Why would you waste prime family time on movies? You do those on the weekdays because there's fewer entertainment options and most of them are closed by the time you get home from work.
I think you have that backward. M-Th is when you go to work then come home and want to just watch TV for the night. F/S/S is when you go out and do something because you don't have to be home early.
He can't help it, the leads were weak.
Unless you like carrying a smartphone in your hands all the time in crowded places, or like leaving your smartphone on the table where it can get lost or stolen, the smart watch is better. Nothing beats a watch for quickly checking something. Constantly fishing a phone out of your pocket, unlocking it, checking stuff and putting the phone back in your pocket can become extremely tedious quickly.
Can't say I've ever left mine anywhere. And I have no problem getting it out of my pockets. Meanwhile a watch is fucking uncomfortable to wear, and tends to break within a few months as you accidently bang it on things. I cried tears of joy the day I realized my new cell phone meant I'd never have to wear a watch again. I think taking it out of your pockets is a problem only about 1% of the people in the world have, everyone else seems to prefer the phone.
There's a few other things in the hardware that would bring up issues:
*Battery- smaller form factor, smaller battery, less life. People complain about that already
*camera- is there any place to put a camera on there that isn't going to be blocked by write hair or inconvenient to take a picture with? Can you see the screen to see the image? is it easy to hold your arm steady enough?
*Text input- voice recognition isn't there yet, and even when it is you don't always want to be public with your messages. How do you type on one quickly?
*Is there enough physical room for everything?
*Heat- if we do all that in a watch, how hot will it get? Will it become a safety hazard or uncomfortable to wear?
*Power- even if everything works, a phone can have the same stuff and more, due to form factor. So why would you limit yourself to the watch?
There's got to be more to life than compile-and-go.