The pithy response here is: “It is a poor craftsman who blames his tools.”
That’s not the full reality here, and I understand, my lead in is just the joke response. My actual response is that I appreciate Stripe’s disclosure here (as a Stripe customer especially) and I think this is a good indicator of performance as a business if not as an uptime indicator. I’ll take a better business over a better uptime for most things, including this, and I presume it leads to better uptimes down the load with better service elsewhere the entire way (or so I hope). I’d also hope they are going to be drastically changing their worflow’s reliance on tools to indicate all things here and bring some better documentation to get context for such changes in the future.
I guess we’ll have to wait til part two, but a dashboard that “surfaces” database operations out of order seems like quite the WTF.
The pithy response here is: “It is a poor craftsman who blames his tools.”
That’s not the full reality here, and I understand, my lead in is just the joke response. My actual response is that I appreciate Stripe’s disclosure here (as a Stripe customer especially) and I think this is a good indicator of performance as a business if not as an uptime indicator. I’ll take a better business over a better uptime for most things, including this, and I presume it leads to better uptimes down the load with better service elsewhere the entire way (or so I hope). I’d also hope they are going to be drastically changing their worflow’s reliance on tools to indicate all things here and bring some better documentation to get context for such changes in the future.