devdoshi

Love this kind of system, so many useful mashup apps to build on top!

or rather, get more done with the same RAM

Are we observing corresponding work to make things use less memory though?

I've switched a lot of things to WASM and use way less RAM.

upvote for WAL + object storage (a very powerful combination I am finally seeing more adoption of) and a lot of interesting historical details.

I'm fortunate I don't rely on any forge for my solo work except for backups. In my personal stack I just have a log and content-addressed object kv storage, which can project to git if needed, or can be committed to git as files. And docker if I need isolation for CI/CD.

The most interesting alternative to me is atomic.dev (check their very informative blog posts) but I'll be keeping an eye on all of them.

If it weren't implemented by cloudflare natively, would you be ok using a library or something that wraps or hooks onto your IaC to wrap entry points with a worker (proxy or circuit-breaker, conceptually) with various types of limits (real-time estimated spend, or just counts of operations, or just a on/off switch wired to an email alert). I'm pulling a few of these threads at the moment since I've been ramping up my cloudflare usage.

I do think it is important to have autonomous discoverability with domain-anchored trust, whether through .well-known or DNS records or DNS over HTTP. It looks like cloudflare has already added a bunch of observability into their products around this area, and I am investigating too [1]. It seems like the number of services needing these, and the amount needed per org should both go up with more agentic use cases.

I believe auth.md is also a recent example that uses .well-known

[1] https://instagrate-me.sudoscience.dev/

I've been getting tired of implementing webhooks and sync the same old way. https://webpoke.sudoscience.dev/ seems simpler. I did a poc using s2.dev and val.town [1] and am using the general idea to explore with TLA+ to see how it would model it to falsify the claims.

[1] https://youtu.be/kSyE4aoNthE

Premiered May 14, 2026 Ron Minsky discusses Jane Street's approach to AI adoption throughout their SDLC at Bug Bash 2026.

Ron stakes out their position that AI workflows should maximize human effectiveness and understanding rather than replacing humans entirely. At Jane Street, many traditional (aka pre-Claude) software engineering practices have become more important rather than less. Type systems help provide fast feedback and enforce invariants that agents can understand. Expect tests allow developers to see system behavior and create deterministic simulations at the library level. Code review remains crucial for maintaining code quality and human understanding, even though agents change the dynamics. Finally, he touches on Jane Street’s growing interest in formal verification, and the impact of agents making previously expensive approaches, like formal methods, more practical.

(quoted from the youtube video description)