Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
abelanger
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
Building a TUI is easy now
(hatchet.run)
306 points
by
abelanger
8mo ago
|
255 comments
32.
▲
Postgres Indexes, Partitioning and LWLock:LockManager Scalability
(ardentperf.com)
2 points
by
abelanger
8mo ago
|
0 comments
33.
▲
Claude Code Psychosis
(jasmi.news)
2 points
by
abelanger
8mo ago
|
1 comments
34.
▲
Stripe's New Homepage
(stripe.com)
2 points
by
abelanger
8mo ago
|
2 comments
35.
▲
by
abelanger
8mo ago
https://archive.ph/GbVrJ
36.
▲
The Devastating Decline of a Brilliant Young Coder (2020)
(wired.com)
1 points
by
abelanger
8mo ago
|
3 comments
37.
▲
Reflecting on two years as an open-source startup
(hatchet.run)
1 points
by
abelanger
9mo ago
|
0 comments
38.
▲
by
abelanger
9mo ago
Sounds like the CodeRabbit controversy: https://xcancel.com/harjotsgill/status/2004050004785484172
39.
▲
Reflecting on two years as an open-source startup
(hatchet.run)
5 points
by
abelanger
9mo ago
|
0 comments
40.
▲
by
abelanger
9mo ago
Drawing the boundary at high throughput, huge fan-out and ultra-low-latency is correct - I'd also add that MQs are often used for pub/sub and signaling. MQs are heavily optimized for reducing E2E latency between publishers and con
41.
▲
by
abelanger
9mo ago
Not harmful for now - "fork from checkpoint" would be perfectly fine for me at the moment. The main issue (as flagged in the post) is that setting up additional tooling can take a while! In the longer term, docker is nice from a r
42.
▲
by
abelanger
9mo ago
This is seriously cool - it's exactly the DX and API I've been waiting for from sandboxed execution providers. I'd love to be able to configure the base image/VM in a way that doesn't bundle coding tools or anything
43.
▲
Designing SDKs that developers love
(hatchet.run)
2 points
by
abelanger
9mo ago
|
0 comments
44.
▲
Strange.website
(strange.website)
220 points
by
abelanger
9mo ago
|
70 comments
45.
▲
by
abelanger
9mo ago
Yep! Feel free to email me at alexander [at] hatchet [dot] run
46.
▲
by
abelanger
9mo ago
Oh no, haven't gotten reports about the website being slow, thanks for flagging! Which browser are you using? Regarding Temporal, our goal is to create the best developer experience possible, and we started Hatchet because we felt that
47.
▲
How to Be a Genius Editor (Of Literal Words)
(genius.com)
4 points
by
abelanger
9mo ago
|
0 comments
48.
▲
by
abelanger
9mo ago
Hatchet | Founding Engineer | NYC or REMOTE (US and EU) | https://hatchet.run Hey HN! I'm Alexander, one of the founders of Hatchet. Hatchet is an open-source platform for running background jobs at scale. We're hiring
49.
▲
Concurrency's Shysters (2008)
(bcantrill.dtrace.org)
4 points
by
abelanger
9mo ago
|
0 comments
50.
▲
Do Parents Have Favorite Children? Of Course They Do
(nytimes.com)
3 points
by
abelanger
9mo ago
|
0 comments
51.
▲
by
abelanger
10mo ago
I mentioned this towards the bottom of the post, but to reiterate: we're extremely grateful to Laurenz for helping us out here, and his post on this is more than worth checking out: https://www.cybertec-postgresql.com/e
52.
▲
by
abelanger
10mo ago
FWIW, I think the memory snapshotting idea isn't going to work for most stacks for a few different reasons, but to speak more broadly on API design for durable execution systems, I agree completely. One of the issues with Temporal and
53.
▲
by
abelanger
10mo ago
Sure, I'll bite. Task-level idempotency is not the problem that durable execution platforms are solving. The core problem is the complexity that arises when one part of your async job becomes distributed: the two common ones are distri
54.
▲
by
abelanger
10mo ago
The "constraining functions to only be durable" idea is really interesting to me and would solve the main gotcha of the article. It'd be an interesting experiment to take memory snapshots after each step in a workflow, which
55.
▲
by
abelanger
10mo ago
Hah, well I'll avoid _talking to_ vendors, more specifically I'll avoid talking to salespeople selling a technical product until we're pretty deep in the product. I do tend to not use vendors that don't have a good self-
56.
▲
The pitfalls of partitioning Postgres yourself
(hatchet.run)
93 points
by
abelanger
10mo ago
|
6 comments
57.
▲
How to think about durable execution
(hatchet.run)
96 points
by
abelanger
10mo ago
|
37 comments
58.
▲
The levers of political persuasion with conversational artificial intelligence
(science.org)
1 points
by
abelanger
10mo ago
|
0 comments
59.
▲
by
abelanger
11mo ago
If anyone needs commands for turning off the CF proxy for their domains and happens to have a Cloudflare API token. First you can grab the zone ID via: curl -X GET "https://api.cloudflare.com/client/v4/zo
60.
▲
by
abelanger
11mo ago
Hatchet ( https://hatchet.run ) | New York City (IN-PERSON | REMOTE) | Full-time We're hiring for a number of engineering positions to help us with development on our open-source, distributed task queue: https://gi
More ›