←back to thread

461 points thunderbong | 1 comments | | HN request time: 0.21s | source
Show context
modernerd ◴[] No.42134059[source]
"Billing alerts" are a joke, give us hard spend limits. Then offer a way to set those limits during onboarding.

Building a business on blank cheques and accidental spends is shady. It's also a large barrier to adoption. The more times devs see reports like, "I tried [random 20-minute tutorial] and woke up to a bill for my life's savings and luckily support waived the fee this one time but next time they're coming for my house", the less they'll want to explore your offerings.

replies(20): >>42134131 #>>42134150 #>>42134268 #>>42134271 #>>42134282 #>>42134287 #>>42134291 #>>42134375 #>>42134462 #>>42134469 #>>42134517 #>>42134613 #>>42134695 #>>42134828 #>>42135170 #>>42135288 #>>42135373 #>>42135557 #>>42135706 #>>42136718 #
exhilaration ◴[] No.42135373[source]
It's been mentioned several time in HN comments that the AWS billing code is a giant pile of spaghetti and there is generally a lot of fear around making big changes to it.

That's been one of the more interesting inside baseball facts I've learned here.

replies(4): >>42135536 #>>42135631 #>>42136220 #>>42136557 #
fallingsquirrel ◴[] No.42136220[source]
And yet somehow every time they launch a new product they have no problem adding it to their billing code.
replies(1): >>42138292 #
1. jkman ◴[] No.42138292[source]
I mean, adding some shotgun changes to a messy codebase is always significantly easier than refactoring the whole.