> Am I the only person who thinks this whole approach is broken? Broken? Depends on your perspective. If you care first and foremost about your users' data, i

> Am I the only person who thinks this whole approach is broken? Broken? Depends on your perspective. If you care first and foremost about your users' data, it sure is broken. But FB is not a hosting company. If you care the most most about correctness of your code and getting everything right the first time (VMS style rather than UNIX `worse is better' style), then again, it will seem broken. But FB is not an academic excercise. If, on the other hand, you felt like a stakeholder in the company and cared most about developing the business, then no, `moving fast and breaking things' is means to that end. If, alternatively, you enjoy experimentation and pushing frontiers, then again, no, `moving fast and breaking things' is about the only modus operandi that can accomodate that. Emphasis on product management and testing is for serving your customers -- but users aren't FB's customers. I cannot assure you, but I would bet a lot FB does indeed heavily test and manage projects related to serving ads -- which is what their customers pay for.