Spooky Stories: Chilling Temporal anti-patterns (part 1)

What this post added

This post details best practices for idempotency and local activities, emphasizing the need for idempotency keys to prevent duplicate side effects, especially with local activities. It also explains Temporal Reset as a 'time travel' mechanism for fixing bugs in production by rewinding and replaying workflows. The post warns about workflow history size limits and suggests using Continue-As-New to manage it. It stresses the importance of deterministic workflows and introduces workflow versioning and patching for safe code updates. Finally, it encourages developers to leverage existing Temporal features like Signals, Queries, and Updates, and to test for determinism.