[HN Gopher] Algorithms you should know before you take system de...
       ___________________________________________________________________
        
       Algorithms you should know before you take system design interviews
        
       Author : code007
       Score  : 103 points
       Date   : 2022-08-11 18:02 UTC (4 hours ago)
        
 (HTM) web link (blog.bytebytego.com)
 (TXT) w3m dump (blog.bytebytego.com)
        
       | cosmotic wrote:
       | If knowing these gets you the job and it can be crammed for,
       | that's not an effective interview.
        
         | jahewson wrote:
         | It's effective at ruling out people who haven't even heard of
         | any of them. Though I can't imagine really expecting people to
         | know more than three or four of these, certainly not in detail.
        
         | bufferoverflow wrote:
         | You're confusing sufficient vs necessary.
         | 
         | Knowing them is probably necessary, but knowing them alone is
         | very unlikely to land you a job.
        
       | FabHK wrote:
       | Several interesting algorithms, but why a picture of a table
       | instead of a table?
        
         | noughtme wrote:
         | Because Substack. Same thing with Medium articles. Never used
         | either of these platforms, but surely they allow custom HTML?
        
         | wollsmoth wrote:
         | Yeah I can look these up no problem but links to articles would
         | have been rad.
        
           | lopatin wrote:
           | Did you try scrolling down to the links?
        
         | mandeepj wrote:
         | > but why a picture of a table instead of a table?
         | 
         | I guess they drawn the whole thing in an image editing tool and
         | exported it as one image. A Table would've required much more
         | effort, multiples images, styling, placement and many web
         | requests to load them.
        
       | fendy3002 wrote:
       | Having done several system design interviews, most of the time
       | they're badly executed. When I asked for some detailed
       | requirements they cannot disclosure them. However in the end they
       | have those hidden requirements and I've failed because my system
       | doesn't meet those requirements.
       | 
       | It's a bad way to conduct a system design interview by having a
       | design in mind and hoping the candidates will reach that with
       | limited knowledge / guidance.
        
       | ricardbejarano wrote:
       | 1. Round-robin
       | 
       | That's all.
        
         | syspec wrote:
         | Please expand, it sounds interesting
        
           | goldenkey wrote:
           | Red Robin, crab law. Hire me or I'll sue!
        
       | notyourwork wrote:
       | TIL that rsync is an algorithm, not just a program that makes it
       | easy to sync content across hosts.
        
       | time0ut wrote:
       | I was expecting to see idempotent consumer, circuit breaker, and
       | a few others that I've used frequently when designing systems.
       | Maybe not interesting enough to make the list?
        
       | madelyn wrote:
       | I feel that if more interviews involved this sort of algorithm
       | instead of the ultra-niche / only situationally useful, there
       | would be way less opposition and much more signal.
       | 
       | At work, I have written and then used a bunch of these in
       | production, just for the narrow scope of things I work on. Might
       | be indicative of me being in a bubble though.
       | 
       | Please, ask me to make a bloom filter or show how consistent
       | hashing enables sharding! I'll pass on yet another "Implement
       | String.reverse()"
        
       | [deleted]
        
       ___________________________________________________________________
       (page generated 2022-08-11 23:00 UTC)