Monday 30 September 2024
Saturday 28 September 2024
Thursday 26 September 2024
Wednesday 25 September 2024
Tuesday 24 September 2024
Monday 23 September 2024
Friday 20 September 2024
Footage of the tornado in Aldershot was captured on residents' doorbell cameras.
from BBC News https://ift.tt/kDyvltT
from BBC News https://ift.tt/kDyvltT
LATEST NEWS
New top story on Hacker News: Show HN: Inngest 1.0 – Open-source durable workflows on every platform
Show HN: Inngest 1.0 – Open-source durable workflows on every platform
20 by tonyhb | 0 comments on Hacker News.
Hi HN! I’m Tony, one of the co-founders of Inngest ( https://inngest.com/ ) Inngest is an open-source durable workflow platform that works on any cloud. Durable workflows are stateful, long running step functions written in code, which automatically retry on failure. It abstracts everything about queues, event streams and state for you, letting you focus on code. Some examples of uses: managing stateful AI chained step functions; managing search/rag indexes and data pipelines; integrations and webhooks; billing and payment flows. Technical details: unlike other solutions, we put lots of effort into designing our SDK’s step.run APIs to make them extremely easy to use — developer experience is the most important thing for us. We had to design and build our own queueing system to work with multi-tenancy, batching, and debouncing, and we’re iterating on this as we move to FoundationDB. It’s largely all Go in the backend, with a bunch of caching, clickhouse, event streams, and coordination on our behalf. Workers are shared nothing, and run based off of the queue and execution state. We did a post last year as we iterated on our TS SDK. The product has changed a lot since then and wanted to show the community what’s changed as we reach 1.0: * Golang, Java, and Python SDKs with cross-language function invocation (across clouds, too) * Multi-tenant aware flow control (concurrency, throttling, debounce) * Batching, grouping many events into a single function call * Much improved dashboard, with tracing and metrics built in * Advanced recovery tools like function replay, temporary pausing, bulk cancellation (with optional expressions). No more dead letter queues! * Branch deploys built in, with staging env support out of the box * Full local testing with production parity There's a ton on the roadmap, with more launching next week. We’re hiring systems & infra engineers, too — it’s a fun job with lots of challenges! Wanted to say thank you to the HN community for feedback so far! Happy Friday :)
20 by tonyhb | 0 comments on Hacker News.
Hi HN! I’m Tony, one of the co-founders of Inngest ( https://inngest.com/ ) Inngest is an open-source durable workflow platform that works on any cloud. Durable workflows are stateful, long running step functions written in code, which automatically retry on failure. It abstracts everything about queues, event streams and state for you, letting you focus on code. Some examples of uses: managing stateful AI chained step functions; managing search/rag indexes and data pipelines; integrations and webhooks; billing and payment flows. Technical details: unlike other solutions, we put lots of effort into designing our SDK’s step.run APIs to make them extremely easy to use — developer experience is the most important thing for us. We had to design and build our own queueing system to work with multi-tenancy, batching, and debouncing, and we’re iterating on this as we move to FoundationDB. It’s largely all Go in the backend, with a bunch of caching, clickhouse, event streams, and coordination on our behalf. Workers are shared nothing, and run based off of the queue and execution state. We did a post last year as we iterated on our TS SDK. The product has changed a lot since then and wanted to show the community what’s changed as we reach 1.0: * Golang, Java, and Python SDKs with cross-language function invocation (across clouds, too) * Multi-tenant aware flow control (concurrency, throttling, debounce) * Batching, grouping many events into a single function call * Much improved dashboard, with tracing and metrics built in * Advanced recovery tools like function replay, temporary pausing, bulk cancellation (with optional expressions). No more dead letter queues! * Branch deploys built in, with staging env support out of the box * Full local testing with production parity There's a ton on the roadmap, with more launching next week. We’re hiring systems & infra engineers, too — it’s a fun job with lots of challenges! Wanted to say thank you to the HN community for feedback so far! Happy Friday :)
Thursday 19 September 2024
Tuesday 17 September 2024
Monday 16 September 2024
Sunday 15 September 2024
Saturday 14 September 2024
Friday 13 September 2024
Thursday 12 September 2024
Monday 9 September 2024
Ask HN: How do you manage your prompts in ChatGPT?
22 by nabi_nafio | 13 comments on Hacker News.
I use ChatGPT regularly for a lot of different tasks. For example, coding, health Q&A, and summarizing docs. The different prompts stack up in the sidebar which becomes very difficult to manage. For example, I frequently have to refer back to a prompt that I wrote previously. But I usually give up looking for it because of the tedious scroll and search process. I was wondering if there is an easier way. How do you manage your prompts in ChatGPT?
22 by nabi_nafio | 13 comments on Hacker News.
I use ChatGPT regularly for a lot of different tasks. For example, coding, health Q&A, and summarizing docs. The different prompts stack up in the sidebar which becomes very difficult to manage. For example, I frequently have to refer back to a prompt that I wrote previously. But I usually give up looking for it because of the tedious scroll and search process. I was wondering if there is an easier way. How do you manage your prompts in ChatGPT?