Algorithms you should know before you take system design interviews

Re:Algorithms you should know before you take system design ... by jtchang on Thursday August 11, 2022 @08:23PM (#32433468)

First time I saw geohashing. Can't this result in some lopsided squares? The way it is described has a standard rectangle projection. But those are inaccurate due to the earth being spherical. So the areas on top and bottom will be much larger.

To be fair I've heard of most of these in my career but they are fairly specialized. If you are conducting a system design interview and expecting the candidate to know one of these I'd suspect there is a bit of bias there (unless that is their area of study).

[ Parent | on HN ]

Re:Algorithms you should know before you take system design ... by killingtime74 on Thursday August 11, 2022 @09:00PM (#32433692)

The shape is considered by H3 https://www.uber.com/en-NZ/blog/h3/

[ Parent | on HN ]

Re:Algorithms you should know before you take system design ... by patches11 on Thursday August 11, 2022 @09:01PM (#32433695)

I think in practice you might use something like https://h3geo.org/docs/

[ Parent | on HN ]

Re:Algorithms you should know before you take system design ... by bigbillheck on Thursday August 11, 2022 @08:44PM (#32433588)

> So the areas on top and bottom will be much larger.

Should be fine in practice, not much demand there.

[ Parent | on HN ]

Re:Algorithms you should know before you take system design ... by Someone on Friday August 12, 2022 @03:35AM (#32435582)

I think the argument is that it wastes lots of code space on uninteresting parts of the world, and also has higher resolution there.

For the first, about ⅓ of the world’s population lives in 0110, and about 0 of it in 0000, 0010, 1000 and 1010, combined.

For the second, I would use an area-preserving projection of earth on a square.

[ Parent | on HN ]