The kind of thing being posted in Decodable's slack today (this one is from @rmoff.net):

And his epitaph read:

Poll:

We (Decodable) have a managed stream processing platform. It has a control plane (CP) and data plane (DP). We always run the CP. Customers can choose to let us run the DP or they can run it in their VPC (BYOC).

What do you call the type of account where we run both the CP and DP? Plz repost!

Unsolicited evergreen career advice: show up for interviews or at least send a note if you can't make it.

The current discourse on disaggregated compute and storage in data infra says local disk is bad. I think this lacks nuance. Local persistent disk (e.g. EBS) is bad. Ephemeral local disk should be embraced as a block cache for reads and staging of writes to durable storage. The cost/op is a win.

Strongly considering open sourcing a bunch of our key docs and templates at Decodable for technical (would-be) founders: MSA, NDA, operational model, marketing and sales funnel / revenue model. Stuff like that. Is this interesting to anyone but me?

I made an infra engineer starter pack. Folks posting about databases, stream processing, durable execution, orchestrators, service meshes, and more.

go.bsky.app/SCZe42X

Of course my first real contribution to tech-bluesky is to complain about the ergonomics of a async programming in Rust. I'm the worst.

I've been writing a ton of Rust lately. I know this isn't a hot take, and I know why it's the way that it is, but async still feels so bolt-on. The way async, closures, generics, and (object-safe) traits work together (or don't) is really painful. It's still good, but it definitely hinders adoption.

I’d be immensely excited to rebuild tech twitter here. Let’s make it happen.

Hello world.