28 ms·
I think you will find that Uber engineering is just like any other place - a lot of silly mistakes while people learn on the company dime. This entry, for exam
by papito 5y ago
I think you will find that Uber engineering is just like any other place - a lot of silly mistakes while people learn on the company dime.
This entry, for example, mentions how they avoided Go routines as a "performance concern" even without any data to prove it. It's bush league level to think you can do it better yourself.
https://eng.uber.com/go-geofence-highest-query-per-second-service/ https://eng.uber.com/go-geofence-highest-query-per-second-se...
- thundergolfer 5y agoThat post you linked is the one that got heavily criticised by a Bing Maps engineer for being under-engineered[1]. 1. https://medium.com/@buckhx/unwinding-uber-s-most-efficient-service-406413c5871d https://medium.com/@buckhx/unwinding-uber-s-most-efficient-s...
- Aeolun 5y agoWhile the linked post maybbe right. I completely agree with the Uber engineers that it sounds too complicated. I can understand the double polygon search without thinking about it. I also understand the double polygon search with bounding box optimization, so I’m not sure why that wasn’t used.
- Closi 5y agoIf that’s the case, it’s weird that they would take the time to write a blog post about how great their algorithm is while effectively saying that they didn’t understand the other approaches and that they were too hard.