HN user

goodoldneon

918 karma
Posts8
Comments296
View on HN
Neovim 0.12.0 4 months ago

I switched from Cursor to Neovim and at first I hated Neovim’s poor AI ghost text. Now I kind of like the break from heavy AI when I write code.

The vast vast majority of my code is written by Claude Code, so I don’t write much. But when I do it’s like an exercise in warding off programming atrophy

You shouldn't be blocking the main event loop for 30 seconds! The main event loop is not intended to be used for heavy processing.

This article is talking about an SDK that runs in users' apps. Users can run whatever code they want, so the SDK has to find a way to keep sending the outgoing heartbeats

Vercel Workflow Kit takes a very different approach. Lack of step IDs (which makes them worse at handling code changes), compilation step, more opinionated about backends ("worlds", as they call them). Vercel Workflow Kit has magic that admittedly makes it a little easier to get started, but that magic causes problems when you want a mature product.

Cloudflare Workflows are actually complementary to StepKit! We'll soon release an adapter that lets you define StepKit workflows that run as Cloudflare Workflows. We have a POC in `packages/cloudflare` in our repo

Inngest engineer here! For a little extra context, the `@stepkit/core` package is basically just an API for defining a workflow. There isn't much to it because we don't want to be overly opinionated on backend implementations!

The `@stepkit/sdk-tools` package is a set of tools for building your own StepKit SDK. The vast vast majority of stuff in there is optional, but highly valuable if you want to avoid reinventing the wheel when building your own SDK.

Looks like you're being downvoted but you're right. A tiny fraction of high school students would actually care about these classes -- high school me wouldn't

IIRC, the lifecycle hook only prevents destruction of the resource if it needs to be replaced (e.g. change an immutable field). If you outright delete the resource declaration in code then it’s destroyed. I may be misremembering though

Do not base your company’s tech decisions on FAANG companies unless your company is a FAANG company. Your challenges are likely very different from theirs

Right, you can change punctuation to clarify it. However, it doesn't change the fact that the Oxford comma could make the list readable as a parenthetical phrase.

I'm not saying the Oxford comma is bad. I'm just saying that it isn't 100% perfect as many people imply.

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, all developer teams need. They don’t want to hire an infra-minded person just for queues and workflows

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

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 your code wherever you want!) and multi-language. Our product takes advanced-but-complicated reliability patterns and makes them simple to configure for any developer.

We're a team of 10 who recently raised a seed extension round. Come join us if you want to work in our fascinating problem space!

Jobs -> https://jobs.ashbyhq.com/inngest

- Staff Frontend Engineer

- Systems Engineer

- Product Engineer

Company -> https://inngest.com