TWIL July 24th 2026
- Don't assume prod resources are in the prod AWS account and staging resources are in the staging one
- Turns out both staging & prod S3 buckets for the React app are in the prod account, along with the prod Cloudfront
- But staging Cloudfront is in the staging account, explaining why CI could never find the Cloudfront distro let alone invalidate it
- It's possible to have ~4 hours of meetings in a day and still feel productive
state is meant to be a random, opaque value in OAuth
- It's definitely not meant to be a nested object
- And if it is a nested object, don't re-use the same key for two different things depending on whether it's inital access or a redirect
- Aaand if you're gonna re-use the key, at least name it differently in the rest of the application
- Otherwise you end up with two
continueUrls, both derived from state=url=<value> at different points, which mean entirely different things