Today in subtle bugs: forget to await a promise, spread and then stringify it and you'll get an empty object đź‘»
JSON.stringify({ ...new Promise(() => {}) })
'{}'
Thinking of making a Cloudformation custom resource at work. Are we:
- Mad with power
- Pragmatically keeping all config in a template
- Overthinking a bash script?
Frontend: we use the Elm Architecture to reliably manage the complexity of state.
Backend: we use Kafka to reliably manage the complexity of state.
In the middle: LOL shall I retry the fetch request a few times?
Someone somewhere gotta materialise those views. Has anyone tried consuming the ordered events directly from the browser and using idempotency ids to simulate req/rep?
but those change events don't have to be super granular - you de-cache your entire site when you deploy anyway and it's likely that your traffic spikes are to just a few pages