3 ms·
Can we please talk about the elephant in the room? There are software engineers, designers, project managers, etc., at Facebook who implemented this bug/featur
by tareqak 6y ago
Can we please talk about the elephant in the room?
There are software engineers, designers, project managers, etc., at Facebook who implemented this bug/feature, right? Given the competitive nature of recruiting and employment at Facebook, this feature was not thrown in by accident, or as a bad joke. This behaviour was implemented as part of a bigger feature, or by itself. It was designed, prioritized, and consciously scheduled for implementation, testing, and deployment. It won against other competing ideas with respect to scheduling, budget, and fulfilling team, departmental, and organizational objective key results (OKRs).
Artifacts that mention this behaviour exist: whether it be in email chains, project-planning and task-management tools like JIRA, commit messages from version control systems like git, deployment logs, and many, many other such things.
Some of those people participate in this forum. Some others no doubt know who they are or who they could be to fair degree of accuracy. Do the rest of us care? Or, do we just point fingers like we are doing now and then go back to hibernating / feigning ignorance until the next time something like this happens again?
- Nextgrid 6y ago> Given the competitive nature of recruiting and employment at Facebook Interviewing at FAANG is about cracking the interview and the tests; it doesn't reflect all the skills that would be relevant in the real world. You can very well be a mediocre engineer but grind Leetcode all day long and eventually pass the interview (and the reverse is also true, a lot of otherwise great engineers wouldn't be able to pass their test), so just because the code is written by FAANG doesn't mean it's bug-free or that the bugs were deemed important enough to be fixed.