Workday Reviews

Temporal Reviews

Workday mentions (4)

• How do you apply for jobs and not waste your time?

  Dont apply if they use workday.com. Source: almost 4 years ago

• Workday tenant / community access

  There's a ton of great product information including recorded demos on workday.com. Source: over 4 years ago

• Potential Career Change to Workday from CPA

  If you haven't already, check out workday.com to watch demos of the product. Lots out there to get a conceptual overview and understand the capabilities. Check out job opportunities at Workday, too. While consulting is a great career, there's also other options such as pre-sales and value management (example: helping put together value propositions for prospects wanting to justify Workday), business... Source: almost 5 years ago

• Experience Team Job Offer

  Hey I was recently extended an offer to join the experience team (training starts aug. 2) after 2 video interviews, having completed all tasks within workday.com, and passing Checkr's background check (came back Clear) but I have not received any further instructions on what to do next. Source: almost 5 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 / about 8 hours 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 / 6 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