Quoting from http://www.youtube.com/watch?feature=player_detailpage&v=C4r...:
"Engineers do not give out 5s. If you tell an engineer that the possible rating scale is 1 to 5 and they like you, they give you a 4. Because tomorrow they might love you and then they would give you a 5. They probably won't, but they might, so they give you a 4 so that they have room. We all are totally okay with this. But the world is also full of this other class of people who if they like you give you a 5. They're quite consistent about it. 'I like you. I see nothing wrong with that. I'm giving you a 5.'"
The graph (with, admittedly, artificial data meant to portray an example) at http://www.youtube.com/watch?feature=player_detailpage&v=C4r... shows it most clearly, with the satisfaction numbers from engineering clearly trending down. Apparently, engineers don't like to fill out forms, while admins do, so satisfaction survey results also have a sample bias in favor of the 5s of admin staff.
You accidentally rating someone 3 for an average service can actually cost them their job. I'm hoping their algorithm uses some sort of a weighted average to offset the ratings of individuals such as yourself who consistently rate very low.
There are a lot of ways in which a ride can be unsatisfactory (smelly, creepy, crappy car, poor driving, loud music, etc.) but not that many in which it can be exceptional. Unless they show up in a Tesla Roadster or something.
i.e. If I always rate 3, but sometimes rate 1; then that might be similar to someone always rating 5 but sometimes rating 1-3.
Ah, but then a user might throw an Internet Fit(tm) and cause a public outcry about ratings being manipulated by Uber etc. etc.
I believe this is yet another case of managers using data without actually taking the time to understand the domain, or use it to identify problems and develop solutions. The approach seems to be nothing more than a facade of customer service.
B2C seems a bit different though you still see more 5s than deserved. Personally, I have no problem giving 4s for good to very good, but not truly outstanding.
I work on a software for routing deliveries (https://www.fleetnavi.com), and although we don't have this functionality built into the platform yet, it's the first thing to do when we get volume.
Aren't they all? Until you actually try to do it...
[In seriousness, we are excessively bad at estimating the true difficulty of problems, and making them sound 'easy' when they're not only serves to devalue the work of the people who actually spend the time and effort to actually figure it out.]
It was (bar the web front end) a relatively modest sub-30kloc chunk of C++.
Now the scale is different but in 10 years, the problem isn't necessarily much more complicated, just larger.
In fact I think a derivative of it now runs some of Yodel's operations.
I also love this:
the problem isn't necessarily much more complicated, just larger
If a programmer ever said this to me, it'd be a massive red flag that the estimate they're about to give me is going to be very wrong.
30kloc of COM/IDL as well that is. The actual routing engine was about 12kloc and the rest was the object model and deserializers. The routing engine was built on a two week binge of Red Bull, TAOCP and some papers printed out.
It really wasn't rocket science even though we charged them like it was.
From scratch by a non red bull enhanced team using c# instead it would probably about 3 months' work for two people to reproduce.
Also, there is no need to get a perfect solution anything better than what's out there is useful.
Ummmm... yeah, scaling the kinds of algorithms that one might apply to this sort of problem up to larger data sets is often extremely difficult.
I don't think it's as trivial because there are lots of things to consider. Some drivers are just SLOW and it will have nothing to do with traffic. Maybe all slow/terrible drivers use your app so all the route speed information is completely based on specific patterns set by your app.
I am in a major metropolis and I drive throughout the city, suburbs and adjacent cities regularly. I know the area and I have been driving for decades.
I have been using Waze for about a year now. The navigation routes it selects appear to be very good. They appear to be based on relevant factors too. I can only guess what variables they include in their calculation, such as weighted capacity, current traffic speed, etc. of the relevant route elements.
My experience with Waze is the opposite of yours.
This is hardly a trivial problem. It might be trivial to deal with a simplified mathematical model of it, but throw people into the mix and it suddenly gets very complicated. http://en.wikipedia.org/wiki/Reflexivity_%28social_theory%29
Google Maps would also change my London commute route on a daily basis given the changes in traffic patterns.
I did a few years in taxis but owning a car that is CC exempt is cheaper including parking in NCP holes. Part of the reason its cheaper is after some experience driving around the city, you realise that at least half the taxi drivers are taking the piss.
"the knowledge" is imminently replaceable by technology and is merely a party trick IMHO.
Once I had gotten a text from my wife as to where to meet her for dinner with friends. She didn't know the restaurant name, and had gotten the street name wrong. I just read the text to my London black cab driver, he asked me: "Did you mean XXX restaurant on [correct street name]?" (Note: there were multiple restaurants on the street). And sure enough, he was 100% correct.
That's the day I learned to really respect drivers with The Knowledge.
Conversely, got a taxi from Angel to Leyton and the idiot went via Poplar and the A13 and the journey cost me £55 for a £30 journey.
As you rightly point out, it doesn't mean that drivers won't still take the piss, but it definitely limits it. (Particularly when I compare it to virtually any other large city I've traveled to.)
There's an expectation that drivers keep their knowledge current. Certainly the examiners keep their knowledge current and test based on that.
Anyway, back on topic, "the knowledge" also covers alternative routes for road closures. I've usually been pretty impressed by black cabs. They know obscure little streets on the opposite side of town. Rarely have to give instructions. Compared to NYC where cabbies ask me how to get somewhere.
Yes of course!! Some other party tricks include reciting hours of lyric poetry from memory, adding large numbers in your head quickly, etc.
You're talking like the world is fair or something. There's not necessarily an equivalence between effort expended and value created.
This is really not the case with my London cab experience. These guys are super professional. In many other cities I've found cabs taking the scenic route but never with black cabs. I feel your 'half' claim extremely inflated off probably what was very few bad experiences.
Its also just a matter of time until cars provide visual aids for navigation, and not just the voice on a GPS device.
0: http://en.wikipedia.org/wiki/Disruptive_innovation 1: http://upload.wikimedia.org/wikipedia/commons/8/8e/Disruptiv...
Google Maps directions is pretty disruptive tech, right? Add 10 years of experience, lots of roads, lots of time to gather data, real-time traffic info, and when I ask it for directions from my current location in inner London to a place in central London[1] it still gives driving directions first, even though I switch to transit, walking, or cycling everytime.
But hey, innovation.
0: http://en.wikipedia.org/wiki/Clueless 1: http://i.imgur.com/c7XAuUm.png
Of course not. Technology will eat the world and improve on and replace humans in all complex cases. Like deciding what mode of transport to use in central London. Because disruption.
You are doing everyone except the driver a disservice. By failing to give low ratings to bad drivers, you are precluding good drivers from entering the market (because the bad ones will never get phased out, and they will saturate the market). You are also preventing consumers from making a well-informed decision, which limits the effectiveness of market mechanisms.
They let users crowd-source their own directions, along with much better turn-by-turn descriptions too. Eg, "turn sharp right just after the firehouse, go past the field and make a left just before the baseball field". Instead of "turn right, keep left and turn left".
Strongly disagreed. GPS has traffic information, a human driver does not.
Perhaps less anecdotally, local traffic is a major staple of local news radio and TV, which probably means it's important even for locals.
What's _really_ valuable, though, isn't real-time traffic information, but future traffic information. What matters isn't the traffic right now, but the traffic as it will be when you arrive at a given portion of the journey. I suspect that at present cabbies have the edge there, but that edge will also be swept away by predictive algorithms incorporating knowledge of typical traffic patterns plus lots of inputs about events that may affect traffic.
The latter point is particularly interesting if a navigation system acquires enough scale that it is directing a substantial fraction of the traffic. In that case, it knows not only what external events may affect traffic, but can further make decisions to control the flow, distributing and smoothing.
Sometimes the existing technology is still better.
Uber drivers in hilly cities like San Francisco never, ever think to avoid climbing right up and down the steepest hills - the algorithms don't tell them not to, there's no traffic and it's not a low speed limit, it just sucks for other reasons.
I had a driver last week who had never heard of Valencia St, and then misunderstood the GPS voice and accidently got on the freeway, getting us stuck in cross-bay traffic for 20 minutes just trying to get to the next exit. Of course I rated that ride 5 stars, because I'm not actually a psychopath ( http://www.forbes.com/sites/jeffbercovici/2014/08/14/what-ar... )
It's going to be a long, long time before we put anything approaching the depth of information that years of experience brings into our algorithmic routing systems. And startups are structurally disincentivized from trying to, anyway.