Gentle reminder to anyone reading this that your problems are probably not FAANG problems. If you architect your system trying to solve problems you don't have, you are gonna have a bad time.
"And note that you don’t even have to be at FAANG scale to run into this problem - even if you have a small inventory (say few thousand items) and a few dozen features, you’d still run into this problem. "
Wow, this is something that has been a floater-in-mind for decades ;
I'll top it off with an interview at Twitter with the Eng MGR ~2009-ish?
--
Him: So tell me how you would do things differnetly here at twitter based n your experience?
ME: "Well, I have no idea what your internal processes are, or architecture, or problems, so my previous experience wouldn't be relevant."
I'd go for the best option that suits goals.
[This was my literal response to the question, which I thought was a trap but responded honestly -- as a previous mgr of teams, the "well, we did it at my last company as such"]
Dont reply this way. <--
Here was his statement:
This is a literal quote from a hiring manager for DevOps/Engineering at Twitter:
"Thank god!, We have hired so many people from FB, where that was there only job out of school, and no other experience, and the biggest thing they told me was "well - the way we did this at FB was... X"
--
His biggest concern was engineering-culture-creep...
> Wow, this is something that has been a floater-in-mind for decades
Have you literally never come across the "you're not Google!!!" trope before now, during the whole ~decade leading up to this very day? Gosh I envy you.
(Also, I am reaaally struggling to understand that story. Who is speaking? It sounds like a story within a story within a story. I can just about piece together the gist, but I'm very confused by all the formatting and nested quotes.)
Wow. That amazes me that anyone would answer that question without knowing anything about the problem space and implemented solutions.
Wait, I got it, I would rewrite everything as AWS Lambdas. That's the right answer! Screw your (almost certainly SQL) DB, let's move it all to DynamoDB too.
jeffbee|3 years ago
-TFA
vikingcaffiene|3 years ago
samstave|3 years ago
I'll top it off with an interview at Twitter with the Eng MGR ~2009-ish?
--
Him: So tell me how you would do things differnetly here at twitter based n your experience?
ME: "Well, I have no idea what your internal processes are, or architecture, or problems, so my previous experience wouldn't be relevant."
I'd go for the best option that suits goals.
[This was my literal response to the question, which I thought was a trap but responded honestly -- as a previous mgr of teams, the "well, we did it at my last company as such"]
Dont reply this way. <--
Here was his statement:
This is a literal quote from a hiring manager for DevOps/Engineering at Twitter:
"Thank god!, We have hired so many people from FB, where that was there only job out of school, and no other experience, and the biggest thing they told me was "well - the way we did this at FB was... X"
--
His biggest concern was engineering-culture-creep...
samhw|3 years ago
Have you literally never come across the "you're not Google!!!" trope before now, during the whole ~decade leading up to this very day? Gosh I envy you.
(Also, I am reaaally struggling to understand that story. Who is speaking? It sounds like a story within a story within a story. I can just about piece together the gist, but I'm very confused by all the formatting and nested quotes.)
HWR_14|3 years ago
Wait, I got it, I would rewrite everything as AWS Lambdas. That's the right answer! Screw your (almost certainly SQL) DB, let's move it all to DynamoDB too.
unknown|3 years ago
[deleted]