goodoldneon

7 ms·

31.
by goodoldneon 2y ago
Wonder if this is the reason: https://x.com/garageklub/status/1779571445930324456
32.
by goodoldneon 3y ago
Queues and workflow engines aren’t the right solution for everything, but they work well for a lot of stuff. Like a signup flow that integrates with multiple third-parties, or a drip campaign, or notifications. Those are things many small,
33.
by goodoldneon 3y ago
But you also spend a lot of cycles building and maintaining the ancillary features that make queues powerful. Early- to mid-stage companies especially need to focus on business logic and less on reinventing wheels
34.
by goodoldneon 3y ago
Inngest | 3 Engineer roles | Fully-remote Inngest is the reliability layer for modern applications. Inngest combines durable execution, events, and queues into a zero-infra platform with built-in observability. We're multi-cloud (host
35.
Debouncing in Queueing Systems: Optimizing Efficiency in Asynchronous Workflows(inngest.com)
11 points by goodoldneon 3y ago|0 comments
36.
by goodoldneon 3y ago
No, Inngest doesn't host your code so it doesn't need your secrets
37.
by goodoldneon 3y ago
What’s an example of Prettier breaking code?
38.
Migrating long running workflows across clouds with zero downtime(inngest.com)
5 points by goodoldneon 3y ago|1 comments
39.
by goodoldneon 3y ago
Which languages do you enjoy more?
40.
by goodoldneon 3y ago
It makes the happy path harder to read but the unhappy paths much clearer. I hated this aspect of Go when I first started with the language but I love it now
41.
by goodoldneon 3y ago
Oh I agree, I've run into too many nil pointer panics. I wish Go had a first-class way of expressing optionality, rather than using pointers
42.
by goodoldneon 3y ago
Go can be `tuple[User | None, Exception | None]` or `tuple[User, Exception | None]`, depending on whether you're returning a pointer. But yea, Go's approach has its warts. Like if you aren't returning a pointer then you need
43.
by goodoldneon 3y ago
Author here! We don't return errors in our public methods so our SDK still feels Pythonic. We're debating whether to add `_safe` suffix methods that return errors to give people the option, but for now our library only throws erro
44.
by goodoldneon 3y ago
That type won't help if you're unpacking like `user, err = get_user(user_id)`. Both values will be nullable and the type-checker won't understand that `user` is not None if `err` is None
45.
by goodoldneon 3y ago
By "context" I mean other data that lived at the time of the error. For example, you may want to update a table row when there's an error but if a thrown error takes you too far down the stack then you might not know the row
46.
by goodoldneon 3y ago
> Exceptions are just spooky GOTO and a distance I couldn't agree more! When you throw exceptions it's unclear where the control flow will go
47.
by goodoldneon 3y ago
Oops! I'll make that correction later today. You're right: they're mutually exclusive
48.
by goodoldneon 3y ago
> What if the program receives an interrupt signal during the get_user call? You shouldn't catch interrupt signals regardless of whether you're throwing or returning errors. This is why your error classes should extend Exceptio
49.
by goodoldneon 3y ago
Author here! > Why does the author want to swallow these exceptions? Sometimes you want to swallow exceptions and sometimes you don't. The examples in the article may be a little contrived, but there are situations where logging an
50.
by goodoldneon 3y ago
We write wrappers for standard and third-party libraries that throw errors. For example, we have our own dump_json function that catches-and-returns errors thrown by json.dumps. We didn't need many wrappers given the nature of our SDK,
51.
by goodoldneon 3y ago
It doesn't need to be contact lens sized. There's a sizeable market for AR glasses, as long as their form factor is indistinguishable from regular glasses
52.
by goodoldneon 3y ago
Would be great while driving. Better than a dash cam
53.
by goodoldneon 3y ago
How do you calculate the count for each filter without running a separate query for each filter?
54.
by goodoldneon 3y ago
"Simulate surveys" makes it sound like a satirical AI product
55.
by goodoldneon 3y ago
When reading your original comment, it sounds like you're saying that the solution is to avoid undergraduate college and leverage connections to immediately get a job. While that might work for people with those connections, how is tha
56.
by goodoldneon 3y ago
How is it difficult? Tons of companies have profitable UIs that aren't using a meta framework. Just because the React team says "we recommend you do X" doesn't mean you have to do X. If they said, "you must do X&quo
57.
by goodoldneon 3y ago
You can still use just React. No one is forcing you to use Next or Remix
58.
by goodoldneon 3y ago
Meta should use an event loop to avoid blocking Threads
59.
by goodoldneon 3y ago
[Inngest engineer] Half of us are Go devs, so we definitely don't think TypeScript should be the default language everyone uses. We only chose to start with a TypeScript SDK!
60.
by goodoldneon 3y ago
> ... they find out how hard writing SDKs and tooling for each of them is. Absolutely. Each additional SDK adds a lot of maintenance effort. It isn't just a write-it-once thing: - More time spent writing/updating docs - More co

More ›