✳flâneur — a map of the web's best reading

Spooky Stories: Chilling Temporal Anti-Patterns (part 1) | Temporal

temporal.io · 1,558 words · saved by 1 readers

I was excited to present this topic, because my favorite part of my job is helping people learn how to use Temporal, solve their pain points, avoid perilous pitfalls, and just have fun using Temporal to make being a developer easier. Because it's October—the spookiest time of year—I will use some of my favorite spooky movies to explain Temporal best practices and their corresponding anti-patterns in a fun, top 10 list format. If you prefer video/audio format, you can also check out the on-demand version of the original webinar. One of the things we observe at Temporal is developers love to wrap libraries (for example, our SDKs) in other libraries, and then wrap those libraries in other libraries. (Hence, the chance for a mummy pun!) Sometimes, wrapping the Temporal SDKs can be okay. For example, wrapping a thin "shim" layer that allows you to simplify security practices at a company, or make connections to Temporal Cloud easier, or make hooking up to metrics simple for developers. Anot

I was excited to present this topic, because my favorite part of my job is helping people learn how to use Temporal, solve their pain points, avoid perilous pitfalls, and just have fun using Temporal to make being a developer easier. Because it's October—the spookiest time of year—I will use some of my favorite spooky movies to explain Temporal best practices and their corresponding anti-patterns in a fun, top 10 list format. If you prefer video/audio format, you can also check out the on-demand version of the original webinar . 10. Wrapping SDKs in Scary Ways # One of the things we observe at

Explore this link on the map →

related reading