4 ms·
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 ch
by exhilaration 2y ago
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.
- bryancoxwell 2y agoWell done AWS for finding a way to make your technical debt cost other people money.
- rolandog 2y agoCompletely agree. Having worked previously for ... (humans?) ... I can authoritatively theorize it would be fixed in a jiffy if it weren't making them bucketloads of money. To make my case: just ponder the opposite: "What would an honest version of AWS do?". They would address the concerns publicly, document their progress towards fixing the issue, and even try to determine who was overcharged due to their faulty code, and offer them some compensation. "We're too big to fix our own code" is, sadly, taken from the MS playbook (IIRC, something like that was made public after the breach of MS manager mailboxes after the whole Azure breach fiasco that was discovered by, IIRC, the DOJ that paid to have access to logs).
- fallingsquirrel 2y agoAnd yet somehow every time they launch a new product they have no problem adding it to their billing code.
- jkman 2y agoI mean, adding some shotgun changes to a messy codebase is always significantly easier than refactoring the whole.
- pvillano 2y agoIf there was a lawsuit, change in regulation, request from an enterprise customer, or doing so MADE THEM MORE MONEY it would be fixed in a week.