71–80 of 124 posts
Earlier quoted context omitted.
clearly the most efficient solution is to pontificate about other people's implementations while never having done anything of the sort at that scale yourself.
While he was a bit rude I wouldnt assume he hasn't built something at this sort of scale.
This is a very inefficient implementation. Really, just poor quality work overall, as anyone with even a basic understanding of spatial indexing would know that an R-tree would be many times faster, as illustrated here: https://medium.com/@buckhx/unwinding-uber-s-most-efficient-s...
This is a very inefficient implementation. Really, just poor quality work overall, as anyone with even a basic understanding of spatial indexing would know that an R-tree would be many times faster, as illustrated here: https://medium.com/@buckhx/unwinding-uber-s-most-efficient-s...
It's funny because had you tried to brute force any of their interview questions (spatial or not) it would have been instant rejection. Often feels like algo analysis is an exercise to get a job and not something engineers actually do, even when required.
Earlier quoted context omitted.
While he was a bit rude I wouldnt assume he hasn't built something at this sort of scale.
nah i think its a pretty fair assumption
This is a very inefficient implementation. Really, just poor quality work overall, as anyone with even a basic understanding of spatial indexing would know that an R-tree would be many times faster, as illustrated here: https://medium.com/@buckhx/unwinding-uber-s-most-efficient-s...
I'm currently implementing an rtree in elm. Does anyone have good references about rtrees that they like?
I think this write up is very fair for a solid engineering team. Is it groundbreaking and eye opening? Absolutely not, I’d say the most “hmm I didn’t know that” part of the entire thing was the part about R-Trees and S2. Is that bad? Absolutely not. These guys did the work, logged their performance and are sharing their story. However, and I believe this is where the animosity in the comments is coming from - given t…
> I guess Leetcoding and Production Engineering really are different things. This is key point. They delivered value to the business. That's the only thing that matters.
Earlier quoted context omitted.
> I guess Leetcoding and Production Engineering really are different things. This is key point. They delivered value to the business. That's the only thing that matters.
> They delivered value to the business. That's the only thing that matters. But this bit isn't true during the interview process.
Earlier quoted context omitted.
clearly the most efficient solution is to pontificate about other people's implementations while never having done anything of the sort at that scale yourself.
While he was a bit rude I wouldnt assume he hasn't built something at this sort of scale.
Earlier quoted context omitted.
They also would have to sift through some really terrible programmers who have fully bought into the worst practices of enterprise-y OO development.
Is that really true? Honest question. Or is that just bias against things that are not new and fancy?