4 ms·
"Quick code fixes" almost always make the problem worse and just cause stress and anxiety. It's always better to simply tackle the root cause and fix that. Unl
by scurvy 11y ago
"Quick code fixes" almost always make the problem worse and just cause stress and anxiety. It's always better to simply tackle the root cause and fix that.
Unless you're disabling a feature, don't push "quick code fixes". You'll pay for it later.
- MichaelGG 11y agoExcept this seems to be counter factual? And the quick fixes were just temporary until the index was finished building. Seems like a perfectly fine thing to do to restore service during an outage, as long as they're rolled back or reviewed later.
- scurvy 11y ago> Seems like a perfectly fine thing to do to restore service during an outage, as long as they're rolled back or reviewed later. Rolling back later seems to forgotten in most cases (unless it's disabling a feature). Then you end up with this weird behavior and code path that few remember. "Oh yeah we did that when...." You usually only rediscover it after that quick hack is a problem. This is decades of experience here.
- mst 11y agoGiven it was temporary and they said it led to the API running "slightly degraded", it sounds like disabling a feature is pretty much exactly what they did.