Mural Reviews

Temporal Reviews

Mural mentions (10)

• Google Ending Support for Jamboard Devices

  Https://mural.co/ Mural has a free tier. I did not used it much but was nice. - Source: Hacker News / almost 3 years ago

• Interview in 3 hours, any tips?

  How you formulate your research questions e.g. Research objective generation workshop and where you store and manage your backlog e.g. mural, miro, excel, uxbacklog. Source: about 3 years ago

• Escape from low maturity

  Transparency of work. Whether youre using https://mural.co for collab analysis, usertesting so people can observe or something as simple as https://uxbacklog.co for a research backlog, giving visibility to the team really helps in building awareness and UR expectation but also gets UR in the pipeline / process. Source: about 3 years ago

• Recommendation for mindmaps

  For instance, mural.co is pretty good. However, it doesnt have the feature I described with which you can colapse knots od your mindmap. Source: over 3 years ago

• What's your favourite tool for the AWS architecture diagrams for the planning (ideating) stages?

  Super early on in the brainstorming stage we'd use something like mural.co for the "ideating" stage and then quickly move to lucidchart for diagrams and early architecture. Source: almost 4 years ago

Temporal mentions (17)

• Temporal in Production: Sharp Edges & Good Practices

  When a team moves from a monolith into microservices and event-driven, asynchronous systems, it inherits a class of problems that used to be someone else's: work that fails halfway through, steps that must not run twice, calls that return before the work is done. Temporal is a durable execution engine that handles a lot of this - you define a multi-step process, and it guarantees the process runs to completion... - Source: dev.to / 2 days ago

• Your Agent Bills While It Waits. Here's the Fix.

  Durable execution — the pattern implemented by Temporal, Inngest, Rivet Actors, and now Cloudflare Workflows — treats waiting as a continuation rather than a loop:. - Source: dev.to / 7 days ago

• Compiler as Custodian

  Two specific moves stand out in Duncan's account. The first is durable execution, via Temporal — Mercury replaced fragile cron-and-database state machines with workflow code whose failure semantics are platform-handled (replay, retry, timeout, cancellation). Mercury open-sourced its hs-temporal-sdk, which wraps Temporal's official Rust Core SDK via FFI and provides a Haskell-native API. The dovetail with Haskell's... - Source: dev.to / about 1 month ago

• How we turned our workflow editor into a real SDK

  We picked Temporal as the first reference engine on purpose. Temporal has the strictest execution model we know of – a V8 sandbox, determinism constraints, replay-driven recovery. If our port contract holds up against that, easier engines – an in-memory test double, a BullMQ queue, or JSON-first platforms like Inngest or Restate – plug in through the same two interfaces. We're shipping Temporal first; the rest is... - Source: dev.to / about 2 months ago

• Three days debugging a missing trace

  The trick is to find whatever metadata channel the queue already gives you and use that and thankfully, almost every mature queue has one (probably because of this scenario). SQS has message attributes, Temporal has context propagators built into the SDK, and Hatchet (which we use to run our workflows) has a metadata field called additionalMetadata. - Source: dev.to / 3 months ago