rayvy

> Wasn't the question about using them for auth, not application state?

Whether a user is auth'd or not can indeed be a form of application state

> It feels dreary because you feel you have nothing left to strive for because you're only measuring your progress by your salary

This.

In your post you mentioned nothing but salary. Sadly I think you might find the hard way that the whole FAANG salary rat-race isn't/wasn't the best choice

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 the elitist (for lack of a better term) attitude of these engineering types at these orgs (think of the poster children of the Valley), this is pretty...lacking. I mean, the part about using the Read/Write lock on the second attempt and instead trying to go with an installed package just screams Node.js, and honestly made me chuckle. I guess Leetcoding and Production Engineering really are different things. I genuinely expected more.

That's cute ;)

P2P is for decentralization. Why would a centralized entity want to implement a decentralized service when they can create a centralized version of that same service faster, easier, and cheaper?

P2P is _hard_ with a capital H.

Your comment is posted as a matter of fact, but includes no sources/citations

This is kind’ve a bait question. I mean the “no duh” answer (as others have already mentioned) is “whichever you are most comfortable with”. I’m confused as to what other answer you could want

Seconded. Would also love to know these things.

Side note: Would definitely change the title as it comes across a bit...baity.

Gonna just chime in and mention Yahoo for Hadoop (yes I know Big Table was Google), and Zookeeper. Great tech started at Yahoo, but they didn’t (unlike today) make too much of a fuss/self-pat-on-the-back about it

Welcome to LA! (Well, when you get here)

Qualifier: been here for about 2.5 years and just got a new position at a startup after 2.5 years at [big_adtech_co]

1. Angelist.co for startups 2. Bultinla.com for startups (though anglelist is better IMO) 3. Startups around here are mainly looking for mid/senior as opposed to junior (in my experience), but obviously there are Jr positions out there 4. Look for recruiters (agencies), to help, plenty of agencies around here hungry for devs (obviously you’ll have to sift through the noise to find the signal here)

5. Avoid leetcode companies..at all costs

Happy hunting

I think you’ve mentioned a HUGE part of the interview process that interviewers forget: you only have 60 mins. 45 mins if you leave time for questions (which you always should). It’s an incredibly difficult task, and deserves significant effort, as opposed to just thinking “oh interviewing is easy”

This is a decent start, but then again remember you only have 60 minutes. And what might seem relatively easy to you, might not be so easy to someone with a time limit (60 mins), and pressure (trying to get a job you want).