Prompt Injection Defense for a 5-Person AI Startup
Prompt injection defense a five-person team can ship in a week: trust boundaries, least-privilege tools, approval gates, and what not to build yet.
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
Writing · Tag
55 posts on AI, page 4 of 5. Or browse the full writing index →
Prompt injection defense a five-person team can ship in a week: trust boundaries, least-privilege tools, approval gates, and what not to build yet.
Most AI agent frameworks reinvent a job queue badly. Oban already is one: durable, idempotent, retry-aware. Run an agent loop that survives a deploy mid-run.
Amazon mandated AI coding, let it touch infrastructure unwatched, and lost millions of orders. The fix was more humans per deploy.
Apple raised prices on Mac, iPad, and HomePod, blaming an AI-driven memory shortage. The cost of intelligence is falling; the hardware to run it isn't.
Eight failure patterns I see running AI coding agents daily: the confident wrong answers, the lost context, and the bugs they reliably ship.
Every AI agent framework runs the same loop: observe, decide, act, repeat. Here it is in 50 lines of Elixir with no framework, just a GenServer.
The Postgres you already run does RAG fine without a vector database. The hand-rolled pgvector path in Phoenix, and when Arcana earns its place.
The path to senior ran through the grunt work AI now does in one prompt. The knowing-vs-doing gap hits juniors first, and here's how to grow architects anyway.
Satya Nadella's 'token capital' framing is right that AI amplifies human judgment, but it's enterprise advice that skips the small teams who feel it first.
Go won the agent daemon and Python owns the reasoning. The layer nobody claimed is the one that bites you: thousands of long-lived, stateful, crash-prone agents you must keep alive. That's the BEAM's home turf.
Most engineers prompt Claude one sentence at a time. Anthropic's own engineers prompt skills. Four rules from their recent talks, with the operator nuance the talks left out.
Fifty prompts I use to ship production AI features, debug distributed systems, and write docs that don't rot. Code review, debugging, refactoring, system design, and PR-quality writing, with five full examples.