Have you heard about our upcoming Hackathon? 👀 Join us at #Replay2023 and our first-ever Hackathon in Seattle. Test your skills building applications with Temporal, and show us what you can do! Find more details on the event and how you can join here 👉 https://t.co/oOQEMmbk8n

We're hosting a hackathon before our Replay conference September 11th! With lots of use cases for Temporal, what do you choose? What about a reimagining of an ecommerce platform, with a Workflow per customer and a Workflow per order? Learn more here:

Donut you want to start your day off right? Check out @bouncingsheep's post on compensating actions, a saga design pattern story. 🥣 🍳🍩 https://t.co/ToiglstOT7

I'm officially looking for the next thing. If you know of any opportunities along the lines of #DevRel #TechnicalProjectManagement #Consulting #Communications, I'm listening. https://t.co/NJovcwxDim RT For Reach, Please?

For the next hour, ask us anything about the TypeScript SDK or our new TypeScript 101 course! Tweet your question with the #TemporalAMA hashtag, and we’ll reply 👀

Some folks from our team are going to be answering YOUR questions about Python and Temporal soon! #TemporalAMA

Be sure to join us for the inaugural #TemporalAMA this afternoon where we'll answer questions surrounding the newly GA'd #Python SDK

Sources close to me have informed me that "Reply" is not a conference (or at least not this one). Replay is the correct autocorrect correction. :)

One thing to emphasize: New or new-ish speakers are VERY WELCOME to submit something as well. I and others on the DevRel team will be around to help you have a great speaking experience!

Whether you know Temporal or not, there's a good chance you know something about backend development. So check it out: Our 2nd annual Reply conference is soliciting talks of all sorts! We'd of course love to hear how you're using Temporal, but plenty of other topics, too!

* Software exists outside of the “tech industry” too. Plenty of meaningful places outside the “normal” sphere. * Downturns suck. It’s gonna be hard. You’re probably feeling sad, angry, unvalued. Those and all the rest are valid feelings. Remember: you ARE valued.

I did a little impromptu (hopefully) motivational but at the beginning of class today, in response to tech layoffs. The main messages: * Your worth as a human is not your job. You are valued and matter all on your own. * Big Tech is not the sole destination for software jobs.

We're not the only ones, of course, but @temporalio is hiring. Check out the DA role, DM if you want to chat.

❤️s out to all the recent layoffs. Lots of former colleagues hit by them, and sad to see so many lovely people affected. I'm always happy to chat and listen with whoever needs it. ❤️

With billionaires backing effective altruism pouring significant funds into AI work, “it is not surprising that the field has been moving in a direction promising an ‘unimaginably great future’ … while proliferating products harming marginalized groups.”

If you're in NYC this Wednesday, Nov. 30 stop by and see us! Our meetup talking all things Temporal, DataDog, and Go starts at 6pm EST...don't forget to stick around for the raffle!

If you're in the NYC area, come join us at the golang meetup next Wednesday! I'll be there, to give a talk on @temporalio !

So are "flaky tests" and "nondeterminism" one and the same? Like flaky tests themselves.... Sometimes. 😉

But if a Workflow is started with 2 and 2, it ought to call the `AddNumbers` activity every time and return 4 at the end. This Workflow would be deterministic even though AddNumbers depends on a flaky service. The activity failing or not is a different question/test.

In @temporalio, we have a similar idea: Workflows must be deterministic. That doesn't mean dependent things can't fail. We expect that to happen.