3 ms·
You're presumably used to operating in an enterprise environment with O(1000) customers and O(10) developers, not a consumer environment with O(100M) customers
by nostrademons 7y ago
You're presumably used to operating in an enterprise environment with O(1000) customers and O(10) developers, not a consumer environment with O(100M) customers and O(1000) developers.
Reliability issues at large consumer tech companies will usually be caught by the QA/canary/SRE process. If they're not, you'll hear about them soon enough with 100M users banging on the product, and then just do a rollback and fix it on a more leisurely pace. Consumer expectations in non-tech industries have gotten so low that you can burn down whole towns, poison people, and leak millions of records of personal data with few consequences to the company; not being able to access your favorite video for 15 minutes is comparatively minor.
Also, the type of changes in market conditions consumer companies face are usually not those you can architect around. They include things like "We are no longer shipping DVDs to customers; we are streaming content online", "We no longer write web software, we're a mobile-first company", and "our business model is no longer selling personal data, it's payments". There is no architectural fix for "your product is canceled".
- JohnFen 7y ago> You're presumably used to operating in an enterprise environment with O(1000) customers and O(10) developers, not a consumer environment with O(100M) customers and O(1000) developers. I have a great deal of experience with both environments.
- user5994461 7y agoI have no idea what you're trying to say. O(1) and O(1000000) are the same thing, the O() notation ignores the constant factor.