Thread

1. stairlane · 1789575338 · focus · HN ↗

   These metrics tend to be bullshit in contracts.

   For example we had a 6 9 (99.9999%) requirement from a customer for any given 3-6 month period. If we violated that, we owed them their money back (baring the outage wasn’t caused by us - I.e our cloud provider shit the bed).

   That’s something like 7.5 seconds. For a contract over $1.5M. Am I the only one who thinks that’s outrageous expectations?

   EDIT: The web app was for generating SBOMs of static assets.

   1. ahtihn · 1789575749 · focus · HN ↗

      It's a contract, you're free to negotiate?

      If you agree to those terms knowing it's unrealistic, you're agreeing to give away your service for free.

      1. swiftcoder · 1789575870 · focus · HN ↗

         > It's a contract, you're free to negotiate?

         Well, someone on the business side of the house is free to negotiate. Whether engineering learns about the contract before sales has inked a 6-nines availability guarantee varies wildly by the company

         1. ahtihn · 1789592899 · focus · HN ↗

            That's a common issue in orgs where sales are incentivized based on size of contract without regard for the profitability of the contract.

            See also: selling features that don't exist and cost more to implement and maintain than the contract is worth.

Unofficial Hacker News client; not affiliated with Y Combinator.