When I Work Reviews

Temporal Reviews

When I Work mentions (6)

• Employee calendars that all super admins have access to

  How are the users accessing these calendars if you don't create accounts for them? What you probably want is a work scheduling service like when I work: https://wheniwork.com. Source: over 3 years ago

• Volunteer schedule with varying hours

  You could try something like this: https://wheniwork.com. Source: almost 4 years ago

• Labour as a percentage of sales.

  I record all of our takings through a spreadsheet and from this I add our takings into wheniwork.com and get my labour as a percentage of sales. Source: almost 5 years ago

• Web-Based Time Keeping System Suggestions

  Look at wheniwork.com. We used them a few years ago and they had lots of features. Source: almost 5 years ago

• Web/App-based Time Tracking Application for Lab use

  We are going to resume our work in few weeks and looking for efficient time tracking applications to keep track of the people working in the lab at any given time. In one lab I am using WhenIWork app and planning to us clockify in the second lab. Both of them are free and have some pros and cons. I was wondering if anybody has experience using any other software (free) in your lab. We are a team of 5-6 people and... Source: about 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 / 5 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 / 10 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 / 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