At any rate, this eventual reduction in insurance is why I started by saying "Initially at least". With time, the cost of manufacturing self driving cars will also go down.
3,810 karma · joined May 17, 2007
At any rate, this eventual reduction in insurance is why I started by saying "Initially at least". With time, the cost of manufacturing self driving cars will also go down.
(edit) The article suggest self driving cars, and by extension Google's ridesharing service won't be ready for 2-5 more years.
All proceeds not used go to UGA and GT equally
(disclaimer: I went to GT and think this is a ridiculous indictment but am not affiliated with the gofundme site or Ryan)
Lookup the British East India company
Can you point me to where PG said this?
"But if you have 1400 alums reviewing apps, by definition you are going to have scoring that is biased against finding black swans, regardless of how many silos you create."
Why do you think the scoring is biased against black swans?
..and this is because Facebook and Google are not independent companies with their own self-interest at heart, but stooges of YC remote controlled by a secret cabal of YC alumni?
That chain of events ultimately led to YC W12.
I missed my first startup school in all these years last Friday, but it was to talk to customers so I don't feel that bad. I hope to be back next year!
And yes, I do remember the Nomad. At the time the iPod launched, my music player was a Sony Discman and pre-ipod, I would have bought the Nomad in a heartbeat if I could.
I think Garmin forerunner will be to the future of wearables what Nomad was to the future of music in 2002.
Edit: Some more context on how this all works from the other ApplePay thread on HN: http://clover-developers.blogspot.com/2014/09/apple-pay.html
I think it is safe to say that the entire YC batch took home the advice Antoine gave to the Plangrid team that night.
Plangrid uses iPads and they have a large number of prominent customers listed on their website who clearly find it very useful.
The RBI rule requiring a one time pin for all online transactions is unwise, a huge barrier to good UX, and should be removed.
Having said that, Uber is not being shutdown in India. Even if no changes are made to this rule by the Oct 31 deadline, which of the following is more likely: Uber leaving a country with several hundred million potential users, or Uber (and every other company who does online transactions) changing their UI flow to accommodate the RBI requirement?
Disclaimer: My company Summon competes directly with Uber.
I see you work for iCracked =) I am a user, and have been seeing your iCracked cars around. Really interested in how your system works in analogous aspects!
Our new system actually decides how many drivers to send the request to based on their reliability rate. So someone with a 100% reliability rate (or close enough) will be the only person getting a particular request.
Our minimum reliability rate is 50% but a vast majority of our rides are done by what we call our exclusive drivers who have a 70% (soon 80%) reliability rate requirement with additional perks. I will update the post to clarify this!
There are multiple reasons why a driver might not accept a ride but they all revolve around the fact that drivers are not our employees and they often are unable to or forget to become unavailable when they should be:
- She just took a break to have lunch (should have turned the app to unavailable but forgot)
- She is a taxi driver (we have both taxi and personal drivers on the platform) and just picked up a ride on the street and got a 2nd ride before she could turn unavailable (we measure volume in rides/second at busy times)
- She drives for other platforms as well and accepted a ride request on it before she could turn unavailable
- Drivers have 15 seconds to accept a ride before it "goes away". Sometimes the real world intervenes and you can't accept the ride in 15 seconds, especially if you are driving and not pulled over.
One more data points:
- I can't speak for Uber/Lyft but if you talk to their drivers you will see that their requirements are similar if not lower.
There are multiple reasons why a driver might not accept a ride but they all revolve around the fact that drivers are not our employees and they often are unable to or forget to become unavailable when they should be:
- She just took a break to have lunch (should have turned the app to unavailable but forgot)
- She is a taxi driver (we have both taxi and personal drivers on the platform) and just picked up a ride on the street and got a 2nd ride before she could turn unavailable (we measure volume in rides/second at busy times)
- She drives for other platforms as well and accepted a ride request on it before she could turn unavailable
- Each driver has 15 seconds to accept a ride before it goes to another driver. Sometimes the real world intervenes and you can't accept the ride in 15 seconds, especially if you are driving and not pulled over.
One more data points:
- I can't speak for Uber/Lyft but if you talk to their drivers you will see that their requirements are similar if not lower.