← All speakers

Bio, Work & Ideas

Paul Iusztin

Conference affiliation: Decoding AI · 2026

Paul Iusztin is the founder and chief executive of Decoding AI, an AI engineer and educator, and coauthor of the LLM Engineer’s Handbook. He builds and teaches production-ready AI systems that turn personal knowledge into reusable agent memory, preserve human judgment in generated writing, and evaluate outputs against real-world requirements.

Raised in Timișoara, Romania, Iusztin began tutoring mathematics and programming in 2016 and working in software development in 2017. He later taught foundational AI classes at Politehnica University of Timișoara and researched three-dimensional object detection and tracking for autonomous driving at Continental. His account of becoming an AI engineer traces his transition into computer vision, machine-learning infrastructure, and production AI, including roles at Everseen, CoreAI, and Metaphysic. More recently, he worked as a founding AI engineer at a San Francisco startup developing agents for financial services.

He founded Decoding AI Magazine in 2023 to teach the complete path from AI prototype to deployed, monitored software. The LLM Engineer’s Handbook, published in 2024 and coauthored with Maxime Labonne, develops that approach through an LLM Twin: a personalized application combining data pipelines, retrieval, fine-tuning, deployment, monitoring, and evaluation. His collaboration with Louis-François Bouchard subsequently expanded into agent-engineering education and open-source practical workshops.

  • AI Research OS: Iusztin and Bouchard developed an open-source research-memory system that converts notes, saved articles, repositories, and other sources into persistent, project-specific context. Its file-based research wiki separates immutable source material from generated summaries, comparisons, conceptual notes, and a YAML index. Agents consult compact indexes and summaries before opening complete sources, reducing token consumption while keeping the system inspectable and independent of a vector database.
  • Human-directed technical writing: His research-and-writing architecture combines human-specified topics, angles, audiences, reusable style profiles, and representative writing samples. Separate reviewer and editor contexts check drafts against source research and authorial intent; structured feedback prioritizes the writer’s instructions over stylistic preferences. Local agent skills can handle individual workflows, while Model Context Protocol servers simplify distributing shared tools, dependencies, and credentials.
  • Calibrated agent evaluation: Iusztin treats an LLM judge as a binary classifier requiring real application outputs, human pass-or-fail labels, development and test splits, and precision, recall, and F1 measurements. Comparing development performance with held-out and live examples exposes overfitting; production traces covering tool calls, latency, cost, and outputs support debugging and regression detection.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

Combine exploratory research, file-based handoffs, structured editorial feedback, and a calibrated judge to turn a human brief into technical content you can inspect and improve.

  • Why a fluent post still needs research and editing
    0:32 ↗
  • Choose how much autonomy the task needs
    6:09 ↗
  • Keep coupled decisions in one agent
    13:15 ↗
  • Treat context as a budget
    16:15 ↗
  • Research broadly enough, then hand off a focused artifact
    20:22 ↗
  • Start with a human guideline and reusable services
    28:26 ↗
  • Separate the reasoning harness from the MCP server
    34:41 ↗
  • Make each research call inspectable
    40:06 ↗
  • Turn a video into a durable research artifact
    44:35 ↗
  • Connect the server and test one capability
    49:15 ↗
  • Use skills to load the research procedure
    56:14 ↗
  • Inspect the searches as well as the final report
    1:07:26 ↗
  • Build the writer’s context deliberately
    1:10:57 ↗
  • Teach the voice with representative examples
    1:19:10 ↗
  • Review in a separate context and return actionable feedback
    1:21:37 ↗
  • Run locally, then decide how to distribute the capability
    1:28:13 ↗
  • Follow the work through threads and traces
    1:33:06 ↗
  • Build evaluation data from the real writer
    1:37:00 ↗
  • Calibrate the judge against expert labels
    1:42:12 ↗
  • Read perfect scores in the context of their dataset
    1:46:37 ↗
  • New traces expose what the small evaluation missed
    1:53:05 ↗
  • Run the complete path from guideline to post
    1:55:00 ↗

Key ideas

Scroll to read ↓

A file-based research system connects saved notes to current work, then preserves sources, summaries, and new questions in a project wiki that can keep growing.

  • Finding the research you already saved
    0:00 ↗
  • When persistent research earns its setup cost
    3:31 ↗
  • Move memory out of the conversation
    7:59 ↗
  • V1: turn a topic and golden links into a report
    12:48 ↗
  • V2: let the second brain supply the seeds
    15:42 ↗
  • V3: preserve sources and build a reference index
    18:28 ↗
  • Read progressively, from summaries to raw evidence
    21:23 ↗
  • Let project knowledge change while protecting personal notes
    24:07 ↗
  • Launch research from an article brief
    27:04 ↗
  • Study harness architecture directly from repositories
    31:58 ↗
  • Start with only a few links
    34:25 ↗
  • Return to the wiki with a new question
    35:48 ↗
  • The remaining work is maintaining trustworthy memory
    36:46 ↗

References