Comment on: We have proof automation now
[..] it's expensive to spend that much time thinking through it all, when users are largely trained to just accept crashes, glitches, inconsistencies, and the occasional sprinkle of data loss.Indeed.
Comment on: When "letting it crash" is not enough
I feel like this approach might still pose some challenges or issues with regards to time or stale data. A couple of problematic scenarios:- Application requests a JWT token. It then crashes and gets restarted. It gets past the problematic point, but later when trying to make a request, it crashes due to the cached token being expired.- Application interacts with the current time in a meaningful manner. Due to the log replay, it will always live in the past and when switching from the cache-sourced time to the current time, some issues might occur, like deltas being larger than expected- Appli
Comment on: Show HN: Canine – A Heroku alternative built on Kubernetes
I hesitate to call it an anti-pattern but it kind of is. It leads you down some bad paths.- In the best possible scenario: 1) you're spending time to duplicate configuration between dev, test, and prod, any time the environments change, 2) you hope your testing in one environment is actually borne out in prod, 3) you are shutting down dev & test when they're not in use (to save money), 4) you rebuild it all regularly to ensure it's still actually repeatable to repair or rebuild it, 5) you do maintenance on all 3 regularly to stay up to date on security patches and dependencies, 6) you stil