42 Zhangjing episode analysis · AI engineering and product operations
Guest: Zhang Luyu, introduced as founder of Dify.AI | Host: Qu Kai; closing questions: producer Celia
Published: August 20, 2023 | Duration: 74 minutes 9 seconds | Prepared: October 18, 2026
Original episode and official introduction
Connecting an API begins the product test
How far is a model that answers questions from an application a business can use over time? This 2023 interview breaks that distance into handling information, testing instructions, organizing tools and operating the product after launch. Dify’s ambition includes a workspace through which business colleagues can keep shaping an application.
Qu Kai discloses that he invested in Dify and has a working relationship with the team. Assessments of its execution, competitors and the opportunity for an intermediate platform should be read with that relationship in view. This analysis preserves the historical questions and methods; model rankings, business figures and predictions from 2023 are not presented as current facts.
1. Fifty thousand applications indicate exposure, not fifty thousand successes
Episode reference: 00:36–06:55. Luyu describes LLMOps as combining development with continuing operation of model applications. After engineers connect the capabilities, operations, sales and other colleagues who understand the business must still change knowledge and instructions to bring responses closer to expectations. Server availability and the usefulness of answers are separate problems that both need attention.
The interview mentions approximately 7,000 GitHub stars, more than 10,000 Docker image pulls and over 40,000 cloud applications, summarized as more than 50,000 applications. An image packages software for deployment. A pull is not established here as a distinct, continuously active production installation. Stars may also represent bookmarks: someone finds a project impressive, clicks and leaves.
Luyu suggests comparing image or package downloads and search trends. Editorial interpretation: These signals help identify developer interest, but further questions remain: has an application entered real work, how many users return, who handles failures and does it earn revenue? Different measurement layers cannot substitute for one another. Extending attention from building to maintaining is central to Dify’s proposition at the time.
2. Identify whether instructions, information or default behavior are missing
Episode reference: 07:48–15:19. The discussion introduces three engineering routes. A prompt supplies instructions, such as correcting grammar or classifying sentiment. Retrieval augmentation finds relevant material before answering and gives it to the model alongside the question. Fine-tuning uses training examples to adjust default behavior, such as producing poetry closer to a desired style.
The example asks which projects Qu Kai worked on that year. The model lacks private or recent information, so the system retrieves project material and constructs a fuller question. Terminology matters: embedding converts content into vector representations suitable for comparison. Retrieval, selection and context assembly form the larger process; embedding alone does not mean inserting material into a prompt.
An 8K context budget, discussed as a contemporary example, must accommodate the user’s question, retrieved material, conversation history and expected output. The enduring issue is which information deserves space and which essential conditions might be omitted. Having another model summarize first also requires checking whether compression loses meaning.
Few-shot prompting supplies a small set of examples. Asking for an appropriate style and showing acceptable outputs constrain execution differently. The interview’s sample and computing requirements for fine-tuning are historical experience, not a universal cost formula. Editorial interpretation: Write down the failure before choosing the repair: incorrect facts, misunderstood instructions and unstable style may call for different interventions.
3. An agent depends on reliable connections between actions
Episode reference: 15:47–23:04. An agent here uses a model, context and tools to take successive actions toward a goal. Booking a flight requires obtaining conditions, checking results and continuing under rules. The conversation distinguishes predefined orchestration, full autonomy and a mixture, proposing that successful action sequences can be saved as repeatable workflows.
This connects exploration with stable execution, although a sequence that succeeds once must still survive changing conditions. Luyu identifies context, reasoning quality and tool quality as constraints. In an API testing example, interface descriptions were too long and could be cut off, so the team tried a more compact representation. A failure may lie in the tool description the model receives.
Editorial interpretation: Ask to see a task trace: what information entered each step, which tool was selected, what it returned and where the process diverged. Conversational claims that a whole software project must enter context at once, or explanations about text weighting, should not become universal technical laws. Larger windows and shorter prompts still require checking results.
4. Prompt workspaces and model neutrality must reduce the cost of change
Episode reference: 23:20–27:29 and 30:14–45:40. Luyu argues that prompting’s potential and difficulty are both underestimated. The proposed workspace resembles an IDE, an integrated environment for editing and debugging software: developers compare prompt variants and models against expected results. Templates should be adapted to models, rather than support consisting only of a name on a menu.
An application may use different models for generation, reasoning, vector retrieval and speech recognition. Dify wants to separate model and prompt choices from business code, reducing the disruption of changing a supplier. Neutrality has a concrete user benefit in lower switching costs; whether it becomes a durable business advantage is a separate judgment.
The discussion describes LangChain as a code toolbox and practical textbook, LangSmith as a tool for tracing each step’s inputs and outputs, and Dify as an integrated product with operational tools. Luyu’s criticism that deeper LangChain applications become fragile or require rewriting is a competitor’s observation from 2023, not a current selection recommendation.
Editorial interpretation: A central difference between an integrated platform and self-assembly is who maintains interfaces, information, prompts and debugging. The team also considers offering useful components separately for use with other frameworks. Compare products through an actual change: replace a model, update a document or exchange a tool. Who must modify what, and do existing tasks still work?
5. Decompose a job to discover what can be delivered now
Episode reference: 36:32–38:20, 46:04–50:42 and 59:07–01:12:30. Private knowledge needs continuing updates, segmentation and weighting; tools and call limits also need maintenance. Two AI specialists cannot permanently supply every business judgment in a company.
Examples include educational feedback, administration, marketing and customer service. Suggesting improvements to an essay differs from producing a trustworthy precise score. Understanding an order and a customer’s mood differs from being authorized to issue a refund. The guests are optimistic about these directions but provide no independent outcome evaluation.
The team describes dividing growth work into twenty or thirty smaller activities and selecting those suited to contemporary model capabilities. In the closing discussion, Qu Kai applies this to requirements: use existing capabilities carefully and define a deliverable problem. Speed can follow from clearer understanding and relevant experience rather than skipping foundational work.
A future with few interfaces and many specialist agents, multimodal models, small local models and AI-readable publishing remains a set of directional scenarios. Vectorizing material does not grant usage rights. Copyright and permissions for rewritten work remain explicitly unresolved. These ideas generate research questions; they do not supply delivery evidence.
Test the method with one customer-service task
This is an editorial exercise, not a published Dify acceptance protocol. Choose a bounded task, such as drafting a response from an order and a return policy. Write an acceptable answer first, then test ordinary cases, outdated information and missing information.
| Change | What to observe | Decision to preserve |
|---|---|---|
| Update the return policy | Does the response use the new conditions, and can the old version be traced? | Who confirms that information is effective |
| Replace the model | How do correctness, waiting time and cost change on the same cases? | When switching is allowed |
| Connect a refund tool | Are proposed replies and executed actions recorded separately? | Where authorization or human takeover is required |
The exercise turns a runnable demonstration into assessable results and gives business colleagues a concrete maintenance role. Claims that Dify saved one or two development months are the team’s contemporary observations. A project should still measure prototyping, debugging and continuing operation separately.
Listening guide and related reading
- 00:34: Continuing operation and the people involved in LLMOps.
- 07:07: Choosing instructions, information and fine-tuning.
- 15:48: Agent forms and reliability problems.
- 23:20: Prompt workspaces and expected answers.
- 38:55: Libraries, debugging tools and integrated products.
- 48:23: Turning parts of a job into applications.
- 01:08:49: Qu Kai’s investment view of intermediate platforms.
Related themes: agent architecture, minimum deliverable tasks and open-source product metrics. Compare Monica founder Xiao Hong on AI assistants to examine how engineering tools and end-user products define value differently.
Source boundary: Reorganized from the complete supplied transcript, official episode introduction and existing close reading; audio was not checked sentence by sentence. Many exchanges were incorrectly combined under the host in transcription, so this article summarizes by context and avoids invented direct quotations. Names follow official metadata. Scale, efficiency, competitive assessments and predictions remain attributed to the 2023 discussion, are not independently verified and do not establish Dify’s current capabilities.