Remote OK Reviews

Temporal Reviews

Remote OK mentions (141)

• Top 7 Remote Job Boards for Software Engineers (No "Fake Remote" BS)

  Built by indie hacker Pieter Levels, Remote OK is a staple in the digital nomad and tech communities. It has a heavily tech-focused index of jobs. - Source: dev.to / 3 months ago

• Developer Job Boards I Actually Used

  RemoteOK: Known for its "Open Salaries" tag—no more guessing the range. - Source: dev.to / 7 months ago

• Guide to Google Jobs API and Alternatives

  RemoteOK: Focuses on remote jobs across industries, perfect for tracking distributed work trends. - Source: dev.to / over 1 year ago

• Perfectly Qualified Yet Rejected? Here’s Why It Happens and What to Change

  What to Do: Look carefully for any region-specific language in the job posting and, if possible, search the company’s hiring FAQs or career page for more details. Job boards like We Work Remotely and Remote OK often filter jobs by region, which can save you time by showing positions that align with your location. - Source: dev.to / almost 2 years ago

• Just got denied for a junior level role with 8 years of exp

  All I could find is the following links, if it helps: https://larajobs.com/ https://djangogigs.com/ https://djangojobs.net/ https://www.golangprojects.com/ https://remoteok.com/. - Source: Hacker News / over 2 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 / 16 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 / 21 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 2 months 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 / 4 months ago