serbrech

Now GitHub can point an agent at this blog and say “implement this” :)

Yes, I mean, I’m an engineer on a cloud Kubernetes service, and I don’t run Kubernetes for my home services. I just run podman quadlets (systems units). But that is entirely different from an enterprise scale setup with monitoring, alerting, and scale in mind…

I recognize the problem statement and decomposition of it. But not the solution. Especially saying that he sees the same problem being worked on by N people. And now that makes in N+1? I’ve been more interested by the protocols and standard that could truly solve this for everyone in a cross-compatible way. Some people have dabbled with atproto as the transport and “memory” storage for example.

Should have LLM providers create stack overflow type of site based on user’s most asked problem. At least we won’t deplete de source of normal searches results.

CosmosDB has etags on every document

If only because there are 100-1000x more system that have now tied themselves ne their data to said cloud

As a feedback, having all the examples in that gif on the readme centered around node almost made me look away without a second thought.

Why is standard etag support making the frontpage?

On the fly speech translation but in the voice of the speaker

I wish that this was just a sdk built on top of a provider/standard. Amqp 1.0 is a standard protocol. You can build all this without being tied to a product or to rabbitMQ, with a storage provider and a amqp protocol layer.