3 ms·
This broke our production app last week. The only solution was to move our CSVs off of Sheets completely.
by brundolf 6y ago
This broke our production app last week. The only solution was to move our CSVs off of Sheets completely.
- crazygringo 6y agoWhy? Couldn't you have just set them to public view access? Seems like it would have been a drastically simpler change.
- brundolf 6y agoWe didn't know about that workaround at the time, we just needed to get our app back online.
- brudgers 6y agoRemoving an external dependency on Google is a sound engineering choice for many use cases (and maybe not for others). One reason it might a sound engineering choice is what happened here. Sure moving off Google is work. So is implementing the work around. Breaking changes always either require work or make user code obsolete. Breaking changes generate work for users. They externalize the cost of making changes non-breaking to end users.
- brundolf 6y agoFortunately it was a transition we'd already talked about making; we were approaching that threshold where the agility/reliability tradeoff was about to flip. But still, it sucked having a few hours of unexpected downtime while we scrambled to make the change.
- djtriptych 6y agoOR a CI step using the docs CLI?