Job interview: “algorithms”
Reality: “Turn a 127 message deep slack thread between 5 engineers into a decision”
- This is the best take so far on the Netflix buffering drama.
- MSFT stock grants New hire: can’t code. has 30k twitter followers. $800k over 4 years. Current eng: finds 500ms backdoor, saves world. $67k retention grant, vests over 5 years.
- Why won't this CSS change?! Restart server >Nope rm -rf everything >Nope rebuild dev env >Nope Oh wait, I was looking at production
- Duplicated string in some code. New developer: "Approved." Mid-experienced developer: "This violates DRY and should be extracted to a constant." Experienced developer: "Approved."
- Asked the front desk guy if people have a hard time quitting this gym once they join.
- The interview: leetcode and big-O The job: turning a 145 reply slack thread into a decision
- San Francisco lol. Just saw these 2 cruise cars (self driving) stopped/confused at an intersection. Person behind is honking + screaming “learn to drive!!”
- I have 14 months of experience. 9 months at FAANG. When applying to startups, would I be a principal SWE or director of engineering?
- Clicks "contact us" button Oh no. It's a mailto: Apple Mail is opening "Syncing 14,321 emails" No, no, no, no, nooooo
- This Post is from an account that no longer exists. Learn more
- He’s a 10 but he always uses a uuid for his database primary key
- According to twitter: - Rails is dead, fat and slow - Next js is the future, fast and efficient According to my laptop dev env: - rails api - 255mb ram - next js frontend - 2.6gb ram
