venturin
The Apparatus, Not the Artifact
One way to slice it: there are three kinds of underspecification an agent has to close.
Intent: what the user wanted (JWT vs cookies, should free users see this feature). Verification can't close this and probably shouldn't try.
Structural e.g. null, types, exhaustiveness, ownership. Sound static analysis closes this by construction.
Domain e.g. auth on every route, error propagation, contract stability. A domain-shaped apparatus closes this because it knows what kind of program is being built.
Babysitter, auditor, prayer is the right taxonomy of bad options. The fourth option is making the LLM a component inside an apparatus that handles structural and domain statically, and leaving the human on intent.
We’ve open-sourced an example service (yes, it's called hackernews) you can try locally or on Kubernetes. It supports seamless scaling via kubectl scale, with zero downtime and no changes to your backend logic.
Blog post with diagrams and code here: https://skip.dev/blog/dynamic-scaling
GitHub repo: https://github.com/skiplang/skip To try it:
npx create-skip-service hackernews --example hackernews --verbose
docker compose -f hackernews/compose.distributed.yml up --build
Curious to hear your thoughts or feedback!Dynamically Scaling Reactive Services with Skip (Now with Kubernetes Support)
https://maecen.com/ https://www.tipeee.com/ https://patreon.com/ https://www.buymeacoffee.com/ https://flattr.com/ https://d.rip/
What other platform to host a profile and raise money monthly do you know ?