MLOps.community

Demetrios

Relaxed Conversations around getting AI into production, whatever shape that may come in (agentic, traditional ML, LLMs, Vibes, etc)

  1. 8 giờ trước

    Developers May Stop Depending on Libraries

    In this episode of Agentic Conversations, we're joined by Shaun Smith, software engineer, open source advocate, and contributor at Hugging Face, to explore how AI coding has changed almost overnight. We dive into reinforcement learning, MCP (Model Context Protocol), Fast Agent, Claude Code, open source AI, and why today's language models have become so capable that many traditional software libraries are becoming "liquefied." Shaun explains how reinforcement learning unlocked long-running autonomous agents, why ideas are becoming more valuable than code, and how developers should think about building software in an era where AI can generate entire applications. Along the way, we discuss Hugging Face's MCP server, Fast Agent, AI-powered developer tools, multimodal applications, MCP Apps, context windows, coding assistants, Rust, Python, TypeScript, open-weight models, software architecture, and what the future of programming looks like when humans increasingly focus on design instead of implementation. Shaun Smith: https://www.linkedin.com/in/smithshaunDemetrios: https://www.linkedin.com/in/dpbrinkm Hugging Face: https://huggingface.co Timestamps: 00:00 Introduction 01:56 The State of Open Source AI 05:18 Reinforcement Learning Changed Everything 07:50 Fast Agent Explained 10:18 Fast Agent as an MCP Reference Platform 12:20 Building Smarter AI Tools at Hugging Face 15:17 Natural Language Search Instead of APIs 17:46 Why MCP Apps Matter 20:06 The Evolution of MCP Apps 23:05 Building AI-Native User Interfaces 26:12 Context Is the New Programming Language 28:00 The End of Code Libraries 29:50 Why Developers Aren't Writing Code 31:25 AI Changes Software Engineering 33:05 The Future of Open Source AI 35:43 Claude Skills That Save Hours 38:02 Training Models with AI 39:05 Building Your Own AI Tools 40:50 MCP for Consumers, Enterprises, and Developers 43:42 Why Shell Access Makes Agents Smarter 45:18 Secure Agent Workflows 46:08 The Future of AI Interfaces 47:02 Outro

    47 phút
  2. Omnigent: Composition, Control, and Collaboration for AI Agents

    3 ngày trước

    Omnigent: Composition, Control, and Collaboration for AI Agents

    Denny Lee is PM Director, Startups & Ecosystem at Databricks, a longtime Apache Spark, MLflow, and Delta Lake contributor — and one of the people behind Omnigent, the open-source meta-harness Databricks just released under Apache 2.0. He joins Demetrios to explain why the industry is moving from models to harnesses to meta-harnesses, why token spend is replaying the CapEx-to-OpEx shift all over again, and why he's using debating AI agents to plan a matcha farm in Taiwan. In this episode: 🍵 Agents as research partners — Denny uses dueling agents to scout matcha-growing regions in Taiwan, down to soil pH, elevation, and processing infrastructure 🥊 Why agents should debate each other — letting two models argue surfaces the questions you didn't know to ask 🔱 Forking conversations — the missing UX pattern: branch a session, keep the shared context, explore two threads in parallel 🧠 The meta-harness layer — how Omnigent sits above Claude Code, Codex, Pi, and custom agents so models and harnesses become hot-swappable parts 👥 The two-pizza rule for agents — military span-of-control logic says you can manage 5–7 agents before you lose the thread 💸 Tokenomics is the new DevOps — the CapEx→OpEx playbook repeats: give developers spend visibility, keep central governance for the rest 🛡️ Policies, budgets, and guardrails — enforcing cost caps and approval rules at the harness layer instead of inside prompts 🤖 Auto model selection — why classic machine learning (not another LLM) may be the right way to route tasks to cheap vs. frontier models ✍️ "Created by" vs. "assisted by" — the open source accountability debate: whoever submits the code owns the code 🗄️ Databases are back — agents need cheap, stateful memory, which is why Postgres, Lakebase, and serverless databases are having a moment If you're building with coding agents, managing AI spend, or trying to keep up with the harness arms race, this one's for you. Links & Resources: Omnigent (open source): https://www.databricks.com/blog/introducing-omnigent-meta-harness-combine-control-and-share-your-agents Omnigent GitHub: https://github.com/databricks/omnigent Denny Lee on LinkedIn: https://www.linkedin.com/in/dennyglee Denny's blog: https://dennyglee.com Tokenomics Foundation announcement: https://www.finops.org/insights/finops-x-2026-day-1-keynote/

    58 phút
  3. 5 ngày trước

    The Current State of Agentic Retrieval - Qdrant Roundtable

    Qdrant Roundtable episode: The Current State of Agentic Retrieval Join the Community: https://go.mlops.community/YTJoinIn Get the newsletter: https://go.mlops.community/YTNewsletter MLOps GPU Guide: https://go.mlops.community/gpuguide Big shout-out to Qdrant for the collaboration! // Abstract AI agents are only as good as the information they can find, retrieve, and remember. In this community roundtable with the Qdrant team, we explored the latest advances in agentic memory, vector search, retrieval systems, and production AI architectures. As AI agents move beyond simple chatbots into systems that can reason across large amounts of information, retrieval is becoming one of the most important layers in the AI stack. The discussion covered the real-world challenges of building agents that remember what matters, forget what doesn't, and consistently retrieve the right context at the right time. If you're building AI agents, RAG systems, or production AI applications, this conversation offers practical insights into where retrieval is headed and what it takes to build reliable, scalable agentic systems. // Bio Ewa Szyszka Ewa is a Developer Relations professional based in San Francisco with a background in Computer Science and Hardware Engineering, passionate about bridging the gap between technology and the developer community. She holds a BSc in Computer Science and an MSc in Electronics, bringing a strong blend of deep technical foundations and communication skills to her work. Dylan Couzon Dylan is based in New York City, and he helps developers build better AI applications. He is passionate about AI, programming, open source, and robotics, and enjoys sharing what he’s building and learning along the way. Neil Kanungo Neil is an experienced professional with expertise in data science, developer relations, and product growth. Currently serving as the Head of Developer Relations at Qdrant, Neil previously held the position of VP of Product Led Growth & Developer Relations at KX, where significant increases in product registration and user activation were achieved. At TIBCO, Neil managed a team focused on enhancing the adoption of TIBCO Spotfire through various initiatives, including tutorial videos and live webinars. With a strong technical background, Neil has developed innovative solutions in analytics, machine learning, and data visualization across multiple roles, including Engineering Data Analyst and Asset Integrity Engineer at Enterprise Products. Neil holds a Bachelor of Science in Radiation Physics from The University of Texas at Austin, a Master of Science in Mechanical Engineering from Texas Tech University, and is pursuing a Master in Applied Data Science from the University of Michigan. Evgeniya Sukhodolskaya Developer Relations at Qdrant with 8 years of IT experience across software engineering, machine learning, and technical management, and 4 years in Developer Relations. Holds a Master’s in Machine Learning, Data Analytics, and Data Engineering. Passionate about NLP, data-centric AI, and the role of vector search in advancing AI technologies. Andrei Cristea Andrei is a Berlin-based Developer Relations Engineer at Qdrant, a prominent open-source vector database. With a Master’s degree in Artificial Intelligence from TU Munich, his expertise bridges AI, data infrastructure, and knowledge engineering. Hosted by Demetrios // Related Links Website: https://qdrant.tech/ ~~~~~~~~ ✌️Connect With Us ✌️ ~~~~~~~ Catch all episodes, blogs, newsletters, and more: https://go.mlops.community/TYExplore Join our Slack community [https://go.mlops.community/slack] Follow us on X/Twitter [@mlopscommunity](https://x.com/mlopscommunity) or [LinkedIn](https://go.mlops.community/linkedin)] Sign up for the next meetup: [https://go.mlops.community/register] MLOps Swag/Merch: [https://shop.mlops.community/]

    59 phút
  4. AI Agents in Healthcare?

    6 ngày trước

    AI Agents in Healthcare?

    Kingsley Madikaegbu is the founder of HealID, a startup building agentic AI on top of the Model Context Protocol (MCP) for one of the most heavily regulated environments there is: healthcare. Recorded at MCP Dev Summit North America in New York, Kingsley sits down with Alex Salkever of the Agentic AI Foundation to break down how you give patients, doctors, caregivers, and family members each their own agent over the same medical record — without breaching HIPAA, leaking PHI, or letting an agent quietly go off the rails. In this conversation:🏗️ The four-layer architecture — Dumb data at the bottom, then access permissions, then MCP, then reasoning agents on top. Why logic never touches the data layer.🔐 MCP vs REST — Why enforcing per-role compliance in a REST API meant encoding permissions everywhere, and how MCP collapses that mess.🪪 HIPAA, auditability & traceability — Proving a specific person (not a snooping agent) accessed a record, with a full audit trail that regulators actually accept.🎟️ The nightclub-bouncer analogy — How MCP reorganizes the entire "club" per guest instead of just checking a VIP list.⌚ Wearables & real-world data — Turning an Apple Watch arrhythmia signal into a triaged, severity-scored workflow with doctors in the loop.🧭 Deterministic vs model-driven — Why anything clinical or regulatory stays binary, and the agent-as-coach (not decision-maker) pattern for patients.🛑 Keeping agents on the leash — Tool restriction, behavioral metadata, and drift/anomaly detection so an agent can't reinterpret its own job.⚡ The instant kill switch — Revoke permission, and the agent returns a hard 404, never partial data.⚖️ The liability question — When an agent follows a designed workflow and something goes wrong, who's responsible: patient, host, or provider? The industry hasn't decided.📋 Kingsley's MCP wishlist — Built-in traceability (OTEL-style spans), native time-bound enforcement, and guardrails against agent-to-agent data leakage.If you're building agentic systems for healthcare, finance, legal, or any regulated industry where "the agent did it" isn't a good enough answer — this one's for you.Links & Resources🔗 HealID — https://gethealid.com/🔗 Kingsley Madikaegbu — https://www.linkedin.com/in/kmadikaegbu🔗 Alex Salkever / Agentic AI Foundation — linkedin.com/in/alexsalkever🔗 MCP Dev Summit North America — https://events.linuxfoundation.org/mcp-dev-summit-north-america/Timestamps:[00:00] Intro[00:13] AI Agent Liability[01:10] MCP in Healthcare AI[06:30] MCP vs REST Architecture[11:29] Healthcare Integration Challenges[18:29] Non-compliant Patient Challenges[24:13] Deterministic vs Model-Driven Workflows[28:08] AI in Healthcare Conversations[34:38] Agent-to-agent workflows in healthcare[38:02] Future MCP security

    39 phút
4,6
/5
24 Xếp hạng

Giới Thiệu

Relaxed Conversations around getting AI into production, whatever shape that may come in (agentic, traditional ML, LLMs, Vibes, etc)

Có Thể Bạn Cũng Thích