Klima Holdings W LLC They're fighting climate change by buying credits and reselling for a profit. They are not a WA energy company that ultimately is mandated to purchase carbon credits to continue operating in WA. Source: about 3 years ago

I read that you wanted to create an App for a gym company. Have you thought about applying for a position at https://klima.com/ ? If I were in your shoes, I would definitely do so. They may be in Berlin but they'll probably be into hiring someone young and passionate for the cause like you are, or keeping you on record. Or, since you asked if KhanAcademy is available in the UK, at least recommend you a British... Source: over 3 years ago

I work for a small startup in Berlin (Klima) and I’ve had very similar conditions in my previous company of a similar size (20-30 people). It’s definitely not the norm here though, so I consider myself lucky to work in these progressive environments. Source: over 4 years ago

Visiting everything in incognito mode has the side effect of being asked each time what I want to do with my cookies. https://klima.com/ is the first website I ever visit that actually manages that properly. - Source: Hacker News / almost 5 years ago

Actually I do personally offset my personal carbon footprint by taxing myself, via Klima: https://klima.com/ However that's not an efficient way for 8 billion people to get out of this problem. - Source: Hacker News / almost 5 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 / 1 day 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 / 7 days 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 1 month 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 / about 2 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 / 3 months ago