4 ms·
The first two stories are notable in how they reflect the terrible practices of the teller. "Our distributed application produces the same type of error after
by redbad 13y ago
The first two stories are notable in how they reflect the terrible practices of the teller.
"Our distributed application produces the same type of error after the same period of time in totally different data centers. We have no idea why, but moving data centers seems to help, so we just keep doing it. #YOLO"
"We've built a product on a data store and library we don't understand even the highest-level constraints of. That ignorance bit us in the ass at peak load. We patched over the problem and continue gleefully into the future. #YOLO"
These stories should be embarrassing, but they're seemingly being celebrated, or at least laughed about. Am I off base?
- scootklein 13y agoyour first characterization seems incorrect (did you read the story? it wasn't application errors), and your second characterization is hyperbolic at best. calling it a high-level constraint doesn't mean it's common, nor obvious. calling them "terrible practices" is redundant, all devops horror stories can be characterized as exposing terrible practices if you're simply looking at the post-hoc view. it's a feature, not a bug, to make light of them. they're laughed about, but with the intent that they're not made again.