urn,type,status,published_at_utc,post_url,title,excerpt,text,image_url,impressions,reactions,comments,reposts,stats_captured_at 7487164575059058688,post,PUBLISHED,2026-07-26T15:18:59.485Z,https://www.linkedin.com/feed/update/urn:li:activity:7487164575059058688/,Pairwise Testing deserves more attention—especially now,The applied mathematics behind it offers a practical answer to a persistent engineering problem: How do we evaluate a complex system systematically when exhaustive testing is too…,"Pairwise Testing deserves more attention—especially now. The applied mathematics behind it offers a practical answer to a persistent engineering problem: How do we evaluate a complex system systematically when exhaustive testing is too expensive and time-consuming? The key concept is a Covering Array—a mathematical construct that transforms thousands of possible combinations into a smaller, systematic set of test cases while ensuring that every pair of input values appears at least once. In other words: • Combinatorial Science defines the challenge. • Covering Arrays provide the mathematical foundation. • Pairwise Testing turns it into an engineering practice. I previously explored this approach in detail, with practical examples, in my article on applying Combinatorial Science to enterprise data platforms. The concept is even more relevant in the era of Agentic AI and AI Evals. An agentic system may vary across models, prompts, tools, datasets, workflows, memory configurations, policies, and runtime conditions. Testing every possible combination quickly becomes impractical. Evals are also not fully automated. Humans still steer: • Evaluation scenarios • Judgments and expected outcomes • Rubrics and scoring criteria • Risk thresholds • Edge cases and failure analysis Applying combinatorial techniques can help teams design a smaller but more systematic evaluation matrix—reducing model calls, human review effort, cost, and execution time while preserving meaningful interaction coverage. ""Every pair, at least once. That simple principle may become an important foundation for scalable AI evaluation engineering. "" Read the detailed article for the concepts, examples, and enterprise use cases. Article link: https://lnkd.in/g49nJ3wQ Article title ""Applying combinatorial science and discrete mathematics to data-platform engineering and testing"" #AppliedMathematics #CombinatorialScience #CoveringArrays #PairwiseTesting #AIEvals #AgenticAI #AIEngineering #DataEngineering",https://media.licdn.com/dms/image/v2/D5622AQH3GqfLeHMRog/feedshare-shrink_800/B56Z.fAgbCHYAc-/0/1785079138251?e=1786579200&v=beta&t=Y2-gN25g6tgPTsti6Oe-03FvTtuY_7joFy9mPhcGztQ,233,0,0,0,2026-08-02 7487142880839565312,post,PUBLISHED,2026-07-26T13:52:47.180Z,https://www.linkedin.com/feed/update/urn:li:activity:7487142880839565312/,Meet DataGov — my new open-source data governance CLI,"Written in Rust. Built for agents. The goal is simple: one binary, with no Python, Java, Node.js, or Docker dependency, that both engineers and AI agents can run reliably. DataGov…","Meet DataGov — my new open-source data governance CLI. Written in Rust. Built for agents. The goal is simple: one binary, with no Python, Java, Node.js, or Docker dependency, that both engineers and AI agents can run reliably. DataGov is being designed to: - Inspect CSV and Parquet datasets - Profile columns - Parse, format, and transpile SQL across dialects - Scan for PII - Run data quality checks - Generate a normalized JSON governance report Here are some commands you can use: - datagov inspect customers.parquet - datagov profile customers.csv - datagov sql transpile query.sql --from spark --to duckdb - datagov pii scan customers.parquet - datagov report customers.parquet --profile --pii --output report.json Why am I building it? Data governance has been my primary focus for years. As agents increasingly handle data engineering tasks, they require governance tools that provide JSON output, stable exit codes, deterministic behavior, and no interactive prompts. I couldn't find a CLI that merged these agent-ready features with effective data governance capabilities, which led me to create this tool. The guiding principles are: - Deterministic first - Local first - Privacy first PII detection will rely on rules and parsers instead of LLM guesses, ensuring sensitive values remain masked by default and that data stays on the local machine. This is just the beginning; it's an early-stage kickoff rather than a finished product announcement. Bolt 1, the CLI foundation and governance report envelope, is complete, and Bolt 2, focused on dataset inspection, is currently underway. The first milestone will encompass inspect, profile, SQL, PII scan, and report functionalities. Check out the repository at https://lnkd.in/gsuU48M5 #AdaptiveDataGovOps #DataGovernance #OpenSource #Rust #AIAgents",https://media.licdn.com/dms/image/v2/D5622AQFb_gqoYru3nA/feedshare-shrink_800/B56Z.esxnFK4Ac-/0/1785073965877?e=1786579200&v=beta&t=DWkYtea5UcLW0OsG1Ch5b8qpcrV9zO2fMZahTiDBUEM,1134,0,0,0,2026-08-02 7486083742336417792,post,PUBLISHED,2026-07-23T15:44:08.883Z,https://www.linkedin.com/feed/update/urn:li:activity:7486083742336417792/,Introducing the latest addition to my agent fleet,"the youtube-transcriber, now number nine. What it does: Simply provide a YouTube link, and it returns the full spoken transcript of the audio, not just the captions. This means…","Introducing the latest addition to my agent fleet: the youtube-transcriber, now number nine. What it does: Simply provide a YouTube link, and it returns the full spoken transcript of the audio, not just the captions. This means you get the actual audio transcribed from start to finish. Why I built it: In conference talks, important figures are often mentioned in passing. Speakers may only mention a statistic once, and then it's lost. Captions can be auto-generated and may miss crucial information or be altered by marketing teams. I wanted a way to make those numbers searchable, with the speaker and timestamp included. What powers it: - LangGraph with five nodes: resolve → fetch audio → transcribe → write outputs, featuring a cached-audio branch for repeat runs to skip downloads. - faster-whisper (distil-large-v3) operates on my machine, not through an API. - yt-dlp for audio extraction and ffmpeg for normalization. - Pydantic for state management, tenacity for retries, and optional OpenTelemetry (I am using Arize and LangSmith) Each run produces four files: a readable transcript with timestamps, a full JSON file with per-segment timings, an SRT file, and a metrics file. In the first four talks (The Youtube videos, I used for my testing), I processed 67 minutes of audio, generating 10,658 words in about 14 minutes of compute time—roughly 4.5 to 4.9 times faster than real-time, with zero tokens and zero costs, as it operates entirely on my mac-mini. The other eight agents include: job-scout, job-matcher, job-pilot, api-test-generator, diagram-generator, github-pr-digest, privacy-classifier, and linkedin-cover-generator. #AIAgents #LangGraph #Whisper #LocalFirst #AINative",https://media.licdn.com/dms/image/v2/D5622AQFqKGhrGbCNmA/feedshare-shrink_800/B56Z.Ppfn.GUAc-/0/1784821447573?e=1786579200&v=beta&t=tifTNUTUsiD0ri8VB8kEFLsgFnQ2NjYXa6nj3R4ssh0,434,0,1,0,2026-08-02 7486074529379913730,post,PUBLISHED,2026-07-23T15:07:32.343Z,https://www.linkedin.com/feed/update/urn:li:activity:7486074529379913730/,"The landscape of agent frameworks is rapidly evolving, with new names appearing…","every few weeks: OpenAI Agents SDK, LangGraph, CrewAI, PydanticAI, LangChain, Claude agents, and more. Despite the varying terminologies and abstractions, the underlying execution…","The landscape of agent frameworks is rapidly evolving, with new names appearing every few weeks: OpenAI Agents SDK, LangGraph, CrewAI, PydanticAI, LangChain, Claude agents, and more. Despite the varying terminologies and abstractions, the underlying execution pattern remains largely consistent. Currently, there is no single industry-standard agent lifecycle, but a common pattern is emerging that is more beneficial to learn than memorizing the vocabulary of any one framework. Here are the eleven stages, typically in the order they run: 1. User request 2. Context assembly 3. Memory retrieval 4. Knowledge retrieval 5. Planning 6. Tool or skill selection 7. Execution 8. Response generation 9. Evaluation 10. Reflection 11. Optional memory update It's important to distinguish between evaluation and reflection. Evaluation assesses whether the output met the task requirements, while reflection considers the process and what changes might be needed for future runs (Feedback loop and Agent Training). Additionally, knowledge and memory are distinct; knowledge is derived from documents, databases, and APIs, whereas memory stems from interactions, preferences, and past decisions. Context is built from both for the current request only. Response generation, which is stage 8 of 11, is the visible part of the process, but it is often mistaken for the entirety of the system. I have compiled the full lifecycle into a one-page cheatsheet, as shown in the pdf document below. #AIAgents #AgentEngineering #GenAI #RAG #AIEngineering …more Your document has finished loading