Joe Haddad @timer150

infra @vercel github.com/timer Hinckley, Ohio Joined June 2010

Tweets

375
Followers

6K
Following

595
Likes

1K

Joe Haddad @timer150

3 months ago

@consolelogwill @rauchg @CaseyGowrie You could leverage Queues to roll resumable streams, a few of our internal demos actually do this. Have you seen github.com/vercel/resumab…?

1 0 0 73 0

View Details

Joe Haddad @timer150

3 months ago

@neoromantic @rauchg @CaseyGowrie We are going to continue investment into the Workflow SDK! cc @pranaygp

1 0 1 80 0

View Details

Joe Haddad @timer150

3 months ago

@tobiastornros @rauchg @CaseyGowrie Yes! You can o11y in your project's o11y tab. We'll update the docs for this!

1 0 1 51 1

View Details

Joe Haddad @timer150

3 months ago

@marclou @rauchg Let us know what we can improve! Looking forward to feedback 😁

0 0 0 40 0

View Details

@BenjDicken @rauchg It is hard for me to imagine maintaining Vercel’s DX for arbitrary compute where we do not have an event binding interface. What does this look like to you? 👀 Have you looked at Sandbox for your use case? Can you share the specific type of work you want to do in this VPS?

0 0 2 127 0

View Details

Joe Haddad @timer150

3 months ago

Is indefinitely actually desirable here? For long running tasks, we typically see someone implement checkpointing so that a transient failure (e.g. upstream API) does not cause you to lose all progress. This can generalize to Queues or Workflow where a task might take 8 hours, but you carve it up into 10 minute chunks. I would love to learn more specifics!

1 0 1 400 0

View Details

Joe Haddad @timer150

6 months ago

@k_firsov @cramforce @rauchg Mind sharing more details (here or in DM)?

1 0 1 157 0

View Details

Joe Haddad @timer150

9 months ago

@maxleiter Do you have thoughts on srcml.org?

1 0 0 145 0

View Details

Joe Haddad @timer150

9 months ago

@mxkaske Sent you a PR to replace your middleware with routes instead! This will guarantee your site is always fast github.com/mxkaske/mxkask…

1 0 1 54 0

View Details

Joe Haddad @timer150

10 months ago

@karthikkalyan90 very aligned- nothing’s worse than a ton of nits!

0 0 1 67 0

View Details

Joe Haddad @timer150

10 months ago

I would switch to a new AI code review tool tomorrow if it _______. We'll build the best ideas and give you early access!

4 0 17 3K 1

View Details

Joe Haddad @timer150

10 months ago

@huozhi I can imagine many layers to this, for starters the bot should auto resolve comments it previously found and are now fixed. Automated approvals sound great if it can follow a repo policy (only for docs, bug fixes that do not introduce new features, etc)!

0 0 1 131 0

View Details

Joe Haddad @timer150

10 months ago

@hp_arora 🎙️ we're waiting

1 0 0 138 0

View Details

Joe Haddad @timer150

10 months ago

@dobroslav_dev @vercel_changes @elysiaJS @anthonysheww think we can get this working? We have our bun builder that could be used automatically: github.com/vercel-communi…

0 0 1 66 0

View Details

Joe Haddad @timer150

10 months ago

@preetsuthar17 @vercel what is the first feature you’d ship?

2 0 2 443 0

View Details

Joe Haddad @timer150

11 months ago

@ScriptedAlchemy @rauchg @kdy1dev @tomlienard Real Rust with Active CPU pricing. vercel.com/blog/introduci…

1 0 1 201 0

View Details

Joe Haddad @timer150

11 months ago

@Tofugrass @vercel_changes All plans, including Hobby (free)

0 0 2 38 0

View Details

Joe Haddad @timer150

11 months ago

@WebReflection @rauchg @tomasz_ducin @WebReflection I think we're talking past one another - the receive handler in initial tweet handles the entire lifecycle of message handling. Without a callback, you'd need: const { message, ack, reject, extend } = await receive("topic", "consumer"); gist.github.com/Timer/d5952ec5…

1 0 0 30 0

View Details

Joe Haddad @timer150

11 months ago

@WebReflection @rauchg @tomasz_ducin send() resolves once the message is durably persisted to the queue, before processing starts.

1 0 0 86 0

View Details

Joe Haddad @timer150

11 months ago

@rauchg @WebReflection @tomasz_ducin @WebReflection given this insight, how would you design the API to receive and process a single message? 👀

2 0 0 375 0

View Details

Joe Haddad @timer150

11 months ago

@rauchg @WebReflection @tomasz_ducin It's semantically equivalent to await new Promise((resolve, reject) => { .. }), where the handler is invoked immediately.