3 ms·
One of the biggest problems with development at FB, Twitter, Google, etc is that frontend engineers may not know "serious CS" and/or have some distributed syste
by fizx 16y ago
One of the biggest problems with development at FB, Twitter, Google, etc is that frontend engineers may not know "serious CS" and/or have some distributed systems "common sense."
It's remarkably easy for an apparently simple commit to dramatically increase load on some backend server, causing site stability issues and/or cost increases.
Your big-name media company probably doesn't care as much about getting every last penny out of its hardware, and its users probably aren't growing at a breakneck pace.
The questions you mentioned were designed to test if you know basic math and CS. If you don't know binary search, you probably also don't know asymptotic complexity, which means there's a chance you'll sneak in an O(n3) (expensive) loop in your javascript somewhere.
- geuis 16y agoAnd this is exactly the problem I am describing. If the position is for someone who is only going to write js, then I agree. Those are important questions. But then that is for an engineering position who writes in js, not a frontend engineer. If you want a good example of what happens when strict CS people write javascript without thought or knowledge of frontend best practices, look at YUI. Ugh. So my argument boils down to making a clear distinction between a programmer and s frontend engineer. You describe the first, I the latter.