Hello,
# general
h
Hello, I’m an AI engineer focused on building production systems around modern AI platforms, mainly on backend and infrastructure. Recently I’ve been working across: * LLM platforms (OpenAI, open-weight models, fine-tuning, eval pipelines) * Agent frameworks (multi-step planning, tool use, orchestration) * RAG systems (vector search, hybrid retrieval, reranking, memory design) * Real-time systems (WebSockets, streaming inference, event-driven architectures) * Multimodal AI (text, image, audio pipelines) * MLOps and deployment (model serving, monitoring, scaling, cost control) * Data pipelines (embedding workflows, indexing, sync systems) * AI + Web3 integrations (on-chain/off-chain coordination, subnet-style systems) My focus is on making systems actually work in production. Reliability, latency control, reducing hallucinations, and designing architectures that scale beyond demos. Currently interested in how people here are approaching: * evaluation and reliability for agent workflows * long-context handling and memory systems * hybrid architectures combining LLMs with deterministic logic * tradeoffs between latency, cost, and output quality Open to exchanging ideas and approaches with others working on similar problems.
p
Our DevRel team @fierce-businessperson-64086 , @mammoth-lighter-94680 , and @brainy-leather-20096 have lots of thouguhts about those topics
How are you approaching those problems today?
m
Eval is hard, Hamel has some good suggestions on how to do with with multi step workflows. I'll link those here, I'd say try to create tests that focus on correct tool calling in isolation before conducting the whole flow
Specifically these first few paragraphs: We recommend evaluating agentic workflows in two phases: 1. End-to-end task success. Treat the agent as a black box and ask “did we meet the user’s goal?”. Define a precise success rule per task (exact answer, correct side-effect, etc.) and measure with human or aligned LLM judges. Take note of the first upstream failure when conducting error analysis. Once error analysis reveals which workflows fail most often, move to step-level diagnostics to understand why they’re failing. 2. Step-level diagnostics. Assuming that you have sufficiently instrumented your system with details of tool calls and responses, you can score individual components such as: - Tool choice: was the selected tool appropriate? - Parameter extraction: were inputs complete and well-formed? - Error handling: did the agent recover from empty results or API failures? - Context retention: did it preserve earlier constraints? - Efficiency: how many steps, seconds, and tokens were spent? - Goal checkpoints: for long workflows verify key milestones. Example: “Find Berkeley homes under $1M and schedule viewings” breaks into: parameters extracted correctly, relevant listings retrieved, availability checked, and calendar invites sent. Each checkpoint can pass or fail independently, making debugging tractable. **Use transition failure matrices to understand error patterns. **Create a matrix where rows represent the last successful state and columns represent where the first failure occurred. This is a great way to understand where the most failures occur.