That’s really about creating an MVP for a startup, because too many founders stay in a cave trying to make it “perfect” before collecting valuable user feedback.
This does not apply to Cloudflare, especially not for an auth token that needs to be published on your website that cannot be restricted.
That sounds like the product is not finished and should not be released?
"If you are not ashamed by what you are shipping, you are not shipping early enough" (Quoting from memory)
That’s really about creating an MVP for a startup, because too many founders stay in a cave trying to make it “perfect” before collecting valuable user feedback.
This does not apply to Cloudflare, especially not for an auth token that needs to be published on your website that cannot be restricted.
If your engineer tells you that, you're going to have a bad time.
I think you're thinking this:
> If you are not embarrassed by the first version of your product, you've launched too late. -Reid Hoffman
That's a terrible attitude for an infrastructure company. This is what private betas / close iteration with customers is for.
This has been the Cloudflare standard operating procedure for the last year or so. Non stop shipping alpha/beta products.
Otherwise known as vibe code snacking. Vibe out the easy 80% and say the hard 20% is “coming soon tm”
Is it perhaps available behind a flag somewhere?
Then it's not finished?