LinearB is an engineering productivity platform that provides visibility into developer workflows, automation, and process metrics. It collects data across the entire development lifecycle to diagnose blockers and optimize delivery. One user reports saving 321 developer-hours per month. - Source: dev.to / 3 months ago

Most tools measure half the picture. Traditional metrics platforms like LinearB focus on quantitative signals (DORA metrics, cycle time). Survey platforms like Culture Amp capture sentiment across organizations but aren't developer-specific. DX (founded by DORA/SPACE research creators) combines developer surveys with SDLC analytics. These approaches require deliberate implementation and buy-in. - Source: dev.to / 8 months ago

LinearB is a SaaS solution that retrieves metrics overtime, some of them being used to calculate DORA Metrics. They also have a Youtube channel that advocate for DORA Metrics and more. - Source: dev.to / over 2 years ago

In helping engineering orgs get visibility into developer workflows with LinearB, Dan Lines and Ori Keren discovered that the majority of cycle time was being spent in pull request and code review. They found that:. - Source: dev.to / about 3 years ago

LinearB and there are a few cheaper alternatives. Ties in DORA metrics from gut repos and agile project management tools like JIRA. https://linearb.io. Source: about 3 years ago

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 / 27 days ago

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 / about 1 month ago

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

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 / 3 months ago

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