Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Bugs are great chances to learn.

What might be fun is figuring out all the ways this bug could have been avoided.

Another way to avoid this problem would have been using a form of “content addressable storage”. For those who are new, this is just a fancy way of saying make sure to store/distribute the hash (ex. Sha256) of what you’re distributing and store it on disk in a way that content can be effectively deduplicated by name.

It’s probably not so easy as to make it a rule, but most of the time, an update download should probably do this



> out all the ways this bug could have been avoided.

The most obvious one is setting up billing alerts.

Past a certain level of complexity, you're often better off focusing on mitigation that trying to avoid every instance of a certain kind of error.


Note that billing alerts protect against unexpected network traffic, not directly against bugs and bad design in the software. Update checking remains a terrible idea.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: