XFollowListPeople, ideas and original work on X

AI reading list

Applied AI engineering

A model response becomes useful through the application around it: the information retrieved, the structure of the result and the checks applied before and after a release. Follow a small extraction or retrieval example, define failures on your own data, then plan the logs and controls that make a running system understandable.

Selected sources
7

People to read

Open the first material, then continue with the author on X. People appear once, grouped by their main reading use and ordered by handle within each group.

2 of 7 people

Operate and maintain the application

Plan latency, cost, failure handling and observability, then keep verification in the release and maintenance loop.

  • Keep verification in the development and maintenance loop. Osmani connects the final output and the path used to produce it with regression tests, versioned context and production observation. This route helps a team decide what must be checked before accepting an agent-built change.

    Start with this Web material · addyosmani.com

    The New Software Lifecycle

    Read Verification and How each phase actually changes. This is Osmani’s commentary on a whitepaper coauthored with Shubham Saboo and Sokratis Kartakis. Use its release-checking questions; cost diagrams are illustrative.

    This work in the author’s profile

    Published . Material checked .

  • Plan the components around a model API as the application grows. Huyen connects retrieval, guardrails, model routing and caching to latency, cost and failure handling. Her observability section shows what to record so a bad response can be traced to the step that produced it.

    Start with this Web material · huyenchip.com

    Building A Generative AI Platform

    Follow the architecture diagrams, gateway and caching tradeoffs, then logs, metrics and traces. The components are a planning guide; the 2024 prices and sample API calls need current documentation before implementation.

    This work in the author’s profile

    Published . Material checked .

A few bearings for your reading

These field notes explain the people, language and questions you may meet along the way.

XFollowList field note

How to evaluate an AI application on your own task

Define a useful success test, trace a published failure and compare fixes through Hamel Husain, Jason Liu, Eugene Yan and Chip Huyen.

XFollowList field note

An AI agent demo checklist: tools, state and success

Assess an AI agent demo through its tools, state, access and checked outcome. Read a published database-error recovery and plan the next useful test.

XFollowList field note

Before you download a local LLM

Separate model from runtime, budget memory beyond the file and plan a repeatable local-model test with original work from five useful authors.

Where to go next

AI agents & automation

Need the application to choose tools and change external state? Continue with agent architecture, execution and action controls.

Vibe coding & coding agents

Want help implementing the application with a coding agent? Read the specification, coding and review workflows.

LLM research & explanations

Need to understand the model’s architecture, training or reasoning before adapting it? Read the original research and teaching materials.

Local models & open projects

Compare local model execution, memory use and serving tradeoffs before choosing where the application runs.

AI security & interpretability

Add tests for attacker-controlled input, data boundaries and unwanted tool actions.

How this list is selected

We selected people through their own engineering guides, project walkthroughs and coauthored work. Each first read answers a specific application question. Historical code and prices keep their original dates; product evaluations need the reader’s data and criteria. Recent X activity was not assessed for this selection.