Lotta fun getting this live. Top of mind these days:
- template is now a "securely self-host AI infra as cheaply as possible" project
- integrating with @runpod to try finetuning some models, interested in more providers
- Still working out how I want agents/memory/skills/tasks to persist and sync across projects, agents, etc.
Currently building an infra template for vibecoding: secure-by-default devcontainer with sandboxed claude code, secrets in doppler (never on disk), tailscale-only SSH with anti-lockout safeguards, push-to-deploy onto a ~€6/mo hetzner VPS via coolify, operable end-to-end from a phone
at DD we only have prod and sandboxes. sandboxes are ephemeral and short lived. otherwise everything is is feature flagged. this is intentional because staging and dev environments will naturally drift from prod and come with their own headaches, as opposed to building prod with test tenancy support
@BayAreaREMatt@ZeBirdman smart. yeah the risk of getting dropped sketches me out. Last i checked FAIR plan enrollment is up like 30% YoY for past few years
Currently building an infra template for vibecoding: secure-by-default devcontainer with sandboxed claude code, secrets in doppler (never on disk), tailscale-only SSH with anti-lockout safeguards, push-to-deploy onto a ~€6/mo hetzner VPS via coolify, operable end-to-end from a phone
the flow state of agentic coding is way less satisfying-English as the primary programming language breaks the fourth wall, grounding you in tangible concepts with reasoning constantly explained, instead of solo navigating an abstract space the mind holds a matrix-like snapshot of
@avg_engineer_@0xlelouch_ In reality flexibility can be provided by exposing an additional REST-“ish” endpoint for whatever specific use case is required. Easier than maintaining a flexible, all purposeful graph
- Batch attacks
- less bot traffic/Cloudflare protection
- Worse observability out the box
- no http spec semantics
- Unnecessary abstraction for most use cases
- higher learning curve vs RESTs is proven
- more client dependencies required
- More complexity
- minimal benefit given the overhead
@garrytan Yeah MCP is far less relevant now IMO. In our experience, it unnecessarily burns tokens compared to CLI. Claude's so good at handling almost anything that the benefits of a single unified API/protocol are outweighed by token cost & context limits.