There's a really neat pattern for building stateful apps on Postgres that can handle millions of entities concurrently.
Traditionally you'd need Kafka / RabbitMQ / other external components. But FOR UPDATE SKIP LOCKED basically make these redundant for some types of applications.
I found it particularly useful for building LLM-based agents that can transition between different states.
I wrote a tool that helps estimate K8s costs by simulating K8s clusters. You write your pods in a simple DSL and it runs kube-scheduler without actual nodes behind the scenes.
It's still really basic but I'd love to hear your feedback!
I think this is a great idea. I can see the DSL being very useful for situations where you want to think about hypotheticals. My main piece of feedback is that you should consider supporting the ability to feed in your existing k8s manifests as input to this tool instead in addition to the DSL. I think that would make this tool very appealing and very easy to onboard users with existing clusters who are looking to reduce their costs.
Not exactly a channel, but a few weeks ago I did a live coding session on how to build an ML platform from scratch (the stuff you need to get ML models to production):
The reason why you don't see so much of this type of literature is because the dominance of virtual AI: Google, Siri, etc. Hardware is expensive and learning with hardware is slow. However, the type of AI required is IMHO much more interesting. I think we really understand how our brains work if we have an AI competing at the Olympics.
That's a really good idea to make the future developers learn the Apple platform. But Microsoft had a better one; to buy Minecraft and add it to Visual Studio.
reply