tomredman

6 ms·

1.
by tomredman 2y ago
> My only issue was that the execution of an inngest function wasn't completely intuitive, at least in TS, and you have to think in terms of inngest or, more precisely, the abstraction it is providing. Is it an actor, a step functio
2.
by tomredman 2y ago
Are there plans beyond workflow? (For context I enjoy Inngest already :)
3.
by tomredman 2y ago
Wow, I had no idea you weren’t at 1.0 yet lol. I’ve been using Inngest for a few years(!) and it’s always felt really polished and complete to me. Congrats on the big one-oh. Question: I’ve been using Rust a lot more lately — does Inngest w
4.
by tomredman 3y ago
Love to see this guys, great work and love to this pivot working for you.
5.
by tomredman 3y ago
Next June!
6.
by tomredman 3y ago
The timing of this is pretty awesome for me. I’m building a product that requires fairly heavy, scheduled background services. Originally, I had built these services intermingled with my client and API, but it was not ideal from a developme
7.
by tomredman 5y ago
I mean, this is true. But it’s weird being in the center of that raging fire. We were worried about getting sued personally (there were lots of threats) and or having our family or work brought it into it. Lots of people tried to get me fir
8.
by tomredman 10y ago
Yup I am. My point though is that that argument is largely underestimating the value delivered by these products. And the apparent lack of P/M fit for spreadsheets managing diversity at large companies.
9.
by tomredman 10y ago
People had the same arguments against Dropbox (just use rsync) and Buffer itself (just use a cronjob).
10.
by tomredman 11y ago
Not me :) I opted for the equity option. -Tom, Mobile Engineer @ Buffer