4 ms·
Because world is full of bullshiters who know enough buzzwords and buzzsentences and interview time is too short. On lower levels leetcode style stuff gives mo
by galkk 3y ago
Because world is full of bullshiters who know enough buzzwords and buzzsentences and interview time is too short.
On lower levels leetcode style stuff gives more quantifiable signals per minute/session.
Plus, do you really want to fully explain something like paxos or raft in interview context?
My personal pet peeves are
1. “event sourcing” and derivatives. It really attracts people who love to talk but never built anything large using it
2. Adepts of uncle martin
- flaminHotSpeedo 3y agoIf you can't differentiate buzzwords from signals you shouldn't be interviewing. Plus how do you expect to get good signals from a leetcode whiteboard interview for someone who spends most of their time designing systems and only writes code when it gets to the point where it's faster and less frustrating to pair program vs explaining what needs to get implemented? To clarify, I don't have a good answer: I still participate in leetcode style interviews (though system design is another component) - but although I sing the song and can't come up with anything better, I don't think it's the best way to go
- mrkeen 3y agoRaft is for event sourcing.