• 1 Post
  • 33 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle



  • No, this is a general practice-- I see it a lot with third-party vendors who want you to integrate with their services. They’ll expire the documentation portal password after 90 days, but the actual user facing service still accepts the same “password123” that’s been set since 2004.

    I suspect the pattern is to protect the vendors from developer scrutiny: by the time you’ve jumped through enough hoops to read the docs and realize it’s trash, the execs have signed the contracts and the sunk costs are too high to bail out.

    Also add another 6 months to actually get the credentials for the test environment.








  • I think there would be more sympathy if Cloudflare pointed to a specific limit breached and proposed ways to get into compliance at their current price plan.

    “Service XYZ is now consuming 500% of expected quota. Shut it down or we need to get you on a bigger plan.” is actionable and meaningful, and feels a little less like a shakedown.

    I’m sick of “unlimited” services that really mean “there’s a limit but we aren’t going to say what it is.” By that standard, freaking mobile telecoms are far more transparent and good-faith players!

    Perhaps this also represents a failing in Cloudflare’s product matrix. Everyone loves the “contact sales for a bespoke enterprise plan” model, but you should be creating a clear road to it, and faux-unlimited isn’t it. Not everyone needs $random_enterprise_feature, so there’s value in a disclosed quota and pay-as-you-scale approach: the customer should be eager to reach out to your sales team because the enterprise plan should offer better value than off-the-rack options at high scale.