Andrei Bondarev's wroclove.rb 2024 single-speaker talk. Frames generative AI as about to become a standard part of every tech stack (alongside databases, caches, queues, storage) per the a16z vision, with developers building on top of AI systems. Covers: what LLMs are and what they excel at (structuring unstructured data, summarization, classification, translation, content generation, Q&A), the shift from business logic in fat models/service objects to business logic in prompts, AI agents as autonomous LLM-powered programs using tools via function calling, and the reliability/generality trade-off (focused narrow agents are POC-ready; general-purpose reliable agents would equal AGI). Discusses slow adoption (fast-changing field, IP/copyright ambiguity, lack of tooling, risk — Air Canada chatbot lawsuit, GM chatbot agreeing to sell a car for $1), calls prompt engineering 'prompt alchemy', covers jailbreaking (Anthropic's many-shot jailbreaking paper) and hallucinations (GPT-4 trained up to April 2023). Introduces RAG: embed user query, similarity-search a vector store of proprietary docs, merge context into prompt. Explains vector embeddings (OpenAI's Ada model is 1536 dimensions), similarity metrics (Manhattan, Euclidean, cosine), evaluations via human up/down votes, LLM-as-critic using GPT-4, and the RAGAS method (faithfulness, context relevance, answer relevance). Argues against open chat bots due to prompt-injection risk — advocates closed control-panel UIs with narrowly-scoped agents. Live-codes a 'Nerds and Threads' e-commerce AI assistant using langchainrb with six tools (customer management, email service, inventory management, order management, payment gateway, shipping service) backed by SQLite, demonstrating order placement, returns, and inventory updates — each driven by a system prompt describing standard operating procedures. Closes on why Ruby (pragmatism, OOP principles, Sandi Metz's POODR, ability to port Python libs via ChatGPT) and open-source maintenance lessons (be responsive, friendly, helpful). Q&A explores generating executable Ruby code once vs. instructing the LLM per request.