[
  {
    "notice": "只有 title 和 text 字段是必填，其他字段可删除不填。填写时，请从第三条数据开始填写，第二条数据是示例，填写完成之后，不要删除前面两条",
    "notice1": "只有 title 和 text 字段是必填，其他字段可删除不填。填写时，请从第三条数据开始填写，第二条数据是示例，填写完成之后，不要删除前面两条",
    "notice2": "只有 title 和 text 字段是必填，其他字段可删除不填。填写时，请从第三条数据开始填写，第二条数据是示例，填写完成之后，不要删除前面两条",
    "title": "这里填标题，必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填",
    "titleTranslate": "这里填标题翻译",
    "text": "这里填原文，一句一个换行符，一段两个换行符，必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填",
    "textTranslate": "这里填原文翻译，一句一个换行符，一段两个换行符",
    "audioSrc": "这里填音频的url/在线地址"
  },
  {
    "title": "How are you today?",
    "titleTranslate": "今天好吗？",
    "text": "STEVEN:Hello, HELEN.\n\nHELEN:Hi, Steven.\n\nSTEVEN:How are you today?\n\nHELEN:I'm very well, thank you. And you?\n\nSTEVEN:I'm fine, thanks.\n\nSTEVEN:How is Tony?\n\nHELEN:He's fine, thanks. How's Emma?\n\nSTEVEN:She's very well, too, Helen.\n\nSTEVEN:Goodbye, Helen.Nice to see you.\n\nHELEN:Nice to see you, too, Steven. Goodbye.",
    "textTranslate": "史蒂文：你好，海伦 \n\n海 伦：你好，史蒂文 \n\n史蒂文：你今天好吗？ \n\n海 伦：很好，谢谢你。你好吗？ \n\n史蒂文：很好，谢谢。 \n\n史蒂文：托尼好吗？ \n\n海 伦：他很好，谢谢。埃玛好吗？ \n\n史蒂文：她也很好，海伦。 \n\n史蒂文：再见，海伦。见到你真高兴。 \n\n海 伦：我见到你也很高兴，史蒂文。再见。",
    "audioSrc": "/sound/article/nce1/009&010－How Are You Today.mp3"
  },
  {
    "title": "01A The Work I Do",
    "titleTranslate": "第01课A｜我是谁，我在做什么",
    "text": "I work on several software projects, and most of them begin with a problem that I understand from experience.\nOne project helps people learn a language, while another helps visitors discover useful tools and compare different products.\nAlthough the projects serve different audiences, I usually describe my role in the same simple way.\nI turn ideas into practical features, review the results, and decide what the team should work on next.\nI use AI assistants during development, but I still need to understand the decisions that affect the final product.\nAn assistant can suggest an approach or explain a function, and I provide the goal and the relevant context.\nWhen someone asks what I do, I avoid listing every framework, service, and package that I use.\nInstead, I explain who the product is for and how it helps people complete a particular task.\nThis introduction gives the other person a clear picture before we discuss any technical details or future plans.\nI do not need to sound like an expert in everything; I need to describe my work accurately and clearly.\nI can discuss a technical detail later, once the other person understands the ordinary activity that the product supports.",
    "textTranslate": "我同时做几个软件项目，其中大多数源于我亲身遇到的问题。\n一个项目帮助人们学习语言，另一个帮助访客发现实用工具并比较产品。\n虽然项目服务不同受众，我通常以相同的简单方式介绍自己的角色。\n我把想法变成实用功能，检查结果，并决定团队下一步做什么。\n开发过程中我使用AI助手，但仍需理解影响最终产品的决定。\n助手可以建议方案或解释函数，我则提供目标和相关背景。\n有人问我做什么时，我不会罗列用到的每个框架、服务和软件包。\n我会说明产品服务谁，以及它怎样帮助人们完成某项任务。\n这样在讨论技术细节或未来计划前，对方就有了清晰认识。\n我不必听起来像无所不知的专家，只需准确清楚地描述工作。\n对方理解产品支持的普通活动后，我再讨论技术细节。"
  },
  {
    "title": "01B Introducing a Project to Someone New",
    "titleTranslate": "第01课B｜我是谁，我在做什么",
    "text": "A clear project introduction answers three questions: who uses the product, what they do with it, and why it matters.\nImagine that I meet a teacher who wants to know more about the language website I am developing.\nI begin with the audience and say that the site helps adults practice Chinese through short lessons and useful conversations.\nThen I describe one ordinary activity, such as reading a story, saving an unfamiliar word, or reviewing yesterday's vocabulary.\nThese examples explain the purpose more effectively than a long list of technical names or complicated product claims.\nIf the teacher asks about my responsibilities, I explain that I organize the content and guide the development work.\nOther people may help with design, teaching, or engineering, and I make their different contributions clear as well.\nI also mention the current stage, because an early experiment and an established service create very different expectations.\nBefore ending the conversation, I ask what the teacher finds useful and what information is still missing from my explanation.\nTheir questions help me improve both the introduction and my understanding of the people who might use the product.\nA short and honest explanation also makes it easier for someone to introduce the project accurately to another interested person.",
    "textTranslate": "清晰的项目介绍回答三个问题：谁使用、用来做什么，以及它为何重要。\n假设我遇到一位老师，想了解我正在开发的语言网站。\n我先说明受众：网站帮助成年人通过短课和实用对话练习中文。\n然后介绍一个日常活动，比如读故事、保存生词或复习昨天的词汇。\n这些例子比一长串技术名称或复杂宣传更能解释用途。\n如果老师问我负责什么，我会说明我组织内容并指导开发工作。\n其他人可能帮助设计、教学或工程开发，我也会说明各自的贡献。\n我还会说明当前阶段，因为初期实验和成熟服务带来的预期完全不同。\n结束前，我会问老师觉得什么有用，以及介绍中还缺少哪些信息。\n对方的问题既帮助我改进介绍，也帮助我理解潜在用户。\n简短诚实的说明也让别人更容易把项目准确介绍给其他感兴趣者。"
  },
  {
    "title": "01C Working Conversation",
    "titleTranslate": "第01课C｜我是谁，我在做什么",
    "text": "Colleague: What do you work on at the moment, and how would you describe your role to someone outside your team?\nMe: I develop small software products, and I usually organize the requirements, review the results, and decide what we should improve next.\nColleague: Who uses your language website, and what does an ordinary learning session look like for a new visitor?\nMe: It is for adults learning Chinese; they can read a lesson, practice useful sentences, and save vocabulary for later review.\nColleague: Do you build everything yourself, or do other people and AI assistants help with parts of the work?\nMe: I use AI assistants for development and explanations, but I review the important decisions and remain responsible for the final result.\nColleague: That sounds clear; could you show me one example so I can understand the product from a learner's point of view?\nMe: Certainly; let us open a short lesson together, and I will explain what the learner can do at each step.",
    "textTranslate": "同事：你目前做什么，怎样向团队外的人介绍自己的角色？\n我：我开发小型软件产品，通常负责整理需求、检查结果并决定下一步改进。\n同事：谁使用你的语言网站，新访客通常怎样学习？\n我：面向学习中文的成年人，可以读课文、练句子并保存词汇复习。\n同事：你独自完成全部工作，还是也有他人和AI助手参与？\n我：我使用AI助手开发和解释，但会检查重要决定，并对最终结果负责。\n同事：很清楚，能展示一个例子，让我从学习者角度理解吗？\n我：当然，我们一起打开一节短课，我会解释学习者每一步能做什么。"
  },
  {
    "title": "01D Sentence Review",
    "titleTranslate": "第01课D｜我是谁，我在做什么",
    "text": "I work on several software projects, and most of them begin with a problem that I understand from experience.\nAlthough the projects serve different audiences, I usually describe my role in the same simple way.\nI use AI assistants during development, but I still need to understand the decisions that affect the final product.\nInstead, I explain who the product is for and how it helps people complete a particular task.\nA clear project introduction answers three questions: who uses the product, what they do with it, and why it matters.\nI begin with the audience and say that the site helps adults practice Chinese through short lessons and useful conversations.\nIf the teacher asks about my responsibilities, I explain that I organize the content and guide the development work.\nBefore ending the conversation, I ask what the teacher finds useful and what information is still missing from my explanation.\nWhat do you work on at the moment, and how would you describe your role to someone outside your team?\nWho uses your language website, and what does an ordinary learning session look like for a new visitor?\nDo you build everything yourself, or do other people and AI assistants help with parts of the work?\nThat sounds clear; could you show me one example so I can understand the product from a learner's point of view?",
    "textTranslate": "我同时做几个软件项目，其中大多数源于我亲身遇到的问题。\n虽然项目服务不同受众，我通常以相同的简单方式介绍自己的角色。\n开发过程中我使用AI助手，但仍需理解影响最终产品的决定。\n我会说明产品服务谁，以及它怎样帮助人们完成某项任务。\n清晰的项目介绍回答三个问题：谁使用、用来做什么，以及它为何重要。\n我先说明受众：网站帮助成年人通过短课和实用对话练习中文。\n如果老师问我负责什么，我会说明我组织内容并指导开发工作。\n结束前，我会问老师觉得什么有用，以及介绍中还缺少哪些信息。\n同事：你目前做什么，怎样向团队外的人介绍自己的角色？\n同事：谁使用你的语言网站，新访客通常怎样学习？\n同事：你独自完成全部工作，还是也有他人和AI助手参与？\n同事：很清楚，能展示一个例子，让我从学习者角度理解吗？"
  },
  {
    "title": "01E Vocabulary in Context",
    "titleTranslate": "第01课E｜我是谁，我在做什么",
    "text": "The new colleague is engaged in research involving a language model, and the team is united around one clear goal.\nAn agent can provide assistance, while several agents may divide a larger task into clearly assigned areas.\nThe engineer and the manager welcomed a new member during the team meeting at the office.\nOur identity as a small business comes from the useful work we do, rather than an impressive job title.\nThe guest said hello, and I replied, \"Hi, welcome; I am happy to show you around.\"\nA friendly \"hey\" suits some chats, while a formal introduction is more appropriate when meeting a new client.\nThe producer and the publisher have different responsibilities, even when both work for the same organization.\nSeveral companies have built useful products, and their teams have worked across different markets for years.\nThe providers are known for their technical skill, and their support teams have genuinely helped us.\nThe same word may describe a human worker or a background worker in a software system.\nI loved the clear explanation, and I believe the same approach will help other non-native speakers.",
    "textTranslate": "新同事参与语言模型研究，团队围绕明确目标团结协作。\n一个智能体可以协助，多个智能体可分担明确划分的任务领域。\n工程师和管理者在办公室团队会议上欢迎新成员。\n我们作为小企业的身份来自有用工作，而非漂亮头衔。\n来宾问好，我回应欢迎并表示高兴带他参观。\n友好的hey适合一些聊天，正式介绍更适合见新客户。\n制作者与发行者即使在同一组织，职责也不同。\n多家公司已开发有用产品，团队跨市场工作多年。\n这些服务商以技术技能闻名，支持团队确实帮过我们。\n同一个词可描述人类工作者或软件后台工作进程。\n我很喜欢清晰解释，相信同样方法有助其他非母语者。"
  },
  {
    "title": "02A A Small Plan for Each Day",
    "titleTranslate": "第02课A｜我的习惯与工作安排",
    "text": "I usually begin my working day by reviewing the notes that I wrote at the end of the previous session.\nThis short review helps me remember what is complete, what needs attention, and which task has the highest priority.\nI choose one clear goal for the morning instead of making a long list that I cannot realistically finish.\nAfter that, I open the project, check the current state, and prepare the materials I need for the first task.\nI often work in short sessions because a natural pause gives me a chance to review the direction before continuing.\nDuring a break, I write down questions rather than switching immediately to a different project or an unrelated issue.\nIn the afternoon, I usually test the result with an ordinary example and compare it with the original goal.\nIf the task is taking longer than expected, I reduce its scope and leave a clear note about the remaining work.\nBefore I finish, I save the useful observations and decide where the next working session should begin.\nA simple routine does not solve every problem, but it makes it easier to return to a project with a clear mind.\nThe notes can be brief, as long as the next action is clear.",
    "textTranslate": "我通常先查看上次工作结束时写的笔记，再开始一天的工作。\n简短回顾帮助我记起已完成内容、待处理事项和最高优先级任务。\n我为上午选择一个明确目标，而不列出实际上做不完的长清单。\n之后打开项目、检查状态，并准备第一个任务需要的材料。\n我经常分短时段工作，因为暂停能让我在继续之前检查方向。\n休息时我记录问题，而不是立即切换到别的项目或无关事项。\n下午通常用普通例子检查结果，并与最初目标比较。\n任务超时的话，我会缩小范围，并记录剩余工作。\n结束前，我保存有用的观察，并确定下次从哪里开始。\n简单习惯解决不了所有问题，但能让我更清醒地回到项目中。\n笔记可以简短，只要下一动作清楚。"
  },
  {
    "title": "02B What I Am Working on This Week",
    "titleTranslate": "第02课B｜我的习惯与工作安排",
    "text": "This week I am preparing the first part of a new learning course and checking how the exercises work in practice.\nI normally write short lessons, but this course needs longer reading materials and a more careful vocabulary plan.\nAt the moment, I am organizing the words into themes rather than arranging them only in alphabetical order.\nThe first theme introduces projects and working habits, while later themes cover questions, changes, problems, and professional communication.\nEvery morning I review one section, and today I am checking whether the examples are natural enough to say aloud.\nSome sentences look correct on the page but feel awkward when I try to use them in a real conversation.\nI am also preparing a small set of practice files so that I can try the materials before sharing the full course.\nMy regular habit is to make a plan first, but I change that plan when the actual results suggest a better approach.\nThe important difference is between what I usually do and what I am doing during this particular period of work.\nKeeping both ideas clear helps me explain my progress without making a temporary activity sound like a permanent responsibility.\nI review the schedule again when the priorities change.",
    "textTranslate": "这周我在准备新课程的第一部分，并检查练习的实际效果。\n我平时写短课，但这套课程需要更长的阅读材料和更细致的词汇计划。\n目前我在按主题组织词汇，而不是只按字母顺序排列。\n第一主题介绍项目和工作习惯，后面涉及提问、修改、问题和职业沟通。\n每天上午我复习一部分，今天检查例句是否自然、适合说出口。\n有些句子纸面上正确，实际交谈时却显得别扭。\n我还在制作少量练习文件，以便分享完整课程前试用材料。\n我习惯先制定计划，但实际结果显示有更好方法时也会调整。\n重要的是区分平时经常做什么，与当前这段时间正在做什么。\n区分二者有助于汇报进度，避免把临时活动说成长期职责。\n优先级变化时，我会重新检查日程。"
  },
  {
    "title": "02C Working Conversation",
    "titleTranslate": "第02课C｜我的习惯与工作安排",
    "text": "Partner: How do you normally organize your mornings when there are several projects waiting for attention at the same time?\nMe: I usually review my notes, choose one main goal, and finish a small piece of work before opening another project.\nPartner: What are you working on today, and is it different from the tasks you handle during an ordinary week?\nMe: Today I am preparing course materials, although I normally spend more time reviewing features and improving the website itself.\nPartner: Do you need to complete the whole course this morning, or can you divide the work into smaller sessions?\nMe: I can divide it into smaller sessions; this morning I am checking one lesson and writing down the remaining questions.\nPartner: When will you return to the other project, and how will you remember exactly where you stopped working yesterday?\nMe: I will review it tomorrow afternoon, and the notes from the previous session will show me the next practical step.",
    "textTranslate": "伙伴：几个项目同时需要处理时，你通常怎样安排上午？\n我：通常看笔记、选一个主要目标，先完成一小部分工作再打开别的项目。\n伙伴：今天在做什么，和普通一周的任务不同吗？\n我：今天准备课程材料，平时更多时间用于检查功能和改进网站。\n伙伴：需要今天上午完成整套课程，还是可以分成短时段？\n我：可以分段，今天上午检查一课并记录剩余问题。\n伙伴：什么时候回到另一个项目，怎样记起昨天停在哪里？\n我：明天下午处理，上次笔记会告诉我下一步。"
  },
  {
    "title": "02D Sentence Review",
    "titleTranslate": "第02课D｜我的习惯与工作安排",
    "text": "I usually begin my working day by reviewing the notes that I wrote at the end of the previous session.\nI choose one clear goal for the morning instead of making a long list that I cannot realistically finish.\nI often work in short sessions because a natural pause gives me a chance to review the direction before continuing.\nIf the task is taking longer than expected, I reduce its scope and leave a clear note about the remaining work.\nThis week I am preparing the first part of a new learning course and checking how the exercises work in practice.\nAt the moment, I am organizing the words into themes rather than arranging them only in alphabetical order.\nSome sentences look correct on the page but feel awkward when I try to use them in a real conversation.\nThe important difference is between what I usually do and what I am doing during this particular period of work.\nHow do you normally organize your mornings when there are several projects waiting for attention at the same time?\nWhat are you working on today, and is it different from the tasks you handle during an ordinary week?\nDo you need to complete the whole course this morning, or can you divide the work into smaller sessions?\nWhen will you return to the other project, and how will you remember exactly where you stopped working yesterday?",
    "textTranslate": "我通常先查看上次工作结束时写的笔记，再开始一天的工作。\n我为上午选择一个明确目标，而不列出实际上做不完的长清单。\n我经常分短时段工作，因为暂停能让我在继续之前检查方向。\n任务超时的话，我会缩小范围，并记录剩余工作。\n这周我在准备新课程的第一部分，并检查练习的实际效果。\n目前我在按主题组织词汇，而不是只按字母顺序排列。\n有些句子纸面上正确，实际交谈时却显得别扭。\n重要的是区分平时经常做什么，与当前这段时间正在做什么。\n伙伴：几个项目同时需要处理时，你通常怎样安排上午？\n伙伴：今天在做什么，和普通一周的任务不同吗？\n伙伴：需要今天上午完成整套课程，还是可以分成短时段？\n伙伴：什么时候回到另一个项目，怎样记起昨天停在哪里？"
  },
  {
    "title": "02E Vocabulary in Context",
    "titleTranslate": "第02课E｜我的习惯与工作安排",
    "text": "The routine is basically simple: save your work, note the next step, and pick it up again when you return.\nPicking a regular time helps the habit fit into everyday life, and the exercise can be done anywhere with a suitable device.\nThe monthly report appears at the end of each month, while the full review takes place annually.\nAfter waking, I spend a few minutes walking before I begin the first session of the day.\nThe update came earlier than expected, but the older notes still describe the previous routine.\nI have gone back to the schedule and taken another look at the tasks that remain unfinished.\nThe planning session ended quickly, and the time saved made the next round of work easier.\nWe are transitioning to a shorter routine, but the change should not reduce the total time spent on useful practice.\nA clear schedule greatly improves efficiency, especially when the team works across several time zones.\nThe next two sessions are worth keeping short so that we can reflect before continuing.",
    "textTranslate": "流程基本简单：保存工作、记下一步，回来后接着做。\n固定时间帮助习惯融入日常，设备合适即可随处练习。\n月报每月末发布，完整评审每年一次。\n醒来后，我先步行几分钟再开始当天首段工作。\n更新比预期早到，但旧笔记仍描述此前习惯。\n我已回看时间表，再检查剩余任务。\n计划会很快结束，节省时间让下一轮工作更容易。\n我们正改用更短日程，但不应减少有效练习总时间。\n清晰排期极大提高效率，尤其团队跨多个时区时。\n接下来两段值得缩短，让我们继续前能反思。"
  },
  {
    "title": "03A Explaining What a Product Does",
    "titleTranslate": "第03课A｜描述一个产品",
    "text": "A product description should help someone imagine a useful activity, rather than simply introduce a collection of impressive technical features.\nOur example product is a small learning website for adults who want to practice language skills during a busy day.\nThere is a short introduction on the home page, and there are several lessons that visitors can explore without creating an account.\nEach lesson includes a reading passage, a conversation, a vocabulary list, and a few exercises with clear answers.\nThe main value is the connection between understanding an expression and using it to complete a familiar task.\nFor example, a learner can read about changing a page and then practice making the same request in English.\nThe website does not need a complicated interface to deliver that value, but it does need accurate and accessible content.\nWe explain the available functions with ordinary verbs such as read, listen, save, review, and practice.\nWhen a visitor understands these actions, it becomes easier to choose a lesson and begin a meaningful learning session.\nA good description therefore connects the audience, the activity, and the benefit in language that a new user can understand.\nThe explanation should remain useful even when the visitor has no technical background.",
    "textTranslate": "产品说明应帮助人们想象有用的活动，而不只是介绍一组漂亮的技术功能。\n示例产品是面向忙碌成年人、帮助练习语言技能的小网站。\n首页有简短介绍，访客不用建账号就能浏览几节课。\n每课包含阅读文章、对话、词汇表以及答案明确的练习。\n主要价值是把理解表达与用表达完成熟悉任务联系起来。\n例如学习者读完页面修改文章后，可以练习用英语提出相同请求。\n网站无需复杂界面来提供价值，但内容必须准确且易于获取。\n我们用阅读、聆听、保存、复习和练习等普通动词解释功能。\n访客理解这些操作后，更容易选择课程并开始有效学习。\n好的说明把受众、活动和收益用新用户能懂的语言连接起来。\n即使访客没有技术背景，说明也应有用。"
  },
  {
    "title": "03B A Visitor's First Session",
    "titleTranslate": "第03课B｜描述一个产品",
    "text": "Imagine that a new visitor opens the learning website during a short break and has only fifteen minutes to study.\nThe visitor does not know our course names, so the first page needs to explain which lesson offers a suitable starting point.\nThere is a brief goal above each lesson, and a sample sentence shows the kind of expression the visitor will practice.\nAfter choosing a lesson, the visitor reads the English passage and checks the Chinese explanation whenever an unfamiliar expression appears.\nA vocabulary section provides a few useful meanings, while the examples show how the same words work in different situations.\nThe visitor can then move to a short exercise and try to produce a complete sentence without looking at the original.\nIf an answer is difficult, there is a reference version to compare with the visitor's own attempt and improve it.\nThis first session should end with a small achievement, such as describing a project or asking a clear question.\nWe can evaluate the product by asking whether the visitor understands the next step and finds the material useful.\nThe number of features matters less than the quality of this ordinary experience, especially when the product is still young.",
    "textTranslate": "想象新访客在短暂休息时打开学习网站，只有十五分钟学习。\n访客不了解课程名称，所以首页要说明哪课适合作为起点。\n每课上方有简短目标，示例句展示将要练习的表达。\n选择课程后，访客阅读英文，并在遇到陌生表达时查看中文解释。\n词汇部分提供实用释义，例句展示同一词在不同情境的用法。\n之后访客可以做短练习，不看原文尝试说出完整句子。\n回答有难度时，可以对照参考答案改进自己的表达。\n第一次学习应以小成果结束，比如介绍项目或清楚提问。\n我们可以询问访客是否知道下一步、材料是否有用，以评估产品。\n产品处于早期时，日常体验质量比功能数量更重要。"
  },
  {
    "title": "03C Working Conversation",
    "titleTranslate": "第03课C｜描述一个产品",
    "text": "Visitor: I have a few minutes to study, but I do not know which lesson to choose or what the website offers.\nGuide: Start with the first lesson; there is a short introduction, a useful reading passage, and a conversation about everyday project work.\nVisitor: Do I need to create an account before I can read the passage and look at the vocabulary explanations?\nGuide: No, the sample content is available without an account, so you can explore the learning approach before making that decision.\nVisitor: What should I be able to do after the lesson, apart from recognizing a list of new English words?\nGuide: You should be able to introduce a small project and explain your usual working habits in several clear sentences.\nVisitor: That sounds useful; is there an exercise where I can try to say the same thing about my own project?\nGuide: Yes, there are questions at the end, and you can compare your answers with reference expressions after trying them yourself.",
    "textTranslate": "访客：我有几分钟学习，但不知道选哪课，也不清楚网站提供什么。\n引导者：从第一课开始，里面有介绍、实用阅读和日常项目工作对话。\n访客：阅读文章和看词汇解释前，需要建账号吗？\n引导者：不需要，示例内容无需账号，你可以先体验学习方式。\n访客：除了认出一批生词，学完应该能做什么？\n引导者：你应该能用几句清晰的话介绍小项目并解释工作习惯。\n访客：听起来有用，有练习让我介绍自己的项目吗？\n引导者：有，末尾有问题，自己尝试后可以对照参考表达。"
  },
  {
    "title": "03D Sentence Review",
    "titleTranslate": "第03课D｜描述一个产品",
    "text": "A product description should help someone imagine a useful activity, rather than simply introduce a collection of impressive technical features.\nThere is a short introduction on the home page, and there are several lessons that visitors can explore without creating an account.\nThe main value is the connection between understanding an expression and using it to complete a familiar task.\nWe explain the available functions with ordinary verbs such as read, listen, save, review, and practice.\nImagine that a new visitor opens the learning website during a short break and has only fifteen minutes to study.\nThere is a brief goal above each lesson, and a sample sentence shows the kind of expression the visitor will practice.\nThe visitor can then move to a short exercise and try to produce a complete sentence without looking at the original.\nWe can evaluate the product by asking whether the visitor understands the next step and finds the material useful.\nI have a few minutes to study, but I do not know which lesson to choose or what the website offers.\nDo I need to create an account before I can read the passage and look at the vocabulary explanations?\nWhat should I be able to do after the lesson, apart from recognizing a list of new English words?\nThat sounds useful; is there an exercise where I can try to say the same thing about my own project?",
    "textTranslate": "产品说明应帮助人们想象有用的活动，而不只是介绍一组漂亮的技术功能。\n首页有简短介绍，访客不用建账号就能浏览几节课。\n主要价值是把理解表达与用表达完成熟悉任务联系起来。\n我们用阅读、聆听、保存、复习和练习等普通动词解释功能。\n想象新访客在短暂休息时打开学习网站，只有十五分钟学习。\n每课上方有简短目标，示例句展示将要练习的表达。\n之后访客可以做短练习，不看原文尝试说出完整句子。\n我们可以询问访客是否知道下一步、材料是否有用，以评估产品。\n访客：我有几分钟学习，但不知道选哪课，也不清楚网站提供什么。\n访客：阅读文章和看词汇解释前，需要建账号吗？\n访客：除了认出一批生词，学完应该能做什么？\n访客：听起来有用，有练习让我介绍自己的项目吗？"
  },
  {
    "title": "03E Vocabulary in Context",
    "titleTranslate": "第03课E｜描述一个产品",
    "text": "The most popular feature lets users search the web using keywords, while a flag identifies each saved result.\nThe news page shows a short breakdown of the latest changes, including the contents of each release.\nThe free demo lets a new user explore the dashboard before choosing one of the paid pricing tiers.\nThe catalog divides the available apps into categories, and each category has a short description.\nThese startups serve different audiences, and their brands communicate different promises about the same kind of product.\nA strong brand does not replace a useful product, but it can make a clear benefit easier to remember.\nThe application shows a profile, an account overview, and several collections of saved items.\nAn amount billed to an account should match the selected plan and the rate displayed before purchasing.\nA public listing may include a brief explainer and a link to the publisher's official website.\nThe home page describes the main value briefly, while further details are available on the individual product pages.",
    "textTranslate": "最受欢迎功能让用户用关键词搜网页，标记识别保存结果。\n新闻页简述最新改动，包含各版本内容。\n免费演示让新用户选付费档位前浏览仪表盘。\n目录把应用分成类别，每类有简述。\n这些初创公司服务不同受众，品牌对同类产品作不同承诺。\n强品牌不能替代有用产品，但让收益更易记。\n应用展示资料页、账号概览和几组已保存条目。\n账号账单金额应与所选套餐及购买前显示费率一致。\n公开收录可含简短说明及发布者官网链接。\n首页简述主要价值，产品页提供进一步细节。"
  },
  {
    "title": "04A Defining the First Useful Version",
    "titleTranslate": "第04课A｜说清楚我想要什么",
    "text": "Before I ask someone to build a feature, I need to describe the result that I want a user to achieve.\nFor a content tool, the goal might be to find relevant posts, prepare a reply, and choose a suitable publishing time.\nThese activities form the core workflow, and every additional requirement should have a clear connection to that practical goal.\nI would like the first version to support account connections and scheduling, but I do not need advanced reports immediately.\nThe difference between a necessary function and an interesting extra becomes important when time and attention are limited.\nI write the requirements as observable actions so that another person can tell when the work is complete.\nFor example, a user should be able to select a date and save a post without publishing it immediately.\nWe must also explain the limits, including which accounts are supported and what happens when an external service is unavailable.\nClear limits make the first version easier to review and reduce the chance of different people imagining different products.\nI can always expand the scope later, after the basic workflow has proved useful in real situations and ordinary daily tasks.\nA clear example makes those boundaries easier for everyone to understand.",
    "textTranslate": "请别人开发功能前，我需要说明希望用户取得的结果。\n内容工具的目标可能是找相关帖子、准备回复并选择发布时间。\n这些活动构成核心流程，每项额外需求都应与实际目标清楚关联。\n我希望第一版支持账号连接和排期，但不需要立即提供高级报告。\n时间和精力有限时，必要功能与有趣附加项的区别很重要。\n我把需求写成可观察动作，让别人知道何时算完成。\n例如用户应该能选择日期并保存帖子，而不立即发布。\n我们也必须说明限制，包括支持哪些账号及外部服务不可用时会怎样。\n清晰边界让初版更易检查，减少不同人想象不同产品的机会。\n基本流程在真实场景和日常任务中证明有用后，我可以再扩大范围。\n清晰例子让所有人更易理解边界。"
  },
  {
    "title": "04B Keeping the Scope Clear",
    "titleTranslate": "第04课B｜说清楚我想要什么",
    "text": "A request can sound simple while leaving several important decisions hidden, especially when it uses broad words such as improve or automate.\nIf I say that a tool should automate content, someone still needs to know which actions the tool should actually perform.\nShould it suggest topics, write complete posts, schedule approved content, or publish without asking for a final review first?\nI separate these choices and describe what belongs in the first release, what can wait, and what requires a human decision.\nI also distinguish between things the system can do and things it is allowed to do on someone's behalf.\nA feature may be technically possible without being necessary for the current goal or appropriate for the current audience.\nWhen the scope is written clearly, it becomes easier to ask focused questions instead of repeatedly changing the entire plan.\nA useful requirement might say that the application can save a draft but must not publish it until the user confirms.\nThis statement gives us a visible action, a meaningful limit, and a practical way to review whether the implementation is correct.\nThe first release does not need every possible function; it needs enough carefully chosen functions to support one complete and useful workflow.",
    "textTranslate": "请求使用改进或自动化等宽泛词时，听起来简单却可能隐藏重要决定。\n如果我说工具应该自动处理内容，仍需说明它具体执行哪些动作。\n它应建议话题、撰写整篇帖子、排期已批准内容，还是不经最终审阅直接发布？\n我拆开这些选择，说明首发包含什么、什么能等、什么需要人工决定。\n我也区分系统能够做什么，以及获准代表他人做什么。\n功能技术上可行，不代表符合当前目标或受众需要。\n范围写清楚后，就更容易集中提问，不用反复修改整个计划。\n实用需求可以写成：应用能保存草稿，但用户确认前不得发布。\n这句话提供可见操作、有意义限制，以及检查实现是否正确的方法。\n首发不必拥有所有可能功能，只需精心选择足够功能支撑一条完整实用流程。"
  },
  {
    "title": "04C Working Conversation",
    "titleTranslate": "第04课C｜说清楚我想要什么",
    "text": "Builder: You asked for a content tool; could you explain the main result you want a user to achieve in the first version?\nOwner: I want users to find relevant posts, connect an account, prepare content, and choose when an approved post should be published.\nBuilder: Should the application write everything automatically, or do you want people to review the content before it becomes public?\nOwner: People must review it first; the tool should save drafts and handle scheduling, but it must not make that final decision.\nBuilder: Do we need detailed reports in the initial release, or can we leave that work until the basic workflow is useful?\nOwner: We can leave reports for later; I would rather finish a complete small workflow than add several features that remain unfinished.\nBuilder: I will write down these requirements and explain the limits before implementing the first feature or connecting any external accounts.\nOwner: Good; please include a concrete example so that we can check the result against the same clear expectations at the end.",
    "textTranslate": "开发者：你想做内容工具，能说明第一版要让用户获得什么主要结果吗？\n负责人：我希望用户找到相关帖子、连接账号、准备内容，并选择已批准帖子的发布时间。\n开发者：应用应自动写全部内容，还是要人工审阅后才能公开？\n负责人：必须先审阅，工具保存草稿并处理排期，但不作最终决定。\n开发者：初版需要详细报告吗，还是等基本流程有用再做？\n负责人：报告可以以后做，我宁愿完成小流程，也不想添加几个未完成功能。\n开发者：实现功能或连接外部账号之前，我会记录需求并解释限制。\n负责人：好，请附上具体例子，让我们最终能按同一明确预期检查。"
  },
  {
    "title": "04D Sentence Review",
    "titleTranslate": "第04课D｜说清楚我想要什么",
    "text": "Before I ask someone to build a feature, I need to describe the result that I want a user to achieve.\nThese activities form the core workflow, and every additional requirement should have a clear connection to that practical goal.\nThe difference between a necessary function and an interesting extra becomes important when time and attention are limited.\nWe must also explain the limits, including which accounts are supported and what happens when an external service is unavailable.\nA request can sound simple while leaving several important decisions hidden, especially when it uses broad words such as improve or automate.\nShould it suggest topics, write complete posts, schedule approved content, or publish without asking for a final review first?\nA feature may be technically possible without being necessary for the current goal or appropriate for the current audience.\nThis statement gives us a visible action, a meaningful limit, and a practical way to review whether the implementation is correct.\nYou asked for a content tool; could you explain the main result you want a user to achieve in the first version?\nShould the application write everything automatically, or do you want people to review the content before it becomes public?\nDo we need detailed reports in the initial release, or can we leave that work until the basic workflow is useful?\nI will write down these requirements and explain the limits before implementing the first feature or connecting any external accounts.",
    "textTranslate": "请别人开发功能前，我需要说明希望用户取得的结果。\n这些活动构成核心流程，每项额外需求都应与实际目标清楚关联。\n时间和精力有限时，必要功能与有趣附加项的区别很重要。\n我们也必须说明限制，包括支持哪些账号及外部服务不可用时会怎样。\n请求使用改进或自动化等宽泛词时，听起来简单却可能隐藏重要决定。\n它应建议话题、撰写整篇帖子、排期已批准内容，还是不经最终审阅直接发布？\n功能技术上可行，不代表符合当前目标或受众需要。\n这句话提供可见操作、有意义限制，以及检查实现是否正确的方法。\n开发者：你想做内容工具，能说明第一版要让用户获得什么主要结果吗？\n开发者：应用应自动写全部内容，还是要人工审阅后才能公开？\n开发者：初版需要详细报告吗，还是等基本流程有用再做？\n开发者：实现功能或连接外部账号之前，我会记录需求并解释限制。"
  },
  {
    "title": "04E Vocabulary in Context",
    "titleTranslate": "第04课E｜说清楚我想要什么",
    "text": "The initial release must be compliant with the agreed requirements, including any explicit limit on automated actions.\nAn auto mode may sound convenient, but users must understand which actions are automated and which require a decision.\nWe considered a different implementation, but the selected approach covers the core requirement with less complexity.\nBefore we implement an option, we should consider its effect on the whole workflow rather than one attractive feature.\nThe system allows users to set a target, and it must clearly explain what happens when they reach it.\nA bounded task has an explicit limit, while an undefined task may expand in an unintended direction.\nA non-unique name is allowed here, but this field requires a unique identifier for each record.\nWe rejected several fancy additions because the basic product did not depend on them.",
    "textTranslate": "初版必须符合约定需求，包括自动操作明确限制。\n自动模式虽方便，用户必须知道哪些操作自动、哪些需决定。\n我们考虑过另一实现，但当前方式更简单地涵盖核心需求。\n实现方案前应考虑整体流程影响，而非单个诱人功能。\n系统允许设目标，必须清楚说明达标后会怎样。\n有界任务有明确限制，未定义任务可能意外扩张。\n此处允许重名，但该字段要求每条记录标识唯一。\n我们拒绝几个花哨附加项，因为基本产品不依赖它们。"
  },
  {
    "title": "05A Asking a Question That Gets a Useful Answer",
    "titleTranslate": "第05课A｜提问与确认理解",
    "text": "A useful question gives the other person enough information to understand what I know and what I still need to learn.\nIf I only ask whether something works, the answer may be too general to help me make the next decision.\nI try to identify the specific uncertainty, such as where a setting is stored or how a service receives a request.\nThen I explain the context in one or two sentences and ask the question that matters for the current task.\nFor example, I might ask whether rebuilding a container will remove the settings that I saved during the previous session.\nThis question names the action, the information at risk, and the situation in which I need an accurate answer.\nIf the explanation contains unfamiliar language, I ask for a concrete example instead of pretending that I understand every detail.\nI can also repeat the main idea in simpler words and ask the other person to confirm whether my understanding is correct.\nA short conversation often becomes more productive when both people agree on the meaning of a few important terms.\nThe goal is to reduce uncertainty enough to act responsibly, rather than collect explanations that do not affect the next step.",
    "textTranslate": "有效的问题会提供足够信息，让对方知道我已懂什么、还需要了解什么。\n如果只问某个东西是否能用，回答可能太泛，无法帮助下一步决定。\n我会明确具体疑点，比如设置存在哪里，或服务如何接收请求。\n然后用一两句解释背景，并提出与当前任务相关的问题。\n例如我会问，重新构建容器会不会删除上次保存的设置。\n这个问题说明了动作、可能受影响的信息，以及需要准确回答的情境。\n解释中出现陌生表达时，我会要求具体例子，不假装理解全部细节。\n我也可以用简单话重述重点，请对方确认理解是否正确。\n双方就几个重要术语含义达成一致后，简短对话往往更有效。\n目标是减少不确定性，以便负责任地行动，而不只是收集无关解释。"
  },
  {
    "title": "05B Checking What Someone Means",
    "titleTranslate": "第05课B｜提问与确认理解",
    "text": "Sometimes an answer appears clear because it uses familiar words, but those words can refer to different things in different projects.\nIf someone says that the update is ready, I need to know whether it is ready for review, testing, or public use.\nI can ask a direct question, such as whether the new version has been deployed to the production environment.\nI can also ask what remains unfinished and who is expected to make the next decision before work can continue.\nThese questions prevent a small difference in interpretation from becoming a larger problem later in the process.\nWhen I request an explanation, I keep the embedded question in ordinary statement order, even if the original question uses inversion.\nFor example, I say that I want to understand how the system works, rather than putting does before its subject.\nA useful answer should distinguish what has been observed from what is still an assumption or a possible explanation.\nIf the evidence is incomplete, it is reasonable to ask what needs to be checked before we reach a firm conclusion.\nClear questions and careful confirmation help me learn the subject while keeping the project moving in a practical direction.\nThat shared understanding makes the next action more deliberate.",
    "textTranslate": "有时回答用了熟悉词，看起来清楚，但不同项目里的含义可能不同。\n有人说更新好了，我需要知道是可审阅、可测试，还是可公开使用。\n我可以直接问，新版本是否已经部署到生产环境。\n也可以问还剩什么，以及谁应在继续之前作下一步决定。\n这些问题避免小小的理解差异在后续变成大问题。\n要求解释时，即使原问题有疑问语序，嵌入的问题仍用陈述语序。\n例如我说想理解系统怎样运作，不把does放在从句主语前。\n有用回答应区分已经观察到的内容，与仍是假设或可能解释的内容。\n证据不完整时，可以问得出明确结论前还需检查什么。\n清晰提问和仔细确认让我边学边把项目推向可行方向。\n共同理解让下一动作更审慎。"
  },
  {
    "title": "05C Working Conversation",
    "titleTranslate": "第05课C｜提问与确认理解",
    "text": "Me: Could you explain where the application saves its settings and whether those settings will remain after the container is rebuilt?\nAssistant: Some settings are stored in the database, while local files may be stored inside the container unless a volume is configured.\nMe: I understand the general difference, but could you give me a concrete example using the configuration that this project actually has?\nAssistant: Yes; first we should inspect the volume configuration and identify the files that the application writes during an ordinary session.\nMe: So rebuilding does not automatically tell us whether the saved data will survive; the storage location determines that result, correct?\nAssistant: Correct; we need to check the actual storage arrangement rather than assume that every file is either persistent or temporary.\nMe: Please explain what you find in simple terms, and distinguish the confirmed facts from anything that still needs another check.\nAssistant: I will summarize the relevant settings, show one concrete example, and explain the next step before suggesting any change.",
    "textTranslate": "我：能解释应用把设置存在哪里，以及重建容器后设置是否保留吗？\n助手：部分设置在数据库里；如果没有配置数据卷，本地文件可能在容器内部。\n我：我理解大致区别，能按本项目实际配置举个具体例子吗？\n助手：可以，先检查数据卷配置，确定应用平时会写哪些文件。\n我：也就是说，重建本身不能决定数据是否保留，存储位置才决定结果，对吗？\n助手：对，需要检查实际存储安排，不能假设所有文件都持久或临时。\n我：请用简单话解释发现，并区分已确认事实和还需检查的内容。\n助手：我会总结相关设置、举例，并在建议改动前解释下一步。"
  },
  {
    "title": "05D Sentence Review",
    "titleTranslate": "第05课D｜提问与确认理解",
    "text": "A useful question gives the other person enough information to understand what I know and what I still need to learn.\nI try to identify the specific uncertainty, such as where a setting is stored or how a service receives a request.\nFor example, I might ask whether rebuilding a container will remove the settings that I saved during the previous session.\nI can also repeat the main idea in simpler words and ask the other person to confirm whether my understanding is correct.\nSometimes an answer appears clear because it uses familiar words, but those words can refer to different things in different projects.\nI can ask a direct question, such as whether the new version has been deployed to the production environment.\nWhen I request an explanation, I keep the embedded question in ordinary statement order, even if the original question uses inversion.\nIf the evidence is incomplete, it is reasonable to ask what needs to be checked before we reach a firm conclusion.\nCould you explain where the application saves its settings and whether those settings will remain after the container is rebuilt?\nI understand the general difference, but could you give me a concrete example using the configuration that this project actually has?\nSo rebuilding does not automatically tell us whether the saved data will survive; the storage location determines that result, correct?\nPlease explain what you find in simple terms, and distinguish the confirmed facts from anything that still needs another check.",
    "textTranslate": "有效的问题会提供足够信息，让对方知道我已懂什么、还需要了解什么。\n我会明确具体疑点，比如设置存在哪里，或服务如何接收请求。\n例如我会问，重新构建容器会不会删除上次保存的设置。\n我也可以用简单话重述重点，请对方确认理解是否正确。\n有时回答用了熟悉词，看起来清楚，但不同项目里的含义可能不同。\n我可以直接问，新版本是否已经部署到生产环境。\n要求解释时，即使原问题有疑问语序，嵌入的问题仍用陈述语序。\n证据不完整时，可以问得出明确结论前还需检查什么。\n我：能解释应用把设置存在哪里，以及重建容器后设置是否保留吗？\n我：我理解大致区别，能按本项目实际配置举个具体例子吗？\n我：也就是说，重建本身不能决定数据是否保留，存储位置才决定结果，对吗？\n我：请用简单话解释发现，并区分已确认事实和还需检查的内容。"
  },
  {
    "title": "05E Vocabulary in Context",
    "titleTranslate": "第05课E｜提问与确认理解",
    "text": "Keep me informed of important changes, but ignore information that does not affect the current decision.\nIf the info is unclear, ask another question and give the other person time to explain the nature of the problem.\nA concrete example can help me figure out which detail matters before I ask a more focused question.\nI answered the first question, but several questions remained unanswered because the necessary evidence was absent.\nThe answers should explain the relevant context and indicate when an unknown detail needs another check.\nClarifying the meaning of a term prevents confusion when the same word represents different ideas in different contexts.\nThe result indicates a problem, but it does not identify the cause without additional analysis.\nI am curious about the design, but I need to distinguish an interesting question from an urgent requirement.\nI could not fathom the explanation until someone gave me a concrete example with ordinary numbers.\nThe listener asked for a succinct answer rather than a substantial collection of loosely related facts.\nA tip may be helpful, but a thorough explanation should clarify the reasoning behind it.",
    "textTranslate": "请告诉我重要变化，无关当前决定的信息可忽略。\n信息不清就再问，并给对方时间解释问题性质。\n具体例子帮助我弄清哪个细节重要，再提出更聚焦的问题。\n我答了首问，但缺证据，几个问题仍未答。\n答案应解释背景，并说明未知细节何时需再查。\n澄清术语含义，可防止同一词在不同语境代表不同概念而混淆。\n结果表明有问题，但没有进一步分析不能定位原因。\n我好奇设计，但需区分有趣问题与紧急需求。\n直到有人给普通数字的具体例子，我才理解说明。\n听者要求简明答案，而非一大堆松散相关事实。\n提示有帮助，但细致说明应解释背后推理。"
  },
  {
    "title": "06A Choosing Between Two Reasonable Options",
    "titleTranslate": "第06课A｜比较方案并作决定",
    "text": "Choosing a solution is easier when I compare it against a clear goal instead of looking for the most impressive technology.\nSuppose that I need a small tool for personal use and have two reasonable ways to build the first version.\nThe first option offers more features, but it requires additional setup and creates more work whenever I need to update it.\nThe second option is simpler, easier to understand, and less expensive to maintain, although it has a few limitations.\nBefore deciding, I compare the cost, the expected workload, and the tasks that each option actually allows me to complete.\nI also ask whether the additional features solve a current problem or merely create possibilities that I may never use.\nFor this project, a smaller solution may be the better choice because I value clarity and a short path to useful results.\nThat does not make the larger option wrong; it means that it fits a different set of requirements and priorities.\nAfter choosing, I write down the reason so that a future change in direction can be compared with the original decision.\nA good comparison helps me make a deliberate choice without pretending that one approach is always best for every situation.",
    "textTranslate": "把方案与明确目标比较，比寻找最炫技术更容易作决定。\n假设我需要个人使用的小工具，有两种合理方式制作初版。\n第一个方案功能更多，但需要额外配置，每次更新工作量也更大。\n第二个更简单、更易理解、维护更便宜，不过也有限制。\n决定前，我比较成本、预期工作量，以及各方案实际能完成的任务。\n也会问，额外功能解决当前问题，还是只提供未必会用的可能性。\n这个项目里，小方案可能更好，因为我重视清晰和快速取得实用结果。\n这不代表大方案错误，只说明它适合另一组需求和优先级。\n选定后记录理由，以便日后改变方向时与最初决定比较。\n良好比较帮助我审慎选择，而不假装某种方法在所有场景都最好。"
  },
  {
    "title": "06B Explaining Why I Prefer One Approach",
    "titleTranslate": "第06课B｜比较方案并作决定",
    "text": "When I recommend an approach, I want the explanation to show a useful trade-off rather than express an unsupported personal preference.\nSaying that the second version is better is not enough unless I explain which goal it serves more effectively.\nFor example, the second layout may make the main action easier to find while using fewer cards and less introductory text.\nIt may also work better on a narrow screen, even if the first version looks more dramatic on a large display.\nThese observations give the team something concrete to discuss and help us avoid arguing only about whether a design feels modern.\nI can say that I prefer the second option because it matches the existing navigation and reduces the number of decisions.\nIf someone disagrees, I ask which requirement they think deserves more attention and whether an example can clarify the difference.\nSometimes the best result combines a useful part of each approach, but that combination still needs to remain coherent and manageable.\nThe purpose of comparison is to support a decision, so I eventually choose an option and explain the next practical step.\nI can reconsider later if new evidence appears, without treating every small uncertainty as a reason to delay the whole project.",
    "textTranslate": "推荐方案时，我希望解释有用的取舍，而不是没有依据的个人偏好。\n说第二版更好不够，还得说明它更有效地满足哪个目标。\n例如第二种布局用更少卡片和介绍文字，让主要操作更容易找到。\n它可能在窄屏效果更好，虽然第一版大屏看起来更有冲击力。\n这些观察让团队有具体讨论依据，避免只争论设计是否现代。\n我可以说偏好第二方案，因为它匹配现有导航并减少决策数量。\n有人不同意时，我会问哪个需求值得更多关注，以及能否举例澄清差别。\n有时最佳结果结合两种方案的优点，但组合仍需连贯且可管理。\n比较是为了支持决定，所以最终应选定方案并说明实际下一步。\n新证据出现后可以重新考虑，不必因每个小疑点拖延整个项目。"
  },
  {
    "title": "06C Working Conversation",
    "titleTranslate": "第06课C｜比较方案并作决定",
    "text": "Designer: I have prepared two layouts; the first shows more information immediately, while the second gives the main action more space.\nMe: Could you compare them on mobile as well, because most visitors may use the page on a narrow screen during a break?\nDesigner: On mobile, the second version has fewer cards and less text, so the first useful action is easier to find.\nMe: I prefer that option, but I would like to keep the short example from the first design because it explains the product.\nDesigner: That combination should work; would you like me to update the preview before we apply the same layout to the other pages?\nMe: Yes, please show one complete example first, and explain any limitations that become visible when the content is longer than expected.\nDesigner: I will prepare that version and compare it with the original using the same content, screen size, and main user task.\nMe: Good; if the new version is clearer, we can choose it and record why it is the better fit for this project.",
    "textTranslate": "设计者：我准备了两种布局，第一种立即展示更多信息，第二种给主要操作更多空间。\n我：也能比较移动端吗，访客可能多在休息时用窄屏查看。\n设计者：移动端第二版卡片和文字更少，更容易找到首个有用操作。\n我：我喜欢那个方案，但想保留第一版的简短例子，因为它解释产品。\n设计者：可以结合，其他页面应用相同布局前，要先更新预览吗？\n我：请先展示一个完整例子，并解释内容超长时暴露的限制。\n设计者：我会准备该版，并用相同内容、屏幕和主要任务与原版比较。\n我：好，如果新版更清晰就选它，并记录为何更适合本项目。"
  },
  {
    "title": "06D Sentence Review",
    "titleTranslate": "第06课D｜比较方案并作决定",
    "text": "Choosing a solution is easier when I compare it against a clear goal instead of looking for the most impressive technology.\nThe first option offers more features, but it requires additional setup and creates more work whenever I need to update it.\nBefore deciding, I compare the cost, the expected workload, and the tasks that each option actually allows me to complete.\nThat does not make the larger option wrong; it means that it fits a different set of requirements and priorities.\nWhen I recommend an approach, I want the explanation to show a useful trade-off rather than express an unsupported personal preference.\nFor example, the second layout may make the main action easier to find while using fewer cards and less introductory text.\nI can say that I prefer the second option because it matches the existing navigation and reduces the number of decisions.\nThe purpose of comparison is to support a decision, so I eventually choose an option and explain the next practical step.\nI have prepared two layouts; the first shows more information immediately, while the second gives the main action more space.\nOn mobile, the second version has fewer cards and less text, so the first useful action is easier to find.\nThat combination should work; would you like me to update the preview before we apply the same layout to the other pages?\nI will prepare that version and compare it with the original using the same content, screen size, and main user task.",
    "textTranslate": "把方案与明确目标比较，比寻找最炫技术更容易作决定。\n第一个方案功能更多，但需要额外配置，每次更新工作量也更大。\n决定前，我比较成本、预期工作量，以及各方案实际能完成的任务。\n这不代表大方案错误，只说明它适合另一组需求和优先级。\n推荐方案时，我希望解释有用的取舍，而不是没有依据的个人偏好。\n例如第二种布局用更少卡片和介绍文字，让主要操作更容易找到。\n我可以说偏好第二方案，因为它匹配现有导航并减少决策数量。\n比较是为了支持决定，所以最终应选定方案并说明实际下一步。\n设计者：我准备了两种布局，第一种立即展示更多信息，第二种给主要操作更多空间。\n设计者：移动端第二版卡片和文字更少，更容易找到首个有用操作。\n设计者：可以结合，其他页面应用相同布局前，要先更新预览吗？\n设计者：我会准备该版，并用相同内容、屏幕和主要任务与原版比较。"
  },
  {
    "title": "06E Vocabulary in Context",
    "titleTranslate": "第06课E｜比较方案并作决定",
    "text": "The price is listed per month, and the comparison should include a pair of examples with matching requirements.\nA trade-off may improve speed while reducing flexibility, so a detailed breakdown is more useful than one impressive number.\nThe quick comparison includes cost, time, and practical limitations, rather than only a ranking based on popularity.\nBudgeting helps us estimate the resources required before we accept an additional piece of work.\nThe alternative scheme reduces repeated decisions, but it involves a different arrangement of shared responsibilities.\nThere are several cases where the simpler approach fits, and one case where it does not.\nThe two publications offer different rates, so the cheaper placement is not automatically the more useful choice.\nThe selection score should reflect the agreed priorities rather than reward a feature merely because it is new.\nThe figures suggest a fair comparison, but we should check whether the samples represent the same workload.\nA bond issued at par is priced at its face value; this finance expression is a specialist extension, not a core project phrase.",
    "textTranslate": "价格按月列示，比较应含一对需求匹配的例子。\n取舍可提速却降灵活性，因此详细分解比单个漂亮数字有用。\n快速比较包括成本、时间和限制，不只按人气排名。\n编制预算帮助我们在接受额外工作前估算资源。\n替代方案减少重复决定，但涉及不同职责安排。\n简化方案适合几个案例，也有一个不适合。\n两家刊物报价不同，更便宜的位置不自动更有用。\n选择评分应体现约定优先级，而非仅因功能新就加分。\n数字看似公平，但要查样本工作量是否相同。\n债券按面值发行称at par，这是金融补充表达，非核心项目用语。"
  },
  {
    "title": "07A Describing a Page Before Changing It",
    "titleTranslate": "第07课A｜描述页面与视觉效果",
    "text": "When I describe a page, I begin with the arrangement of its main sections rather than commenting immediately on the colors.\nThe header is at the top, the navigation sits on the left, and the main content occupies the center of the screen.\nA clear structure helps visitors understand where they are and how to reach the information that matters for their current task.\nNext, I look at the relationship between the title, the description, and the main button inside each section of the page.\nIf these elements compete for attention, the page can feel crowded even when there is enough empty space around them.\nI describe the specific issue with words such as narrow, wide, centered, uneven, or difficult to read on a smaller screen.\nFor example, the title may be too large, while the text below it may be too faint against the background.\nThe icon may also sit slightly above the label, which makes two neighboring items look as though they do not belong together.\nThese observations give us a clear starting point for improvement without requiring a complete redesign of the whole interface.\nI want the description to be accurate enough that another person can locate the problem before I suggest a particular change.",
    "textTranslate": "描述页面时，我先说明主要区块安排，不立即评论颜色。\n页头在顶部、导航在左侧、主体内容位于屏幕中央。\n清晰结构帮助访客理解当前位置，以及如何找到当前任务所需信息。\n接着查看各区块中标题、描述和主要按钮之间的关系。\n如果元素争抢注意力，即使周围空白够多，页面仍会显拥挤。\n我用窄、宽、居中、不均匀，或小屏难读等词描述具体问题。\n例如标题可能过大，下方文字与背景相比又太淡。\n图标也可能略高于文字，让相邻项目看起来不像一组。\n这些观察提供清晰改进起点，无需重做整个界面。\n我希望描述足够准确，让对方在我建议修改前就能定位问题。"
  },
  {
    "title": "07B Reading the Visual Details",
    "titleTranslate": "第07课B｜描述页面与视觉效果",
    "text": "Visual details communicate relationships, so a small difference in spacing or emphasis can change how someone understands a page.\nWhen a heading is closer to the previous section than to its own text, the grouping becomes difficult to recognize.\nA consistent gap between related items makes the content easier to scan, especially when the page contains several different learning activities.\nThe same principle applies to typography, where size, weight, and contrast should help distinguish the title from supporting information.\nA darker background does not automatically create better contrast, because the actual text color and font weight still affect readability.\nOn mobile, the width of the content changes, and a comfortable desktop arrangement may become narrow or unnecessarily difficult to navigate.\nI check whether a long label wraps naturally and whether the main button remains easy to reach without covering important text.\nImages and animations should support the purpose of the page, rather than make ordinary information harder to see or understand.\nA cinematic image or a photorealistic illustration may be appropriate in one place and distracting in another, depending on the task.\nThe final judgment should come from the actual content and user activity, not just from an attractive screenshot of an empty page.",
    "textTranslate": "视觉细节传递关系，小小间距或强调差异就可能改变理解。\n标题离上一区块比自身正文更近时，分组关系就难以辨认。\n相关项间距一致，会让多种学习活动所在页面更易浏览。\n排版也如此，字号、字重和对比度应区分标题与辅助信息。\n深背景不会自动带来更好对比，实际字色和字重仍影响可读性。\n移动端内容宽度变化，桌面舒适布局可能变窄或难导航。\n我检查长标签是否自然换行，主按钮是否易操作且不遮文字。\n图片动画应服务页面目的，而非让普通信息更难理解。\n电影感或写实图片是否合适，取决于位置与任务。\n最终应依据真实内容和用户活动判断，而不只看空页面截图。"
  },
  {
    "title": "07C Working Conversation",
    "titleTranslate": "第07课C｜描述页面与视觉效果",
    "text": "Reviewer: The page contains the right information, but the title and the button compete for attention, especially on a small screen.\nMe: Could you describe the spacing as well, because I am not sure which items should look like one connected group?\nReviewer: The heading should be closer to its own description, and the gap above the next section should be a little larger.\nMe: I also notice that the navigation icon sits above its label; does that make the sidebar look slightly uneven to you?\nReviewer: Yes, and the supporting text is rather faint, so it would help to improve the contrast before adding any decorative effects.\nMe: Please show me a preview with the real lesson content, including a long heading and a button label that may wrap.\nReviewer: I will compare desktop and mobile layouts and explain which changes improve grouping, readability, and access to the main action.\nMe: That will help us make a clear decision about the page without changing its existing style more than the task requires.",
    "textTranslate": "评审者：信息正确，但标题和按钮争抢注意，尤其在小屏上。\n我：也能描述间距吗，我不确定哪些项应该是一组。\n评审者：标题应更靠近自己的描述，下一区块上方间距应稍大。\n我：导航图标还比文字偏高，你也觉得侧栏有些不齐吗？\n评审者：是的，辅助文字偏淡，增加装饰前先提高对比度更有用。\n我：请用真实课文展示预览，包括长标题和可能换行的按钮文字。\n评审者：我会比较桌面和移动布局，解释哪些修改改善分组、阅读和主要操作。\n我：这样能明确决定，不会超出任务所需大幅改变现有风格。"
  },
  {
    "title": "07D Sentence Review",
    "titleTranslate": "第07课D｜描述页面与视觉效果",
    "text": "When I describe a page, I begin with the arrangement of its main sections rather than commenting immediately on the colors.\nA clear structure helps visitors understand where they are and how to reach the information that matters for their current task.\nIf these elements compete for attention, the page can feel crowded even when there is enough empty space around them.\nThe icon may also sit slightly above the label, which makes two neighboring items look as though they do not belong together.\nVisual details communicate relationships, so a small difference in spacing or emphasis can change how someone understands a page.\nA consistent gap between related items makes the content easier to scan, especially when the page contains several different learning activities.\nOn mobile, the width of the content changes, and a comfortable desktop arrangement may become narrow or unnecessarily difficult to navigate.\nA cinematic image or a photorealistic illustration may be appropriate in one place and distracting in another, depending on the task.\nThe page contains the right information, but the title and the button compete for attention, especially on a small screen.\nThe heading should be closer to its own description, and the gap above the next section should be a little larger.\nYes, and the supporting text is rather faint, so it would help to improve the contrast before adding any decorative effects.\nI will compare desktop and mobile layouts and explain which changes improve grouping, readability, and access to the main action.",
    "textTranslate": "描述页面时，我先说明主要区块安排，不立即评论颜色。\n清晰结构帮助访客理解当前位置，以及如何找到当前任务所需信息。\n如果元素争抢注意力，即使周围空白够多，页面仍会显拥挤。\n图标也可能略高于文字，让相邻项目看起来不像一组。\n视觉细节传递关系，小小间距或强调差异就可能改变理解。\n相关项间距一致，会让多种学习活动所在页面更易浏览。\n移动端内容宽度变化，桌面舒适布局可能变窄或难导航。\n电影感或写实图片是否合适，取决于位置与任务。\n评审者：信息正确，但标题和按钮争抢注意，尤其在小屏上。\n评审者：标题应更靠近自己的描述，下一区块上方间距应稍大。\n评审者：是的，辅助文字偏淡，增加装饰前先提高对比度更有用。\n评审者：我会比较桌面和移动布局，解释哪些修改改善分组、阅读和主要操作。"
  },
  {
    "title": "07E Vocabulary in Context",
    "titleTranslate": "第07课E｜描述页面与视觉效果",
    "text": "The character in the illustration has an extremely simple outline, while the motion guides attention toward the main action.\nThe positioning rules define the positions of the cards, and an offset moves the label slightly away from the icon.\nOn a handheld device, the screen is smaller, so the same page needs a more compact arrangement of the controls.\nThe animation uses a slow movement to guide attention toward the button without making the whole page feel unstable.\nA bolder heading creates emphasis, while a blue badge can identify a category when color is not the only signal.\nThe hero section contains the main title, a short tagline, and a visual that introduces the product.\nA consistent logo, title style, and footer make separate pages feel like parts of one site.\nThe panel has a sticky header and a popover that opens beside the selected item.\nThe tabs should remain visible when the viewport becomes narrow, without creating horizontal overflow.\nThe mock image shows a spaceship near a hallway, but the final illustration should use the real product context.\nA camera capture can reveal facial details that are not appropriate for every public demonstration.\nThe image tool can colorize a picture, adjust its frame, or unwarp a distorted shape.\nThe layout builder uses flex behavior to distribute available space across the elements in a column.\nA narrow window needs a different outline around the focused control so that keyboard users can locate it.\nThe example headings and titles should be realistic, and the image should not turn an ordinary page into a dramatic movie scene.\nThe screen shows the current cursor position and a marker next to the selected text.",
    "textTranslate": "插图角色轮廓极简，动效引导主要操作。\n定位规则定义卡片位置，偏移量让标签略离图标。\n手持设备屏幕较小，控件需更紧凑安排。\n动画用缓慢移动引导按钮注意，不使页面不稳。\n醒目标题强调，蓝色徽章可识别分类，但不能只靠颜色。\n首屏主视觉区包含主标题、简短标语及产品图片。\n统一标志、标题样式和页脚让独立页面像一个站点。\n面板有吸附页头和选项旁弹出的浮层。\n可视区域变窄时标签页应仍可见，不产生横向溢出。\n模拟图展示走廊附近飞船，但最终插图应符合产品语境。\n相机拍摄可能暴露不适合公开演示的面部细节。\n图像工具可以着色、调框或还原变形形状。\n布局构建器用弹性行为把可用空间分给列中元素。\n窄窗口需为焦点控件设置不同轮廓，便于键盘用户定位。\n示例标题应真实，不应让图片把普通页面变电影场景。\n屏幕展示光标位置，并在选中文本旁显示标记。"
  },
  {
    "title": "08A Turning an Observation into a Clear Request",
    "titleTranslate": "第08课A｜提出修改并给反馈",
    "text": "Useful feedback connects an observation to a requested change, so that the person doing the work knows what to improve.\nInstead of saying that the page feels wrong, I explain which part is difficult to read, understand, or use.\nI might say that the header is too large on mobile and ask for a smaller title with slightly less padding.\nIf I want an existing pattern preserved, I include that request rather than assume that the other person will notice it.\nFor example, I can ask them to replace the icon while keeping its size and alignment consistent with the navigation.\nI separate necessary changes from optional ideas, because a long list can make every small suggestion appear equally urgent.\nWhen the task is clear, the next preview should show a specific improvement that we can compare with the previous version.\nI review that result using the same content and screen size so that unrelated differences do not confuse the comparison.\nIf the problem remains, I describe what is still visible and ask for another focused adjustment instead of restarting the entire design.\nThis approach makes feedback easier to act on and helps the conversation move from personal impressions to concrete decisions.",
    "textTranslate": "有用反馈把观察与修改请求连接起来，让执行者知道改哪里。\n我会说明哪部分难读、难理解或难用，而不只说页面不对劲。\n我可能说移动端页头太大，请求缩小标题并稍减内边距。\n想保留现有模式时，我会明确提出，不假定对方会注意。\n例如请求更换图标，同时保持尺寸和对齐方式与导航一致。\n我区分必要修改与可选想法，因为长清单容易让所有小建议都显得紧急。\n任务明确时，下版预览应显示可与上一版比较的具体改进。\n我用相同内容和屏幕尺寸检查，避免无关差异干扰比较。\n问题仍在时，我说明仍可见的现象，并要求针对调整，不重启整个设计。\n这样反馈更可执行，对话也能从个人印象转为具体决定。"
  },
  {
    "title": "08B Giving Feedback After a Preview",
    "titleTranslate": "第08课B｜提出修改并给反馈",
    "text": "After a preview is ready, I take a moment to compare the result with the original request before suggesting anything new.\nThis protects the work from an endless cycle in which every improvement immediately creates a different and unrelated direction.\nI begin by identifying what is now correct, such as the smaller header or the better alignment between neighboring navigation items.\nThen I describe any remaining issue in a way that someone can observe, rather than asking them to guess my preference.\nFor example, the dropdown may still look different from the avatar menu, even though both controls perform a similar kind of action.\nI can ask for the same border, background, and spacing while allowing the content inside each menu to remain different.\nIf the result already meets the requirement, I say so clearly and choose whether to continue with the remaining pages.\nApproval should identify the version or example being accepted, especially if several alternatives have appeared during the conversation.\nA simple instruction such as proceed with the second option is more useful when everyone can see which option it refers to.\nClear feedback includes an ending as well as a beginning, so that completed work can remain complete while the next task starts.",
    "textTranslate": "预览完成后，我先与原要求比较，再提出新建议。\n这可避免陷入每次改进后又立即提出无关新方向的循环。\n我先确认已正确的地方，比如页头缩小或相邻导航对齐改善。\n再以可观察方式描述剩余问题，而不让对方猜偏好。\n例如两个控件执行类似操作，但下拉菜单仍与头像菜单风格不同。\n我可要求相同边框、背景和间距，同时允许菜单内容不同。\n结果已满足需求时，我明确确认，并决定是否继续其他页面。\n尤其谈过多个备选时，应说明批准的是哪个版本或例子。\n大家能看到第二方案具体指什么时，按第二方案推进才有用。\n清晰反馈既要能开始也要能结束，让已完成工作结束、下一任务开始。"
  },
  {
    "title": "08C Working Conversation",
    "titleTranslate": "第08课C｜提出修改并给反馈",
    "text": "Me: The mobile header is still too large, and the menu icon looks slightly higher than the text next to it.\nDesigner: Would you like me to make the title smaller and align the icon with the label while preserving the current colors?\nMe: Yes, and please make the dropdown look consistent with the avatar menu, including its border, background, and spacing between items.\nDesigner: Should I apply these changes to every page immediately, or show you one example before changing the rest of the site?\nMe: Show me one complete example first, using a long title and the same content that we used in the previous preview.\nDesigner: The new preview is ready; the header is smaller, the icon is aligned, and both menus now use the same style.\nMe: This meets the request; go ahead with this version and update the remaining pages without introducing additional changes to their content.\nDesigner: Understood; I will use this approved example as the reference and report any page where the same approach does not fit.",
    "textTranslate": "我：移动端页头仍太大，菜单图标比旁边文字略高。\n设计者：要缩小标题并对齐图标与文字，同时保留当前颜色吗？\n我：是的，下拉菜单也要与头像菜单一致，包括边框、背景和项目间距。\n设计者：立即应用所有页面，还是先展示一个例子？\n我：先用长标题和上版相同内容展示一个完整例子。\n设计者：新预览好了，页头变小、图标对齐，两个菜单风格一致。\n我：这符合要求，按这版更新其余页面，内容不作额外修改。\n设计者：明白，以批准例子作参考，并报告不适用的页面。"
  },
  {
    "title": "08D Sentence Review",
    "titleTranslate": "第08课D｜提出修改并给反馈",
    "text": "Useful feedback connects an observation to a requested change, so that the person doing the work knows what to improve.\nI might say that the header is too large on mobile and ask for a smaller title with slightly less padding.\nFor example, I can ask them to replace the icon while keeping its size and alignment consistent with the navigation.\nI review that result using the same content and screen size so that unrelated differences do not confuse the comparison.\nAfter a preview is ready, I take a moment to compare the result with the original request before suggesting anything new.\nI begin by identifying what is now correct, such as the smaller header or the better alignment between neighboring navigation items.\nI can ask for the same border, background, and spacing while allowing the content inside each menu to remain different.\nA simple instruction such as proceed with the second option is more useful when everyone can see which option it refers to.\nThe mobile header is still too large, and the menu icon looks slightly higher than the text next to it.\nYes, and please make the dropdown look consistent with the avatar menu, including its border, background, and spacing between items.\nShow me one complete example first, using a long title and the same content that we used in the previous preview.\nThis meets the request; go ahead with this version and update the remaining pages without introducing additional changes to their content.",
    "textTranslate": "有用反馈把观察与修改请求连接起来，让执行者知道改哪里。\n我可能说移动端页头太大，请求缩小标题并稍减内边距。\n例如请求更换图标，同时保持尺寸和对齐方式与导航一致。\n我用相同内容和屏幕尺寸检查，避免无关差异干扰比较。\n预览完成后，我先与原要求比较，再提出新建议。\n我先确认已正确的地方，比如页头缩小或相邻导航对齐改善。\n我可要求相同边框、背景和间距，同时允许菜单内容不同。\n大家能看到第二方案具体指什么时，按第二方案推进才有用。\n我：移动端页头仍太大，菜单图标比旁边文字略高。\n我：是的，下拉菜单也要与头像菜单一致，包括边框、背景和项目间距。\n我：先用长标题和上版相同内容展示一个完整例子。\n我：这符合要求，按这版更新其余页面，内容不作额外修改。"
  },
  {
    "title": "08E Vocabulary in Context",
    "titleTranslate": "第08课E｜提出修改并给反馈",
    "text": "The preview looks great, but please mark the change that fixes the original issue rather than highlighting every small difference.\nThe critique includes practical comments about spacing, and each comment connects an observation with a requested improvement.\nThe reviewer outlined the main concerns and used highlights to show where the spacing still looked inconsistent.\nThe revised version looks clearer, but a small alignment mistake remains on the side of the menu.\nWe missed that detail earlier, so the next revision should correct it before introducing more changes.\nA useful response treats mistakes as information, rather than making the person receiving feedback feel foolish.\nThe design has been revamped, but I would still like to refine the grouping of related items.\nAn impeccable screenshot does not guarantee that the actual page works well with long content or ordinary user input.\nA successful change improves the user's experience while keeping the agreed scope firmly in view.",
    "textTranslate": "预览很好，但请标出解决原问题的修改，不必高亮每个小差别。\n评析含实用间距评论，每条把观察与修改相连。\n评审者概述关注点，用高亮标出间距仍不一致处。\n修订版更清晰，但菜单一侧仍有小对齐错误。\n我们先前遗漏细节，下次修订应先纠正再加修改。\n有用回应把错误当信息，不让收到反馈者觉得愚蠢。\n设计已改版，但我仍想细化相关项分组。\n无可挑剔的截图不保证真实页面在长内容或普通输入下正常。\n成功改动改善体验，同时牢牢把握约定范围。"
  },
  {
    "title": "09A Explaining a Workflow One Action at a Time",
    "titleTranslate": "第09课A｜解释操作与工作流程",
    "text": "A workflow description explains how a person moves from an initial intention to a useful result through a series of connected actions.\nFor a learning exercise, the user first chooses a lesson, reads the goal, and opens the part that they want to practice.\nAfter the passage appears, they can listen to a sentence, type what they hear, and compare their attempt with the original text.\nIf a word is unfamiliar, the user should be able to check its meaning without losing the place where the exercise stopped.\nWhen the user returns, the system needs to show the relevant sentence and preserve the information needed to continue comfortably.\nThese details matter because a workflow is more than a collection of buttons that happen to appear on the same screen.\nEach action should have an understandable result, and the following step should be visible when the previous action has finished.\nI describe the ordinary path first, then add important alternatives such as correcting an answer or returning to an earlier section.\nThis sequence helps the team see missing connections before they spend time polishing individual controls or adding more options.\nA clear workflow makes the product easier to explain, easier to review, and more likely to support the user's actual intention.",
    "textTranslate": "流程说明解释一个人怎样通过一系列关联动作，从最初意图走向有用结果。\n学习练习中，用户先选课、读目标，再打开想练的部分。\n文章出现后，可以听一句、输入所听内容，再与原文比较。\n遇到生词时，用户应能查义，而不丢失练习停止的位置。\n用户回来后，系统应显示相关句子，并保留继续所需信息。\n这些细节重要，因为流程不只是碰巧出现在同一屏的按钮集合。\n每个动作应有易懂结果，前一动作结束后应能看见下一步。\n我先描述正常路径，再补充改答案或返回前一区块等重要分支。\n这个顺序帮助团队在打磨控件或加选项之前发现缺失连接。\n清晰流程让产品更容易解释、检查，也更能支持用户实际意图。"
  },
  {
    "title": "09B What Happens After a Click",
    "titleTranslate": "第09课B｜解释操作与工作流程",
    "text": "A button label describes an action, but the behavior after the click determines whether the interface actually keeps that promise.\nIf a button says save, the user expects the information to remain available after leaving the page and returning later.\nThe application should therefore explain whether the action succeeded, failed, or is still waiting for a response from another service.\nA silent delay can make people click again because they cannot tell whether their first request was received or ignored.\nThe description of the workflow should include this waiting state and explain when another action becomes safe or useful.\nWe also need to think about cancellation, because a user may change their mind before a long operation has finished.\nCan the user close the dialog, continue reading, or return later without creating duplicate work or losing important input?\nThese questions connect interaction design with the state that the application maintains behind the visible controls and messages.\nI prefer an explanation that follows one real example, from the initial input to the final confirmation and the next available action.\nThat example gives both the developer and the reviewer a common reference when they discuss whether the whole process works correctly.\nThe same description can guide a later review.",
    "textTranslate": "按钮文字描述动作，但点击后行为决定界面是否兑现承诺。\n按钮写保存时，用户预期离开页面再回来仍有信息。\n因此应用应说明操作成功、失败，还是仍在等待其他服务响应。\n无提示延迟会让人再次点击，因为不知道首个请求被接收还是忽略。\n流程说明应包含等待状态，并解释何时再次操作安全或有用。\n也要考虑取消，因为长操作结束前用户可能改变想法。\n用户能关闭对话框、继续阅读或稍后回来，而不重复操作或丢重要输入吗？\n这些问题把交互设计与可见控件消息背后的应用状态连接起来。\n我更喜欢沿一个真实例子，从初始输入讲到最终确认和下一操作。\n这样开发者与检查者讨论整体流程是否正确时，有共同参考。\n同一说明也可指导后续检查。"
  },
  {
    "title": "09C Working Conversation",
    "titleTranslate": "第09课C｜解释操作与工作流程",
    "text": "Me: Could you walk me through the exercise from the first click, including what happens when a learner does not know a word?\nDeveloper: The learner chooses a lesson, opens the passage, and selects a sentence; they can then listen, type, and check the answer.\nMe: If they open the dictionary during the exercise, will they return to the same sentence or have to begin the passage again?\nDeveloper: They should return to the same sentence, and the application should preserve any input that has not yet been submitted.\nMe: Please include that state in the explanation, and show how the page communicates that an answer is still being checked.\nDeveloper: I will also explain what the learner can do if the request fails, including retrying without losing the previous attempt.\nMe: Good; describe one complete example before we add optional controls, so we can see whether the basic path is actually clear.\nDeveloper: I will document the input, the visible feedback, and the next action at each step, then compare the behavior with that description.",
    "textTranslate": "我：能从首次点击讲完整练习，并包括学习者不认识词时的情况吗？\n开发者：学习者选课、打开文章、选择句子，然后听、输入并检查答案。\n我：练习中打开词典，回来在同一句，还是要重头开始？\n开发者：应回到同一句，应用应保留未提交输入。\n我：请把这个状态写入说明，并展示页面如何表达答案仍在检查。\n开发者：也会解释请求失败后如何重试且不丢上次尝试。\n我：好，先讲完整例子再加可选控件，以确认基本路径清楚。\n开发者：我会记录每步输入、可见反馈和下一操作，再对照行为。"
  },
  {
    "title": "09D Sentence Review",
    "titleTranslate": "第09课D｜解释操作与工作流程",
    "text": "A workflow description explains how a person moves from an initial intention to a useful result through a series of connected actions.\nAfter the passage appears, they can listen to a sentence, type what they hear, and compare their attempt with the original text.\nWhen the user returns, the system needs to show the relevant sentence and preserve the information needed to continue comfortably.\nI describe the ordinary path first, then add important alternatives such as correcting an answer or returning to an earlier section.\nA button label describes an action, but the behavior after the click determines whether the interface actually keeps that promise.\nThe application should therefore explain whether the action succeeded, failed, or is still waiting for a response from another service.\nWe also need to think about cancellation, because a user may change their mind before a long operation has finished.\nI prefer an explanation that follows one real example, from the initial input to the final confirmation and the next available action.\nCould you walk me through the exercise from the first click, including what happens when a learner does not know a word?\nIf they open the dictionary during the exercise, will they return to the same sentence or have to begin the passage again?\nPlease include that state in the explanation, and show how the page communicates that an answer is still being checked.\nGood; describe one complete example before we add optional controls, so we can see whether the basic path is actually clear.",
    "textTranslate": "流程说明解释一个人怎样通过一系列关联动作，从最初意图走向有用结果。\n文章出现后，可以听一句、输入所听内容，再与原文比较。\n用户回来后，系统应显示相关句子，并保留继续所需信息。\n我先描述正常路径，再补充改答案或返回前一区块等重要分支。\n按钮文字描述动作，但点击后行为决定界面是否兑现承诺。\n因此应用应说明操作成功、失败，还是仍在等待其他服务响应。\n也要考虑取消，因为长操作结束前用户可能改变想法。\n我更喜欢沿一个真实例子，从初始输入讲到最终确认和下一操作。\n我：能从首次点击讲完整练习，并包括学习者不认识词时的情况吗？\n我：练习中打开词典，回来在同一句，还是要重头开始？\n我：请把这个状态写入说明，并展示页面如何表达答案仍在检查。\n我：好，先讲完整例子再加可选控件，以确认基本路径清楚。"
  },
  {
    "title": "09E Vocabulary in Context",
    "titleTranslate": "第09课E｜解释操作与工作流程",
    "text": "The navigator helps visitors move between sections, and the preferences panel lets them enable the features they need.\nThe user can replay the recording, download the text, or submit an answer before moving to the next exercise.\nThe user can scroll through the list, click a tab, and select the next unit before starting the exercise.\nClicking the icon should not collapse the panel unless the control is explicitly labeled as collapsible.\nThe application can switch modes, but it should explain the current mode before the user enters a command.\nA toast confirms the save action, while a more serious warning stays visible until the person has read it.\nThe selected option is marked with a clear indicator, and the secondary action appears below it.\nThe selector changes the active category, while the handlers respond to the specific events raised by each control.\nA timeout should lead to a clear retry option instead of leaving the interface in a state that looks permanently busy.\nThe user can exit the exercise and return to the same position without creating duplicate entries.\nThe navigation guide shows the available directions and the path back to the previous part of the workflow.",
    "textTranslate": "导航器帮助切换区块，偏好面板让人启用所需功能。\n用户可重播录音、下载文本，或提交答案后继续。\n用户可滚列表、点标签页，并在练习前选择下一单元。\n除非控件明确标成可折叠，点击图标不应折叠面板。\n应用可切换模式，但用户输入命令前应说明当前模式。\n短暂提示确认保存，更严重警告则持续到用户阅读。\n选项用清晰标记标注，辅助操作出现在下方。\n选择器改当前类别，处理函数响应控件引发事件。\n超时应提供重试选项，不让界面永远像忙碌状态。\n用户可退出练习并回同位置，不产生重复条目。\n导航指南展示方向及返回流程上一部分的路径。"
  },
  {
    "title": "10A Building a Lesson from Useful Material",
    "titleTranslate": "第10课A｜组织内容与学习材料",
    "text": "A useful lesson needs more than a long vocabulary list, because recognizing individual words is different from understanding a connected message.\nI begin with a learning task, such as explaining a project or describing a problem that someone needs help solving.\nThen I choose a short passage and a conversation that show how the relevant words and expressions work in that situation.\nThe vocabulary section explains the meaning used in the text, and additional examples show how that meaning changes with context.\nI also include a translation, but I encourage the learner to read the English first and use the Chinese only when necessary.\nFor listening practice, the learner should hear complete expressions rather than only isolated words with no natural rhythm or connection.\nA writing exercise can ask them to change the subject, replace the object, or adapt the sentence to their own work.\nThese small changes make the learner retrieve the structure instead of simply copying a sentence without considering its meaning.\nI finish with a few questions that invite a personal answer and make it possible to use several expressions together.\nThe aim is a manageable lesson that links reading, listening, vocabulary, grammar, and actual communication through one clear learning task.",
    "textTranslate": "有用课程不只要长词表，因为认出词汇不同于理解连贯信息。\n我先定学习任务，比如介绍项目或描述需要帮助解决的问题。\n再选短文和对话，展示相关词汇表达在该场景如何运作。\n词汇部分解释文中词义，补充例句展示语境如何影响含义。\n我也提供翻译，但鼓励先读英文，仅必要时看中文。\n听力练习应听完整表达，而不只是缺少节奏联系的孤立单词。\n写作练习可要求换主语、换宾语，或把句子用于自身工作。\n这些小改写迫使学习者提取结构，而不只是不理解含义地抄句子。\n最后给几个需要个人回答的问题，让多个表达能一起使用。\n目标是用一个明确任务，把阅读、听力、词汇、语法和实际沟通连接成可完成的课。"
  },
  {
    "title": "10B Learning Words in a Meaningful Context",
    "titleTranslate": "第10课B｜组织内容与学习材料",
    "text": "When I study a new word, I want to know what it means here, which words it often appears with, and how I can use it.\nA dictionary may offer several meanings, but the first example should make the meaning in the current lesson easy to understand.\nFor instance, review can describe checking a result, reading material again, or writing an evaluation of a product for other people.\nI do not need to memorize every meaning immediately, but I should recognize when the word is being used differently.\nI also pay attention to countability, because expressions such as some feedback and a few examples follow different grammatical patterns.\nWord forms matter too, so I connect develop with developed and developing rather than treat each spelling as a completely unrelated item.\nAfter reading, I try to produce a short sentence about my own project without looking at the reference example first.\nIf I get stuck, I return to the phrase, say it aloud, and use it in a slightly different sentence.\nLater lessons should bring useful words back in new situations so that review becomes part of understanding a new message.\nA word becomes valuable when I can recognize it, understand its role, and choose it naturally when I have something to say.",
    "textTranslate": "学习新词时，我想知道此处含义、常见搭配及如何使用。\n词典可能列多种意思，但首个例句应让本课词义容易理解。\n例如review可指检查结果、复习材料，或为他人写产品评测。\n我不必立即记所有意思，但应识别词义是否发生变化。\n我也注意可数性，因为some feedback与a few examples结构不同。\n词形也重要，我把develop与其过去式、进行形式关联，不当成无关词。\n阅读后，我不先看参考，试着写关于自己项目的短句。\n卡住时就回看词组、朗读，并用在略不同的句子里。\n后续课应在新场景复现实用词，让复习融入理解新信息。\n能认出词、理解作用，并表达时自然选用，它才真正有价值。"
  },
  {
    "title": "10C Working Conversation",
    "titleTranslate": "第10课C｜组织内容与学习材料",
    "text": "Learner: There are many words in this course; should I memorize every definition before I begin reading the first passage or conversation?\nTeacher: Start with the passage, identify the words that prevent understanding, and then study the meanings that are relevant to this lesson.\nLearner: What should I do with different forms, such as develop, developed, and developing, when they appear in separate exercises?\nTeacher: Keep them connected to the same base word, but notice the tense or grammatical role that each form has in its sentence.\nLearner: I can understand the example, but I cannot always produce a similar sentence when someone asks about my own project.\nTeacher: Practice changing one part at a time; replace the project, the action, or the reason, then say the new sentence aloud.\nLearner: Should I review the same list repeatedly, or use the expressions in different passages and ordinary conversations during the week?\nTeacher: Do both, but include active use; a short personal answer often reveals what you understand better than another round of silent reading.",
    "textTranslate": "学习者：课程词很多，读第一篇文章或对话前，要先背所有释义吗？\n老师：先读文章，找阻碍理解的词，再学与本课有关的意思。\n学习者：develop及不同词形出现在不同练习时，该怎么处理？\n老师：把它们关联到同一原形，同时注意各自时态或句中作用。\n学习者：我懂例句，但别人问我项目时，不一定能说类似句。\n老师：每次改一部分，替换项目、动作或理由，再朗读新句。\n学习者：应该反复看同一表，还是一周内在不同文章和交谈中使用？\n老师：两者都做，并主动使用；简短个人回答往往比再默读一轮更能检验理解。"
  },
  {
    "title": "10D Sentence Review",
    "titleTranslate": "第10课D｜组织内容与学习材料",
    "text": "A useful lesson needs more than a long vocabulary list, because recognizing individual words is different from understanding a connected message.\nThen I choose a short passage and a conversation that show how the relevant words and expressions work in that situation.\nI also include a translation, but I encourage the learner to read the English first and use the Chinese only when necessary.\nThese small changes make the learner retrieve the structure instead of simply copying a sentence without considering its meaning.\nWhen I study a new word, I want to know what it means here, which words it often appears with, and how I can use it.\nFor instance, review can describe checking a result, reading material again, or writing an evaluation of a product for other people.\nWord forms matter too, so I connect develop with developed and developing rather than treat each spelling as a completely unrelated item.\nLater lessons should bring useful words back in new situations so that review becomes part of understanding a new message.\nThere are many words in this course; should I memorize every definition before I begin reading the first passage or conversation?\nWhat should I do with different forms, such as develop, developed, and developing, when they appear in separate exercises?\nI can understand the example, but I cannot always produce a similar sentence when someone asks about my own project.\nShould I review the same list repeatedly, or use the expressions in different passages and ordinary conversations during the week?",
    "textTranslate": "有用课程不只要长词表，因为认出词汇不同于理解连贯信息。\n再选短文和对话，展示相关词汇表达在该场景如何运作。\n我也提供翻译，但鼓励先读英文，仅必要时看中文。\n这些小改写迫使学习者提取结构，而不只是不理解含义地抄句子。\n学习新词时，我想知道此处含义、常见搭配及如何使用。\n例如review可指检查结果、复习材料，或为他人写产品评测。\n词形也重要，我把develop与其过去式、进行形式关联，不当成无关词。\n后续课应在新场景复现实用词，让复习融入理解新信息。\n学习者：课程词很多，读第一篇文章或对话前，要先背所有释义吗？\n学习者：develop及不同词形出现在不同练习时，该怎么处理？\n学习者：我懂例句，但别人问我项目时，不一定能说类似句。\n学习者：应该反复看同一表，还是一周内在不同文章和交谈中使用？"
  },
  {
    "title": "10E Vocabulary in Context",
    "titleTranslate": "第10课E｜组织内容与学习材料",
    "text": "The course includes several scenarios, and each scenario begins with a short chat between two people with different responsibilities.\nThe messages look like ordinary emails, and the worksheet can also be printed on paper for offline review.\nThe syllabus includes a cloze exercise, flashcards, and a short exam that asks learners to use the target phrases.\nThe podcast has a transcript and subtitles, while the video provides another example of the same conversation.\nSeveral podcasts and videos use native speakers, while others rely on a clearly labeled synthetic voice.\nA male voice and another voice read the same examples, so learners can compare pronunciation without changing the vocabulary.\nThe lesson explains the subject and verb, then asks the learner to translate a complete sentence rather than isolated words.\nThe editor checks the formatting, the spelling of the headings, and the consistency of the teaching examples.\nThe editorial plan separates useful explanation from repetitive slop that adds length without helping the learner understand.\nThe narrator can distill a long conversation into a short digest, but the distillation must preserve the original meaning.\nThe documentary provides a clear narrative, while the audio recording lets learners hear the speaker's natural rhythm.\nUseful sources include original articles and carefully selected references, but a reference alone does not replace an explanation.\nThe learning material can be reused after its examples have been reviewed, and the reused text should remain accurate.\nA suitable microphone improves recording quality, while transcription turns the audio into text that can be searched and reviewed.",
    "textTranslate": "课程包含多个情境，每个以职责不同的两人短聊开始。\n信息像普通邮件，练习页也能印纸离线复习。\n大纲含完形填空、卡片及使用目标短语的短测。\n播客有文字稿和字幕，视频提供同一对话另一个例子。\n部分播客视频用母语者，其他使用明确标注的合成声音。\n男声与另一声音读相同例句，学习者可在词汇不变时比较发音。\n课程解释主语动词，再要求译整句而非孤词。\n编辑检查格式、标题拼写和教学例子一致性。\n编辑计划区分有用解释与只增长度却无助理解的重复堆砌。\n叙述者可把长对话提炼为摘要，但必须保原意。\n纪录片提供清晰叙事，录音让学习者听自然节奏。\n来源可含原创文章和精选参考，但参考本身不能替代解释。\n例子审阅后可复用学习材料，复用文本仍需准确。\n合适麦克风改善录音质量，转录把音频变成可搜索复习文字。"
  },
  {
    "title": "11A Finding the Part That Needs to Change",
    "titleTranslate": "第11课A｜找到并说明具体对象",
    "text": "Before changing a feature, I want to find the file or component that controls the behavior I can see on the page.\nA project may contain many folders, so a clear question is more useful than opening unrelated files and guessing where to begin.\nI describe the visible element, name the page where it appears, and explain which action or state I am trying to understand.\nFor example, I may need the component that renders the course cover and the function that chooses which image to display.\nThe answer should connect those pieces and show how information moves from the source data into the final rendered page.\nA directory name can provide a clue, but it does not prove that every file inside has the same responsibility or purpose.\nI also look for existing helpers that handle the same problem, because using the established approach can keep related pages consistent.\nWhen the relevant code is found, I ask for a short explanation of its inputs, outputs, and important connections to other modules.\nThis makes it easier to identify the smallest meaningful change and understand which behavior might need to be checked afterward.\nThe goal is not to memorize the entire repository, but to build a useful map of the parts involved in the current task.",
    "textTranslate": "修改功能前，我想找到控制页面可见行为的文件或组件。\n项目目录很多，清晰提问比乱开文件猜起点更有用。\n我描述可见元素、所在页面，并解释想理解的操作或状态。\n例如可能需要找到渲染课程封面的组件及决定图片的函数。\n回答应连接这些部分，说明信息如何从源数据进入最终页面。\n目录名可以提供线索，却不能证明内部文件职责相同。\n我也找处理同类问题的既有辅助函数，沿用现有方法保持页面一致。\n找到代码后，我会要求简述输入、输出和与其他模块的重要联系。\n这样更易找到最小有意义改动，并理解后续检查哪些行为。\n目标不是背下整个仓库，而是建立当前任务相关部分的实用地图。"
  },
  {
    "title": "11B Explaining How the Pieces Fit Together",
    "titleTranslate": "第11课B｜找到并说明具体对象",
    "text": "A good explanation of an implementation describes responsibilities and relationships before going through every line of a long function.\nSuppose that the application shows a list of lessons, and each lesson has a title, an image, and a short description.\nOne module retrieves the data, another prepares the display values, and a component renders the information that the user sees.\nThe file containing the query may be different from the file containing the markup, even though both affect the same page.\nIf an image is missing, we need to understand whether the stored path is empty or the rendering logic uses it incorrectly.\nThese possibilities suggest different changes, so locating the visible component alone may not identify the actual source of the problem.\nI prefer examples that follow one piece of data through the relevant functions and explain what each step adds or changes.\nTechnical names are useful when they identify a specific object, but the explanation should also describe its role in ordinary language.\nA simple diagram or a short sequence can sometimes explain the relationship more clearly than a large block of copied code.\nOnce the connection is clear, we can discuss the change without treating the whole project as one mysterious and inseparable system.",
    "textTranslate": "好的实现说明先描述职责和关系，再逐行解释长函数。\n假设应用显示课程列表，每课有标题、图片和简短描述。\n一个模块取数据，一个准备显示值，组件则渲染用户看到的信息。\n查询文件可能不同于页面标记文件，虽然都影响同一页面。\n图片缺失时，要区分存储路径为空，还是渲染逻辑用错。\n两种可能对应不同修改，所以只找到组件未必找到问题根源。\n我偏好沿一条数据经过相关函数，说明每步添加或改变什么。\n技术名称可定位具体对象，但还应以普通语言解释作用。\n简单图示或短流程有时比大段复制代码更清楚。\n关系清楚后，就能讨论修改，不把项目视作神秘不可分整体。"
  },
  {
    "title": "11C Working Conversation",
    "titleTranslate": "第11课C｜找到并说明具体对象",
    "text": "Me: Could you find the component that shows the course cover and explain where its image path comes from before changing the layout?\nDeveloper: The display component receives prepared lesson data, while a separate module retrieves the record and chooses the values used on the page.\nMe: Please show me the function that prepares those values, because I want to understand whether the missing image is a data problem.\nDeveloper: I will trace one lesson from the database record to the rendered card and identify the step where the path becomes empty.\nMe: Is there an existing helper that handles the same kind of image on other pages, or does this component use separate logic?\nDeveloper: There is a shared helper; I will explain its current contract and compare this page with another page that already uses it.\nMe: Good; propose the smallest change that restores the image and keeps the related pages consistent, then explain what should be reviewed.\nDeveloper: I will describe the relevant inputs, outputs, and affected views so that the change is understandable before implementation begins.",
    "textTranslate": "我：改布局前，能找到课程封面组件并解释图片路径来源吗？\n开发者：显示组件接收整理过的课程数据，另一个模块取记录并选择页面值。\n我：请展示准备值的函数，我想知道图片缺失是否为数据问题。\n开发者：我会跟踪一课从数据库到卡片的过程，找到路径变空的步骤。\n我：其他页面是否有处理同类图片的辅助函数，还是此组件另写逻辑？\n开发者：有共享辅助函数，我会解释其约定并与已使用它的页面比较。\n我：好，提出恢复图片并保持相关页面一致的最小改动，再说明检查内容。\n开发者：会说明相关输入、输出和受影响视图，使实现前就能理解改动。"
  },
  {
    "title": "11D Sentence Review",
    "titleTranslate": "第11课D｜找到并说明具体对象",
    "text": "Before changing a feature, I want to find the file or component that controls the behavior I can see on the page.\nI describe the visible element, name the page where it appears, and explain which action or state I am trying to understand.\nThe answer should connect those pieces and show how information moves from the source data into the final rendered page.\nWhen the relevant code is found, I ask for a short explanation of its inputs, outputs, and important connections to other modules.\nA good explanation of an implementation describes responsibilities and relationships before going through every line of a long function.\nOne module retrieves the data, another prepares the display values, and a component renders the information that the user sees.\nThese possibilities suggest different changes, so locating the visible component alone may not identify the actual source of the problem.\nA simple diagram or a short sequence can sometimes explain the relationship more clearly than a large block of copied code.\nCould you find the component that shows the course cover and explain where its image path comes from before changing the layout?\nPlease show me the function that prepares those values, because I want to understand whether the missing image is a data problem.\nIs there an existing helper that handles the same kind of image on other pages, or does this component use separate logic?\nGood; propose the smallest change that restores the image and keeps the related pages consistent, then explain what should be reviewed.",
    "textTranslate": "修改功能前，我想找到控制页面可见行为的文件或组件。\n我描述可见元素、所在页面，并解释想理解的操作或状态。\n回答应连接这些部分，说明信息如何从源数据进入最终页面。\n找到代码后，我会要求简述输入、输出和与其他模块的重要联系。\n好的实现说明先描述职责和关系，再逐行解释长函数。\n一个模块取数据，一个准备显示值，组件则渲染用户看到的信息。\n两种可能对应不同修改，所以只找到组件未必找到问题根源。\n简单图示或短流程有时比大段复制代码更清楚。\n我：改布局前，能找到课程封面组件并解释图片路径来源吗？\n我：请展示准备值的函数，我想知道图片缺失是否为数据问题。\n我：其他页面是否有处理同类图片的辅助函数，还是此组件另写逻辑？\n我：好，提出恢复图片并保持相关页面一致的最小改动，再说明检查内容。"
  },
  {
    "title": "11E Vocabulary in Context",
    "titleTranslate": "第11课E｜找到并说明具体对象",
    "text": "The editor can insert a line, create a new prompt, and organize related prompts into a small collection.\nThe template engine handles generation, while the browser must render the resulting page and complete hydration before some interactions work.\nThe code uses nesting to group conditions, and the keys identify the values inside the generated object.\nThe script adds tags to each document and creates a readable slug for its public URL.\nThe source tree contains folders, scripts, and documents, and each file should have a clearly described responsibility.\nA code comment explains why the branch exists, while the surrounding comments describe the unusual edge cases.\nThe function receives an array of items and returns a non-null value that matches the declared type.\nA union type allows several variants, and each variant carries attributes that identify its particular role.\nThe node has two children, and the root keeps a reference to the start of the whole structure.\nThe generator imports a template, inserts the data, and stores the resulting document in the workspace.\nA loader and a fetcher handle different stages of loading, so their names should make that distinction clear.\nThe listener receives signals, while a router maps the incoming request to the function that handles it.\nA lint command checks common code issues, and a diff shows which lines changed during the revision.\nThe script can print an index, indent nested output, and truncate a line that is longer than the display allows.\nAn adapter connects the shared interface to a provider, while the integration keeps external details out of the central module.\nThe runtime can bind a handler, generate a key, and pass the result through a pipe to another process.\nThe framework may bootstrap the application before initializing components and attaching the event listeners that they require.\nThe test harness uses a mock response so that execution does not depend on a real external service.\nA schema describes the expected fields, while the actual record contains the values that were stored.\nThe executor runs the submitted action, and the execution report records whether that action was executed successfully.\nThe technical note distinguishes a variable, a property, and an attribute using examples from the current implementation.\nThe file was referenced by another module, and several references need to be updated if its path changes.",
    "textTranslate": "编辑器可插入行、创建提示词，并把相关提示词组织成小集合。\n模板引擎处理生成，浏览器需渲染页面并完成水合，部分交互才可用。\n代码以嵌套组织条件，键标识生成对象中的值。\n脚本为文档加标签，并生成公开网址的可读标识。\n源树含目录、脚本和文档，每个文件应有清楚职责。\n代码注释解释分支存在原因，周围注释说明特殊边界情况。\n函数接收条目数组，返回匹配声明类型的非空值。\n联合类型允许多个变体，各变体有标识角色的属性。\n节点有两个子项，根保留整个结构起点引用。\n生成器导入模板、插入数据，并把结果文档存工作区。\n加载器和取数器处理不同阶段，名称应清楚区分。\n监听器接收信号，路由器把请求映射到处理函数。\n静态检查命令查常见问题，差异对比显示修订中改了哪些行。\n脚本可打印索引、缩进嵌套输出，并截断超过显示长度的行。\n适配器连接共享接口与服务商，集成将外部细节隔离于中央模块。\n运行时可绑定处理器、生成键，并通过管道传给另一个进程。\n框架可能先引导启动应用，再初始化组件并附加所需监听器。\n测试框架用模拟响应，使执行不依赖真实外部服务。\n结构定义描述预期字段，实际记录则含已存的值。\n执行器运行提交动作，执行报告记录是否执行成功。\n技术笔记用当前实现例子区分变量、属性和特征字段。\n该文件被别的模块引用，路径变化时多处引用需更新。"
  },
  {
    "title": "12A Understanding Where a Service Runs",
    "titleTranslate": "第12课A｜描述环境与运行状态",
    "text": "Before I ask why a service is unavailable, I first need to know where it runs and how a request reaches it.\nAn application may run directly on the host, inside a container, or within a virtual machine that has its own environment.\nThese arrangements can look similar in a browser while depending on different ports, network routes, and configuration files behind the scenes.\nI describe the actual setup before proposing a change, because restarting the wrong service may not affect the problem at all.\nThe next step is to check which process is running and whether it is listening at the address that the client uses.\nA running process does not automatically mean that the application is reachable from every other machine or environment on the network.\nThe request may still be blocked, sent to the wrong port, or directed through a proxy that is configured differently than expected.\nI find it helpful to follow one request from the browser to the application and identify each important connection along that path.\nThis creates a shared explanation of the environment instead of a collection of unrelated commands that happen to change its state.\nOnce the path is clear, we can investigate the specific point where the expected behavior stops and choose an appropriate next action.",
    "textTranslate": "询问服务为何不可用前，应先知道它在哪里运行、请求如何到达。\n应用可能直接在宿主机、容器，或有独立环境的虚拟机中运行。\n浏览器里看着相似，背后依赖的端口、网络路由和配置文件却不同。\n我先说明实际配置再建议修改，因为重启错误服务可能毫无帮助。\n下一步检查哪个进程在运行，是否监听客户端使用的地址。\n进程运行不等于网络中每个机器和环境都能访问应用。\n请求可能仍被阻挡、发错端口，或经过配置不符预期的代理。\n我会沿一条请求从浏览器到应用，确认路径中每个重要连接。\n这样形成共同环境解释，而不是一组碰巧改变状态的无关命令。\n路径明确后，就能找预期行为停止的具体位置并选下一步。"
  },
  {
    "title": "12B Separating Configuration from Runtime State",
    "titleTranslate": "第12课B｜描述环境与运行状态",
    "text": "Configuration describes how a system is intended to behave, while runtime state describes what it is actually doing at a particular moment.\nA file may say that a service should start automatically, but the current process can still be stopped because an earlier attempt failed.\nLikewise, changing a configuration file does not always update a running process immediately; some applications need a reload or a restart.\nI therefore ask which settings were changed, when they were applied, and what evidence shows that the service is using them now.\nThis distinction is especially useful when a project has separate local, testing, and production environments that share similar names.\nA successful change on my laptop does not prove that the same configuration is active on the server used by other people.\nI also distinguish unavailable from stopped, because a service can be running but unreachable from a particular client or network.\nAn explanation should name the environment and the observed state, rather than simply say that everything is online or offline.\nWhen the settings and state are documented separately, it becomes easier to repeat a setup and understand why two machines behave differently.\nThe result is a more reliable conversation about what needs to change, what is already correct, and what still requires direct observation.",
    "textTranslate": "配置描述系统打算如何工作，运行状态则描述某时刻实际在做什么。\n文件可能指定自动启动，但先前启动失败后进程仍可能停止。\n修改配置也不一定立即更新进程，部分应用需重载或重启。\n因此我会问改了哪些设置、何时应用，以及什么证据表明服务正在使用。\n本地、测试、生产环境名称相似时，这个区别尤其有用。\n笔记本修改成功，不能证明其他用户访问的服务器已用相同配置。\n我也区分不可访问与已停止，因为运行服务也可能对某客户端不可达。\n说明应指出环境和观察状态，而不是笼统说一切在线或离线。\n分别记录设置与状态，更易复现环境并理解两台机器为何不同。\n这样能更可靠地讨论哪些要改、哪些正确、哪些还需观察。"
  },
  {
    "title": "12C Working Conversation",
    "titleTranslate": "第12课C｜描述环境与运行状态",
    "text": "Me: Could you check which services are running inside the virtual machine and distinguish them from the services running directly on the host?\nOperator: Yes; I will identify the processes and their ports, then explain how the browser reaches the application from the host environment.\nMe: The configuration says the service starts automatically, but does that prove it is actually running after the last restart this morning?\nOperator: No; we need to inspect the current state and check whether the most recent startup attempt succeeded or returned an error.\nMe: Please also explain whether the changed settings have been applied, because I edited the file but did not restart the process afterward.\nOperator: I will check how this application loads configuration and whether it supports a reload without restarting the entire environment or losing work.\nMe: Good; keep the explanation focused on this actual setup, and show where a request stops if the browser cannot reach the service.\nOperator: I will report the environment, the observed state, and the evidence for each conclusion before proposing the change needed to restore access.",
    "textTranslate": "我：能检查虚拟机内运行的服务，并与宿主机服务区分吗？\n运维者：可以，先确认进程端口，再解释宿主环境浏览器怎样访问应用。\n我：配置写自动启动，能证明今早重启后确实运行吗？\n运维者：不能，需要检查当前状态及最近启动是否成功或报错。\n我：也请解释新设置是否已应用，因为我编辑后没重启进程。\n运维者：会检查应用如何加载配置，能否不重启整个环境或丢工作就重载。\n我：好，聚焦实际配置，若浏览器访问不了，就展示请求停在哪。\n运维者：会先报告环境、状态和结论证据，再建议恢复访问的修改。"
  },
  {
    "title": "12D Sentence Review",
    "titleTranslate": "第12课D｜描述环境与运行状态",
    "text": "Before I ask why a service is unavailable, I first need to know where it runs and how a request reaches it.\nThese arrangements can look similar in a browser while depending on different ports, network routes, and configuration files behind the scenes.\nThe next step is to check which process is running and whether it is listening at the address that the client uses.\nI find it helpful to follow one request from the browser to the application and identify each important connection along that path.\nConfiguration describes how a system is intended to behave, while runtime state describes what it is actually doing at a particular moment.\nLikewise, changing a configuration file does not always update a running process immediately; some applications need a reload or a restart.\nA successful change on my laptop does not prove that the same configuration is active on the server used by other people.\nWhen the settings and state are documented separately, it becomes easier to repeat a setup and understand why two machines behave differently.\nCould you check which services are running inside the virtual machine and distinguish them from the services running directly on the host?\nThe configuration says the service starts automatically, but does that prove it is actually running after the last restart this morning?\nPlease also explain whether the changed settings have been applied, because I edited the file but did not restart the process afterward.\nGood; keep the explanation focused on this actual setup, and show where a request stops if the browser cannot reach the service.",
    "textTranslate": "询问服务为何不可用前，应先知道它在哪里运行、请求如何到达。\n浏览器里看着相似，背后依赖的端口、网络路由和配置文件却不同。\n下一步检查哪个进程在运行，是否监听客户端使用的地址。\n我会沿一条请求从浏览器到应用，确认路径中每个重要连接。\n配置描述系统打算如何工作，运行状态则描述某时刻实际在做什么。\n修改配置也不一定立即更新进程，部分应用需重载或重启。\n笔记本修改成功，不能证明其他用户访问的服务器已用相同配置。\n分别记录设置与状态，更易复现环境并理解两台机器为何不同。\n我：能检查虚拟机内运行的服务，并与宿主机服务区分吗？\n我：配置写自动启动，能证明今早重启后确实运行吗？\n我：也请解释新设置是否已应用，因为我编辑后没重启进程。\n我：好，聚焦实际配置，若浏览器访问不了，就展示请求停在哪。"
  },
  {
    "title": "12E Vocabulary in Context",
    "titleTranslate": "第12课E｜描述环境与运行状态",
    "text": "A stream carries updates while the connection remains open, and a log records the responses that the client receives.\nThe tail of the logs shows the most recent event, and the monitor counts the hits on the relevant endpoint.\nThe daemon runs in the background, while a terminal command displays the service's current health and listening address.\nThe installed plugin is compatible with the current stack, but a preinstalled extension may use a different configuration.\nThe config uses a default route, and the router applies the rules that determine where the request goes next.\nWe checked the routes and the rule that sends traffic through the tunnel before changing any network settings.\nA proxy sniffer may inspect traffic, so its role and access should be understood before enabling it.\nThe devices use the same network, but each device has its own local address and available ports.\nThe service can handle concurrent calls, although the number of connections remains limited by the configured resources.\nThe browser uses the login page to create a session, and the session lifetime depends on the application settings.\nA locale controls language and regional formatting, while the underlying content remains the same.\nThe application can use a websocket to keep a connection open while exchanging updates in both directions.\nThe dock shows the active applications, and a separate window displays the console output for the current process.\nThe monitor shows the process count, memory usage, and the network traffic associated with the running application.",
    "textTranslate": "连接开放时流传送更新，日志记录客户端所收响应。\n日志尾部显示最近事件，监控器统计相关端点命中。\n守护进程后台运行，终端命令展示当前健康状态及监听地址。\n已装插件兼容当前技术栈，但预装扩展可能用不同配置。\n配置用默认路由，路由器按规则决定请求去向。\n修改网络设置前，我们查路由及经隧道发送流量的规则。\n代理嗅探器可能检查流量，启用前应理解作用权限。\n设备同网，但各有本地地址和可用端口。\n服务可处理并发调用，但连接数仍受配置资源限制。\n浏览器用登录页创建会话，时效取决于应用设置。\n语言地区设置控制语言和地区格式，底层内容保持相同。\n应用可用双向持久连接保持连通并双向交换更新。\n程序坞展示活动应用，独立窗口显示当前进程控制台输出。\n监控器展示进程数、内存用量及应用相关流量。"
  },
  {
    "title": "13A Describing a Problem Before Trying to Fix It",
    "titleTranslate": "第13课A｜讲述一次故障",
    "text": "Yesterday I opened the course page and noticed that the topic menu was empty, although I expected several saved topics to appear.\nI had been reviewing the lesson content, so the missing options interrupted the task and made it impossible to continue normally.\nBefore changing anything, I wrote down the page I visited, the action I took, and the result that I actually saw.\nI also described the expected behavior, because an empty menu might be correct in one situation and a problem in another.\nThe page itself loaded successfully, but the request that should have retrieved the topics returned an error instead of the expected data.\nAt that point, I could distinguish the visible symptom from the particular operation that failed behind the interface.\nI checked whether the issue happened again after returning to the page and whether another lesson showed the same missing options.\nThese observations did not explain the cause yet, but they gave the investigation a much clearer starting point than a general complaint.\nWhen I asked for help, I included the relevant error message and avoided adding guesses that I could not support with evidence.\nA clear account of what happened made the next conversation shorter and helped the other person focus on the actual failure.",
    "textTranslate": "昨天打开课程页时，我发现主题菜单为空，虽然预期应显示几个已保存主题。\n当时我在检查课程内容，缺少选项打断任务，让我无法正常继续。\n修改前，我记录访问页面、执行操作和实际看到的结果。\n我也描述预期行为，因为某种情境中空菜单正确，另一种却有问题。\n页面本身加载成功，但应获取主题的请求返回错误而非预期数据。\n此时我能区分可见症状，与界面背后失败的具体操作。\n我检查重访页面是否再次出现问题，以及其他课程是否同样缺选项。\n观察尚未解释原因，却比泛泛抱怨提供更清晰起点。\n求助时，我附上相关错误信息，避免加入无证据猜测。\n清楚叙述发生的事让后续沟通更短，也让对方聚焦实际故障。"
  },
  {
    "title": "13B Writing a Useful Reproduction",
    "titleTranslate": "第13课B｜讲述一次故障",
    "text": "A reproduction describes the steps that lead to a problem so that another person can observe the same behavior independently.\nIt should begin with the necessary starting conditions, such as the selected account, the current page, and any required saved data.\nThen it lists the actions in the order they occurred, using precise verbs instead of broad instructions such as use the application.\nFor example, I can say that I opened the lesson, selected the topic menu, and waited for the options to load.\nThe description should separate the expected result from the actual result and note whether the problem occurs every time or only sometimes.\nIf the issue appeared while another operation was running, that background activity may matter and should be mentioned without assuming a connection.\nI also record what changed recently, while keeping a recent change separate from a confirmed explanation of why the problem happened.\nA good reproduction does not need every detail of the entire session; it needs the details that another person must repeat to see the issue.\nOnce the problem has been fixed, the same sequence becomes a practical way to check whether the original failure has really disappeared.\nThis turns a confusing experience into a small, repeatable example that supports both investigation and a clear explanation of the result.",
    "textTranslate": "复现说明描述导致问题的步骤，让别人能独立观察同样行为。\n应先写必要初始条件，比如选中账号、当前页面及需要的已保存数据。\n再按发生顺序列操作，用精确动词，而不写使用应用等笼统指令。\n例如说打开课程、选择主题菜单，并等待选项加载。\n应区分预期与实际结果，并说明每次发生还是偶尔发生。\n若问题出现时另一操作正在运行，应提及该背景，但不武断认定关联。\n也记录近期改动，但近期改动不等于已确认原因。\n好的复现不必包含整次会话所有细节，只需让别人重现问题的必要信息。\n修复后，相同步骤可用于检查原故障是否真正消失。\n这样把困惑经历变成小而可重复的例子，支持调查和解释结果。"
  },
  {
    "title": "13C Working Conversation",
    "titleTranslate": "第13课C｜讲述一次故障",
    "text": "Me: Yesterday I opened a lesson and selected the topic menu, but no options appeared even though the database should contain several topics.\nDeveloper: Were you changing the lesson while the page was loading, or did you wait until the ordinary content had already appeared?\nMe: I waited for the content, then opened the menu; the page looked normal, but the request for topics returned an error.\nDeveloper: Does the same problem happen when you repeat those steps with another lesson, using the same account and browser session?\nMe: Yes, it happened again; I have recorded the steps, the expected options, and the actual response so that you can reproduce it.\nDeveloper: That helps; I will investigate the failed request before changing the visible menu, because the symptom alone does not identify the cause.\nMe: Please also note any recent changes that may be relevant, but keep those possibilities separate from what the evidence actually confirms.\nDeveloper: After the fix, I will repeat your reproduction and check whether the menu works with both the original lesson and another example.",
    "textTranslate": "我：昨天打开课程选主题菜单，没有选项，虽然数据库应该有几个主题。\n开发者：页面加载时你在修改课程，还是等普通内容显示后才操作？\n我：等内容显示才开菜单，页面正常，但主题请求报错。\n开发者：同账号同浏览器会话，换另一课重复这些步骤也有问题吗？\n我：有，我已记录步骤、预期选项和实际响应，方便复现。\n开发者：有帮助，先查失败请求，再改可见菜单，因为症状本身不能确定原因。\n我：也请留意可能相关的近期改动，但将可能性与已证实内容分开。\n开发者：修复后会重复步骤，检查原课程及另一个例子菜单是否正常。"
  },
  {
    "title": "13D Sentence Review",
    "titleTranslate": "第13课D｜讲述一次故障",
    "text": "Yesterday I opened the course page and noticed that the topic menu was empty, although I expected several saved topics to appear.\nBefore changing anything, I wrote down the page I visited, the action I took, and the result that I actually saw.\nThe page itself loaded successfully, but the request that should have retrieved the topics returned an error instead of the expected data.\nThese observations did not explain the cause yet, but they gave the investigation a much clearer starting point than a general complaint.\nA reproduction describes the steps that lead to a problem so that another person can observe the same behavior independently.\nThen it lists the actions in the order they occurred, using precise verbs instead of broad instructions such as use the application.\nIf the issue appeared while another operation was running, that background activity may matter and should be mentioned without assuming a connection.\nOnce the problem has been fixed, the same sequence becomes a practical way to check whether the original failure has really disappeared.\nYesterday I opened a lesson and selected the topic menu, but no options appeared even though the database should contain several topics.\nI waited for the content, then opened the menu; the page looked normal, but the request for topics returned an error.\nYes, it happened again; I have recorded the steps, the expected options, and the actual response so that you can reproduce it.\nPlease also note any recent changes that may be relevant, but keep those possibilities separate from what the evidence actually confirms.",
    "textTranslate": "昨天打开课程页时，我发现主题菜单为空，虽然预期应显示几个已保存主题。\n修改前，我记录访问页面、执行操作和实际看到的结果。\n页面本身加载成功，但应获取主题的请求返回错误而非预期数据。\n观察尚未解释原因，却比泛泛抱怨提供更清晰起点。\n复现说明描述导致问题的步骤，让别人能独立观察同样行为。\n再按发生顺序列操作，用精确动词，而不写使用应用等笼统指令。\n若问题出现时另一操作正在运行，应提及该背景，但不武断认定关联。\n修复后，相同步骤可用于检查原故障是否真正消失。\n我：昨天打开课程选主题菜单，没有选项，虽然数据库应该有几个主题。\n我：等内容显示才开菜单，页面正常，但主题请求报错。\n我：有，我已记录步骤、预期选项和实际响应，方便复现。\n我：也请留意可能相关的近期改动，但将可能性与已证实内容分开。"
  },
  {
    "title": "13E Vocabulary in Context",
    "titleTranslate": "第13课E｜讲述一次故障",
    "text": "Please debug the failed request before changing the page, and raise a separate issue if another failure appears during the investigation.\nI didn't see the warning at first, and the application doesn't explain what happens when the request is rejected.\nThe page shows a broken image, and I don't know whether the original file is missing or the path is wrong.\nThe system suddenly became disconnected while it was uploading a file, and the partial result looked incomplete.\nThe developer encountered a bug while debugging the menu, then discovered that an earlier patch had changed its behavior.\nA crash can drop a connection, but the visible symptom alone does not establish which component failed first.\nThe recent patch was applied, yet the bug appeared again because a different process was still using the older settings.\nThe reference response is false in this example, while the actual result is true; the mismatch needs a precise description.\nThe first call failed, but two later calls succeeded, so the issue is intermittent rather than constant.\nThe old report had omitted the browser version, which made the issue difficult to reproduce on another machine.\nThe missing input created a mess, but repeating the same steps helped us separate two different messes into independent issues.",
    "textTranslate": "请先调试失败请求再改页面，调查中若有其他故障另提问题。\n起初没看到警告，应用也不解释请求被拒后怎样。\n页面图片损坏，我不知原文件缺失还是路径错。\n上传中系统突然断连，部分结果看着不完整。\n开发者调试菜单时遇到缺陷，发现之前补丁改变行为。\n崩溃可能断连接，但可见症状不能确定哪个组件先失败。\n补丁已应用，但另一进程仍用旧设置，所以故障再现。\n示例参考响应为假，实际为真，差异需精确描述。\n首次调用失败，之后两次成功，所以问题间歇发生。\n旧报告遗漏浏览器版本，导致其他机器难复现。\n缺输入造成混乱，重复步骤帮助把两种混乱分为独立问题。"
  },
  {
    "title": "14A Following the Evidence to a Cause",
    "titleTranslate": "第14课A｜分析原因并解释结果",
    "text": "Once a problem can be reproduced, I look for evidence that distinguishes possible causes instead of trying unrelated changes at random.\nIn the empty menu example, the browser showed a failed request, so the next useful question concerned the response from the server.\nWe compared the request with the expected endpoint and discovered that the application was using an incorrect configuration value.\nThat observation suggested a cause, but we still needed to check whether correcting the value restored the expected data and visible options.\nAfter the correction, the request succeeded and the menu displayed the topics that were already stored in the database.\nWe then repeated the original steps with another lesson to see whether the same explanation fit more than one example.\nThis sequence connected the visible problem, the underlying request, the incorrect value, and the result of the specific change.\nIt also helped us avoid a misleading explanation in which refreshing the page appeared to be the entire solution.\nA cause should explain the evidence and predict what will change when the relevant condition is corrected or removed.\nThe clearer that connection becomes, the easier it is to describe the fix and decide which related behavior still needs attention.",
    "textTranslate": "问题能复现后，我寻找区分可能原因的证据，不随机尝试无关修改。\n空菜单例子中浏览器请求失败，因此下一问题是服务器返回什么。\n我们比较请求与预期端点，发现应用使用错误配置值。\n观察提示原因，但仍需检查修正值能否恢复数据及可见选项。\n修正后，请求成功，菜单显示数据库已存主题。\n再用另一课重复原步骤，查看解释是否不只适用于单例。\n这个过程连接可见问题、底层请求、错误值和具体修改结果。\n也避免误以为刷新页面就是完整解决方案。\n原因应解释证据，并预测相关条件纠正或移除后什么会改变。\n联系越清楚，越容易解释修复并决定还需关注哪些相关行为。"
  },
  {
    "title": "14B Explaining a Fix Without Overstating It",
    "titleTranslate": "第14课B｜分析原因并解释结果",
    "text": "After fixing a problem, I want the report to explain the trigger, the cause, the change, and the evidence that supports the conclusion.\nA short statement that everything works is not enough when only one page or one request has actually been observed.\nI describe what failed before the change and what now happens when the same sequence is repeated with the corrected configuration.\nIf another environment has not been checked, I say so rather than imply that a local result proves every remote deployment is correct.\nThis distinction makes the report more useful, because it shows the practical limits of the evidence without hiding the successful result.\nI also note any remaining uncertainty that could change the next decision, such as whether an old process is still using the previous settings.\nAn effective explanation uses because when there is a supported reason and words such as may when the connection is still uncertain.\nIf the same issue returns, the report should help us identify whether the original condition has returned or a different cause is involved.\nA careful report is therefore part of solving the problem, because it preserves the reasoning that would otherwise disappear after the immediate task.\nIt gives the next person a concrete starting point and reduces the chance of repeating a change without understanding why it helped.",
    "textTranslate": "修复后，我希望报告解释触发条件、原因、修改及支持结论的证据。\n只观察一个页面或请求时，仅说一切正常并不足够。\n我描述改前哪里失败，以及修正配置后重复相同步骤会怎样。\n未检查其他环境时，应明确说明，不暗示本地成功证明所有远端正常。\n这让报告更有用，既展现证据边界，也不掩盖成功结果。\n也记录影响下一决定的不确定性，例如旧进程是否仍用旧设置。\n有根据时用because说明原因，仍不确定时用may等词。\n若问题复发，报告应帮助判断原条件重现，还是另有原因。\n因此仔细报告也是解决问题的一部分，保留即时任务后可能遗失的推理。\n为下一人提供具体起点，减少不明原理地重复修改。"
  },
  {
    "title": "14C Working Conversation",
    "titleTranslate": "第14课C｜分析原因并解释结果",
    "text": "Me: We can reproduce the empty menu now; what evidence would help us distinguish a missing record from a request sent to the wrong endpoint?\nDeveloper: We should inspect the response and compare the configured address with the expected endpoint before modifying the menu component or database records.\nMe: If the configuration is wrong, can we change only that value and repeat the same steps to see whether the result changes?\nDeveloper: Yes; that will give us a focused comparison and help us explain whether the configuration caused this particular failure.\nMe: The request now succeeds and the topics appear; please also try another lesson so we know whether the same explanation applies there.\nDeveloper: Both examples work after the correction, but I have not yet checked the production environment or confirmed which settings its process uses.\nMe: Include that limit in the report, along with the original trigger, the corrected value's role, and the observations that support the fix.\nDeveloper: I will separate the confirmed local result from the remaining deployment check and explain exactly what the next verification needs to establish.",
    "textTranslate": "我：现在能复现空菜单，什么证据能区分缺记录与请求发错端点？\n开发者：先查响应并比较配置地址与预期端点，再改菜单组件或记录。\n我：若配置错了，能只改那个值再重复步骤，观察结果变化吗？\n开发者：可以，这能提供聚焦比较，并判断配置是否导致该故障。\n我：现在请求成功且主题出现，请试另一课，确认解释是否也适用。\n开发者：修正后两例正常，但尚未查生产环境及其进程所用设置。\n我：报告中写清限制、原触发条件、修正值的作用及支持修复的观察。\n开发者：会区分已确认本地结果和待查部署，并说明下一核对要证实什么。"
  },
  {
    "title": "14D Sentence Review",
    "titleTranslate": "第14课D｜分析原因并解释结果",
    "text": "Once a problem can be reproduced, I look for evidence that distinguishes possible causes instead of trying unrelated changes at random.\nWe compared the request with the expected endpoint and discovered that the application was using an incorrect configuration value.\nAfter the correction, the request succeeded and the menu displayed the topics that were already stored in the database.\nIt also helped us avoid a misleading explanation in which refreshing the page appeared to be the entire solution.\nAfter fixing a problem, I want the report to explain the trigger, the cause, the change, and the evidence that supports the conclusion.\nI describe what failed before the change and what now happens when the same sequence is repeated with the corrected configuration.\nI also note any remaining uncertainty that could change the next decision, such as whether an old process is still using the previous settings.\nA careful report is therefore part of solving the problem, because it preserves the reasoning that would otherwise disappear after the immediate task.\nWe can reproduce the empty menu now; what evidence would help us distinguish a missing record from a request sent to the wrong endpoint?\nIf the configuration is wrong, can we change only that value and repeat the same steps to see whether the result changes?\nThe request now succeeds and the topics appear; please also try another lesson so we know whether the same explanation applies there.\nInclude that limit in the report, along with the original trigger, the corrected value's role, and the observations that support the fix.",
    "textTranslate": "问题能复现后，我寻找区分可能原因的证据，不随机尝试无关修改。\n我们比较请求与预期端点，发现应用使用错误配置值。\n修正后，请求成功，菜单显示数据库已存主题。\n也避免误以为刷新页面就是完整解决方案。\n修复后，我希望报告解释触发条件、原因、修改及支持结论的证据。\n我描述改前哪里失败，以及修正配置后重复相同步骤会怎样。\n也记录影响下一决定的不确定性，例如旧进程是否仍用旧设置。\n因此仔细报告也是解决问题的一部分，保留即时任务后可能遗失的推理。\n我：现在能复现空菜单，什么证据能区分缺记录与请求发错端点？\n我：若配置错了，能只改那个值再重复步骤，观察结果变化吗？\n我：现在请求成功且主题出现，请试另一课，确认解释是否也适用。\n我：报告中写清限制、原触发条件、修正值的作用及支持修复的观察。"
  },
  {
    "title": "14E Vocabulary in Context",
    "titleTranslate": "第14课E｜分析原因并解释结果",
    "text": "We can optimize the query after understanding the evidence, rather than relying on a guess about which part is slow.\nThe research includes observations from several examples, and researching the difference may explain why only one environment fails.\nThe analysis detected an invalid value, and correcting that value resolves the failure in the reproduced example.\nThe evidence supports this explanation, but the data has not yet been verified against the original source.\nThe crawler follows public links, while a separate tool can scrape the text from the pages found during the crawl.\nSearch results can guide an investigation, but the highest ranking result is not automatically the most reliable source.\nThe log highlights repeated requests and counts how often the same endpoint returns an unexpected response.\nThe cache may explain the difference; if a cached response was served, the page might not reflect the latest record.\nThe finding seemed surprising, but a mirror of the original data confirmed that the same value existed before the change.\nThe investigation should stay focused on the observed failure while remaining open to another explanation if new evidence appears.",
    "textTranslate": "理解证据后可优化查询，不猜哪部分慢。\n研究含多个例子的观察，研究差异可能解释为何只一个环境失败。\n分析发现无效值，纠正后解决复现例中的故障。\n证据支持解释，但数据尚未与原来源核对。\n爬虫跟随公开链接，另一工具抓取爬行中找到的页面文字。\n搜索结果能引导调查，但排名最高不自动最可靠。\n日志突出重复请求，并统计端点返回异常响应次数。\n缓存可能解释差异，返回缓存响应时页面可能不反映最新记录。\n发现看着意外，但原数据镜像确认该值改前已存在。\n调查应聚焦已见故障，也准备在新证据出现时接受其他解释。"
  },
  {
    "title": "15A Saving Information That Needs to Survive",
    "titleTranslate": "第15课A｜讨论数据与保存",
    "text": "When an application saves information, I need to know what has been saved, where it is stored, and how long it is expected to remain.\nA visible confirmation can show that one request succeeded, but it does not explain what will happen after a restart or a migration.\nSome data belongs in the database, while temporary interface state may exist only in the current browser session or running process.\nFor a learning product, completed lessons and saved vocabulary usually need to remain available when the learner returns on another day.\nThe position of an open dialog may not require the same treatment, depending on the experience that the product intends to offer.\nI ask for these choices to be explicit so that a local convenience does not accidentally become the only copy of important information.\nBefore changing storage behavior, we review the existing records and identify which values are shared, private, temporary, or safe to regenerate.\nWe also check whether the new version can read information that was saved by the old version before the change.\nA successful update should preserve the data that the user expects to keep, rather than merely make the newest empty example work.\nUnderstanding persistence helps us describe the real behavior of the product and plan changes without making unsupported promises about what survives.",
    "textTranslate": "应用保存信息时，我需知道保存了什么、在哪里，以及应保留多久。\n可见确认能显示请求成功，却不解释重启或迁移后怎样。\n部分数据属于数据库，临时界面状态可能只在当前浏览器会话或进程中。\n学习产品中，已完成课程和生词通常需次日仍可用。\n打开对话框的位置则未必同样处理，取决于产品体验目标。\n我要求明确这些选择，避免临时本地方便方案意外成为重要信息唯一副本。\n改存储行为前，检查现有记录，区分共享、私人、临时或可重建值。\n也检查新版能否读取改动前旧版保存的信息。\n成功更新应保留用户预期保留的数据，不只是让全新空例子可用。\n理解持久化有助于描述真实行为，规划改动而不无依据承诺数据保留。"
  },
  {
    "title": "15B Planning a Backup and a Restore",
    "titleTranslate": "第15课B｜讨论数据与保存",
    "text": "A backup is useful only if we understand what it contains and how the information can be restored when it is needed.\nBefore a database migration, I ask for a current export and record which environment, date, and application version it belongs to.\nThe file should be stored in an appropriate location with access that matches the sensitivity of the information inside it.\nI also want to know whether the backup includes only database records or the uploaded files that those records refer to.\nA record with an image path is not the same thing as the image itself, so these two resources may need separate handling.\nThe restore procedure should explain the required starting state and the effect it will have on information that already exists.\nIf the procedure replaces current data, that consequence needs to be understood before anyone uses it in a live environment.\nWe can then plan a suitable check that shows whether the restored application can actually read its records and associated files.\nI keep the explanation connected to the actual project, because a generic instruction may omit a service or resource that this application requires.\nA documented backup and restore process gives the team a clearer understanding of what has been protected and what still depends on another system.",
    "textTranslate": "备份只有在知道内容及需要时如何恢复，才有用。\n数据库迁移前，我要求当前导出，并记录所属环境、日期和应用版本。\n文件应放在合适位置，访问权限需符合内部信息敏感性。\n我也想知道备份只含数据库记录，还是包含记录所指上传文件。\n图片路径记录不等于图片本身，因此可能需分别处理。\n恢复流程应解释起始条件，以及对既有信息产生的影响。\n若流程替换当前数据，在真实环境执行前必须理解后果。\n之后安排适当核对，确认恢复后的应用确实能读记录和关联文件。\n我把说明与实际项目连接，因为通用指令可能遗漏本应用依赖服务或资源。\n有文档的备份恢复流程让团队明确保护了什么，以及哪些仍依赖其他系统。"
  },
  {
    "title": "15C Working Conversation",
    "titleTranslate": "第15课C｜讨论数据与保存",
    "text": "Me: Before changing the database structure, could you export the current data and explain exactly which files and records the backup will contain?\nDeveloper: The database export will contain the records, but uploaded images are stored separately, so their files require a separate backup or reference.\nMe: Please record the source environment and date, and keep the backup in a location appropriate for the private information that it contains.\nDeveloper: I will also describe the restore procedure, including which services must be available and whether restoring will replace any existing records.\nMe: Have the learner progress and saved vocabulary been included, or does the export cover only the public course content that visitors can read?\nDeveloper: Both are included in this export; I will list the relevant tables so that the scope is explicit rather than assumed.\nMe: Good; after the migration, check whether the application can still read the old records and open the files associated with them.\nDeveloper: I will report which data has been preserved and identify any resource that remains outside the backup or depends on a separate system.",
    "textTranslate": "我：改数据库结构前，能导出当前数据并说明备份含哪些文件记录吗？\n开发者：数据库导出含记录，上传图片另存，需要单独备份或引用。\n我：请记录来源环境日期，并按私人信息要求放在合适位置。\n开发者：还会说明恢复流程，包括所需服务与是否替换既有记录。\n我：包含学习进度和生词了吗，还是只有访客可读的公开课文？\n开发者：此次两者都包含，我会列相关表，明确范围。\n我：好，迁移后检查应用是否仍能读旧记录并打开关联文件。\n开发者：会报告保留数据，并标明备份外或依赖独立系统的资源。"
  },
  {
    "title": "15D Sentence Review",
    "titleTranslate": "第15课D｜讨论数据与保存",
    "text": "When an application saves information, I need to know what has been saved, where it is stored, and how long it is expected to remain.\nSome data belongs in the database, while temporary interface state may exist only in the current browser session or running process.\nThe position of an open dialog may not require the same treatment, depending on the experience that the product intends to offer.\nWe also check whether the new version can read information that was saved by the old version before the change.\nA backup is useful only if we understand what it contains and how the information can be restored when it is needed.\nThe file should be stored in an appropriate location with access that matches the sensitivity of the information inside it.\nThe restore procedure should explain the required starting state and the effect it will have on information that already exists.\nI keep the explanation connected to the actual project, because a generic instruction may omit a service or resource that this application requires.\nBefore changing the database structure, could you export the current data and explain exactly which files and records the backup will contain?\nPlease record the source environment and date, and keep the backup in a location appropriate for the private information that it contains.\nHave the learner progress and saved vocabulary been included, or does the export cover only the public course content that visitors can read?\nGood; after the migration, check whether the application can still read the old records and open the files associated with them.",
    "textTranslate": "应用保存信息时，我需知道保存了什么、在哪里，以及应保留多久。\n部分数据属于数据库，临时界面状态可能只在当前浏览器会话或进程中。\n打开对话框的位置则未必同样处理，取决于产品体验目标。\n也检查新版能否读取改动前旧版保存的信息。\n备份只有在知道内容及需要时如何恢复，才有用。\n文件应放在合适位置，访问权限需符合内部信息敏感性。\n恢复流程应解释起始条件，以及对既有信息产生的影响。\n我把说明与实际项目连接，因为通用指令可能遗漏本应用依赖服务或资源。\n我：改数据库结构前，能导出当前数据并说明备份含哪些文件记录吗？\n我：请记录来源环境日期，并按私人信息要求放在合适位置。\n我：包含学习进度和生词了吗，还是只有访客可读的公开课文？\n我：好，迁移后检查应用是否仍能读旧记录并打开关联文件。"
  },
  {
    "title": "15E Vocabulary in Context",
    "titleTranslate": "第15课E｜讨论数据与保存",
    "text": "The backup includes several tables, and the exported sheet contains the records needed for the sample import.\nThe import tool reads a table, maps its fields, and reports any duplicated entries before saving the new data.\nThe application imports the source file, while another script creates backups and writes a snapshot of the current state.\nA database dump contains structured records, and the older dumps should be labeled with their source environment and date.\nThe private file is locked, and the credentials must not be copied into a public export or pasted into a report.\nA recoverable deletion moves an item to the trash, while permanent removal requires a different understanding of its consequences.\nThe upload includes a copy of the image, and the downloaded file should match the saved version before it replaces an existing resource.\nThe schema update was applied, but the content itself was regenerated from a separate source after the migration.\nThe ordering of the records changed, although the total count and the values stored in each item remained the same.",
    "textTranslate": "备份含多个表，导出表页含示例导入所需记录。\n导入工具读表、映射字段，并在保存前报告重复条目。\n应用导入源文件，另一脚本备份并写当前状态快照。\n数据库转储含结构记录，旧转储应标来源环境日期。\n私人文件已锁，凭据不得复制到公开导出或粘贴进报告。\n可恢复删除把项移回收站，永久删除需另行理解后果。\n上传含图片副本，下载文件替换既有资源前应与保存版一致。\n结构更新已应用，但内容在迁移后从独立来源重新生成。\n记录顺序改变，但总数和各项值不变。"
  },
  {
    "title": "16A Reporting Progress Without Mixing Up the Stages",
    "titleTranslate": "第16课A｜汇报进度与发布更新",
    "text": "A progress report should explain what has changed and what remains, rather than use one broad word to describe several different stages.\nI may have finished editing the page without committing the changes, and a successful commit does not mean that the update is already online.\nAfter the commit, the changes may still need to be pushed to the remote repository before an automatic build can begin.\nIn some projects, a push to the production branch starts deployment; in others, publishing requires a separate action or approval.\nI name the actual stage so that the person reading the report knows which result they can expect to observe now.\nFor example, I can say that the changes have been pushed but the production deployment is still running and has not completed yet.\nIf a build fails, I report where it failed and which evidence is available, instead of implying that the entire update has disappeared.\nThe remaining work may involve correcting a configuration, retrying a build, or checking the published page after the deployment succeeds.\nThis separation also makes it easier to choose the next action without repeating steps that have already finished successfully.\nA useful report ends with the current result, the remaining uncertainty, and the concrete step that will resolve it for this project.",
    "textTranslate": "进度报告应说明已改与剩余内容，不用一个宽泛词概括不同阶段。\n页面编辑完成可能尚未提交，而提交成功不等于已上线。\n提交后可能还需推送远端，自动构建才会开始。\n有些项目推生产分支即部署，其他则需独立操作或批准。\n我指出实际阶段，让报告读者知道现在能观察什么结果。\n例如可以说改动已推送，但生产部署仍在运行，尚未结束。\n构建失败时，我报告失败阶段和证据，不暗示整个更新消失。\n剩余可能是修配置、重试构建，或部署成功后检查页面。\n分清阶段也更易选择下一动作，不重复已成功步骤。\n有用报告以当前结果、剩余疑点及解决它的具体步骤结尾。"
  },
  {
    "title": "16B Following an Update into Production",
    "titleTranslate": "第16课B｜汇报进度与发布更新",
    "text": "Before an update goes live, I review what will be published and confirm that the release contains the changes we actually intend to share.\nThe source files should not accidentally include private configuration, unrelated experiments, or generated material that does not belong in the repository.\nThen I follow the deployment process that the project already uses, rather than assume that every application publishes in the same way.\nA preview helps us inspect the result before publication, but it may use a different environment from the one that serves ordinary visitors.\nOnce the production deployment is complete, I open the actual site and check the pages affected by the update.\nI look for the intended content and confirm that the main links lead to the correct destinations under the production domain.\nIf the new version does not appear, I investigate the current deployment and delivery behavior instead of editing the same content again immediately.\nThe report should distinguish a successful deployment from the particular pages and actions that have actually been checked afterward.\nAfter sharing the production link, I record any remaining follow-up work so that a completed release does not hide an unfinished requirement.\nA release is easier to understand when every stage has a clear outcome and the final result can be connected to the intended source changes.",
    "textTranslate": "更新上线前，我检查将发布什么，确认版本包含确实想分享的改动。\n源文件不应误含私人配置、无关实验，或不应入仓库的生成材料。\n接着沿用项目既定部署流程，不假设所有应用相同。\n预览有助发布前检查，但环境可能不同于普通访客访问环境。\n生产部署完成后，我打开实际站点，检查受更新影响的页面。\n我查找预期内容，确认主要链接在生产域名下指向正确位置。\n新版未出现时，我先查部署与分发，而不立即重改内容。\n报告应区分部署成功，与之后真正检查过的页面和操作。\n分享线上链接后，记录待跟进工作，避免已发版掩盖未完需求。\n每阶段有清晰结果且最终效果对应源改动时，版本发布更易理解。"
  },
  {
    "title": "16C Working Conversation",
    "titleTranslate": "第16课C｜汇报进度与发布更新",
    "text": "Me: Have the latest changes been committed and pushed, or are they still only available in the local working directory on this machine?\nDeveloper: They have been committed and pushed, and the automatic build has started, but the production deployment is not complete yet.\nMe: Please distinguish those stages in the report and let me know which step is running before you say that the update is online.\nDeveloper: The build has now passed; the deployment is running, and I will check the updated pages once it finishes successfully.\nMe: Before sharing the link, confirm that the production site shows the intended content and that the main navigation still works as expected.\nDeveloper: The updated pages are visible, and the reviewed links work; I will report the exact pages checked and any remaining limitations.\nMe: Good; include the production URL and summarize what changed, without treating an unchecked part of the application as verified by this release.\nDeveloper: I will provide that summary and record the remaining follow-up tasks so that the next session starts from the actual release state.",
    "textTranslate": "我：最新改动提交推送了吗，还是仅在本机工作目录？\n开发者：已提交推送，自动构建已开始，但生产部署未完成。\n我：报告中区分这些阶段，称已上线前先说明哪步正在运行。\n开发者：构建现已通过，正在部署，成功后会检查更新页面。\n我：发链接前，确认生产站显示预期内容，主导航仍按预期工作。\n开发者：更新页已可见，检查过的链接正常，会报告具体页面和限制。\n我：好，附线上网址并总结改动，别把未检查部分也当作已验证。\n开发者：会提供总结并记待跟进任务，让下次从真实发布状态开始。"
  },
  {
    "title": "16D Sentence Review",
    "titleTranslate": "第16课D｜汇报进度与发布更新",
    "text": "A progress report should explain what has changed and what remains, rather than use one broad word to describe several different stages.\nAfter the commit, the changes may still need to be pushed to the remote repository before an automatic build can begin.\nI name the actual stage so that the person reading the report knows which result they can expect to observe now.\nThe remaining work may involve correcting a configuration, retrying a build, or checking the published page after the deployment succeeds.\nBefore an update goes live, I review what will be published and confirm that the release contains the changes we actually intend to share.\nThen I follow the deployment process that the project already uses, rather than assume that every application publishes in the same way.\nI look for the intended content and confirm that the main links lead to the correct destinations under the production domain.\nAfter sharing the production link, I record any remaining follow-up work so that a completed release does not hide an unfinished requirement.\nHave the latest changes been committed and pushed, or are they still only available in the local working directory on this machine?\nPlease distinguish those stages in the report and let me know which step is running before you say that the update is online.\nBefore sharing the link, confirm that the production site shows the intended content and that the main navigation still works as expected.\nGood; include the production URL and summarize what changed, without treating an unchecked part of the application as verified by this release.",
    "textTranslate": "进度报告应说明已改与剩余内容，不用一个宽泛词概括不同阶段。\n提交后可能还需推送远端，自动构建才会开始。\n我指出实际阶段，让报告读者知道现在能观察什么结果。\n剩余可能是修配置、重试构建，或部署成功后检查页面。\n更新上线前，我检查将发布什么，确认版本包含确实想分享的改动。\n接着沿用项目既定部署流程，不假设所有应用相同。\n我查找预期内容，确认主要链接在生产域名下指向正确位置。\n分享线上链接后，记录待跟进工作，避免已发版掩盖未完需求。\n我：最新改动提交推送了吗，还是仅在本机工作目录？\n我：报告中区分这些阶段，称已上线前先说明哪步正在运行。\n我：发链接前，确认生产站显示预期内容，主导航仍按预期工作。\n我：好，附线上网址并总结改动，别把未检查部分也当作已验证。"
  },
  {
    "title": "16E Vocabulary in Context",
    "titleTranslate": "第16课E｜汇报进度与发布更新",
    "text": "The build system generates staging builds, and a successful build can be reviewed before the production release is published.\nWe will deploy the approved changes after the preview is ready, then check the live webpage under the production domain.\nThe release notes mention the patched behavior, the current version, and the follow-up tasks that remain open.\nThe builder reports completion after the output is created, but publication still depends on the separate deployment stage.\nA rebuild uses the updated source, while a retry may repeat the previous attempt without changing the input.\nThe deployment command was called from the terminal, and its output was captured in the report for later review.\nThe configuration was restored to the previous revision, and the update was withdrawn while the team investigated the failure.\nA working release can remain available while a new variant is reviewed in a separate environment.",
    "textTranslate": "构建系统生成预发布版本，成功后可在正式发布前检查。\n预览就绪后部署批准改动，再检查生产域名下页面。\n发布说明提到修补行为、当前版本和待跟进任务。\n构建器产物完成后报结束，但公开仍依赖部署阶段。\n重建使用新源，重试可能不改输入重复上次尝试。\n部署命令从终端调用，输出被记录供后查。\n配置恢复上版，更新撤回供团队调查。\n新变体在独立环境审阅时，正常版本仍可用。"
  },
  {
    "title": "17A Discussing a Risk Before Acting",
    "titleTranslate": "第17课A｜讨论可能性与风险",
    "text": "Before changing a system, I ask what could be affected and which assumptions need to be confirmed before the action begins.\nA change that looks small in the interface may affect private information, access permissions, or a service used by several different people.\nI want to understand the actual scope of that effect rather than treat every unfamiliar operation as either completely safe or automatically dangerous.\nThe first step is to identify the resource, the people who can access it, and the behavior that the change would introduce.\nIf an application needs a credential, we should explain what that credential allows and where it will be stored during normal use.\nWe should also distinguish a temporary connection from persistent access that remains available after the immediate task has ended.\nThese details support a specific decision instead of a vague instruction to make everything secure without describing what secure means here.\nI use words such as may, might, and could when discussing uncertain outcomes, and I explain which observation would make the judgment stronger.\nIf the consequence is difficult to reverse, it is especially important to understand the intended result and the recovery options before proceeding.\nA useful risk discussion gives people enough concrete information to choose an appropriate action and recognize the conditions that would change that choice.",
    "textTranslate": "改系统前，我问可能影响什么，以及行动前需确认哪些假设。\n界面看似小改，可能影响私人信息、访问权限或多人服务。\n我希望了解实际影响范围，不把陌生操作视作绝对安全或必然危险。\n第一步确认资源、可访问者及改动将带来的行为。\n应用需凭据时，应说明凭据权限及正常使用存储位置。\n也要区分临时连接与任务结束后仍可用的持久访问。\n这些细节支持具体决定，而不是含糊要求一切安全却不解释含义。\n讨论不确定后果时用may、might、could，并说明什么观察能加强判断。\n后果难以逆转时，推进前尤其要理解预期结果与恢复选择。\n有用风险讨论提供足够具体信息，帮助选动作并识别改变决定的条件。"
  },
  {
    "title": "17B Thinking Through an Alternative",
    "titleTranslate": "第17课B｜讨论可能性与风险",
    "text": "An alternative plan becomes useful when it changes a relevant constraint, rather than simply move the same uncertainty into a different environment.\nSuppose that a workflow depends on a remote service, and that service is sometimes unavailable during the hours when we need it.\nWe might keep a local copy of suitable public data, reduce the number of requests, or design a clear way to resume later.\nEach option has a cost, and the choice depends on whether freshness, availability, privacy, or simplicity matters most for the current task.\nIf the data were available locally, we could continue reading during an outage, but we would still need a plan for updates.\nThis hypothetical statement helps us explore a possibility without claiming that the local copy already exists or is automatically the best solution.\nWe can then ask what would happen if the connection failed halfway through a task and whether a partial result could be recovered.\nA practical alternative should explain both the ordinary workflow and the condition under which a different path becomes necessary or useful.\nWhen we compare these possibilities, we are choosing how to handle uncertainty rather than promising that no failure will ever occur.\nThe final plan should state its assumptions clearly so that the team knows when to keep following it and when to reconsider the approach.",
    "textTranslate": "备选计划应改变相关限制，而不是把同一不确定性搬到另一环境。\n假设流程依赖远端服务，而它有时在需要时段不可用。\n我们可以保留合适公开数据的本地副本、减少请求或设计稍后恢复方式。\n每个选项有成本，选择取决于新鲜度、可用性、隐私、简洁性哪个最重要。\n数据若本地可用，故障时可继续阅读，但仍需更新计划。\n这种假设帮助探索可能性，不声称本地副本已存在或必为最佳。\n再问任务中途断线会怎样，部分结果能否恢复。\n可行备选应说明正常流程及何种条件下替代路径必要或有用。\n比较这些可能性是在选择处理不确定性的方式，而非保证永不失败。\n最终计划应写清假设，让团队知道何时继续、何时重新考虑。"
  },
  {
    "title": "17C Working Conversation",
    "titleTranslate": "第17课C｜讨论可能性与风险",
    "text": "Me: If we give this service access to the account, what actions will it be allowed to perform after the current session has ended?\nDeveloper: That depends on the permission scope and credential lifetime; I will explain both before proposing where the application should store the credential.\nMe: Please distinguish the access required for reading from the access needed for publishing, because those actions have different consequences for the account.\nDeveloper: We can request only the scope needed for the current workflow and document which additional action would require a separate permission later.\nMe: What would happen if the connection failed while a scheduled action was running, and how would we avoid repeating the same action accidentally?\nDeveloper: We would need to track the actual result and resume from a known state, rather than assume that every missing response means failure.\nMe: If a simpler approach reduces that uncertainty, please compare it with this design and explain the limitations of both options clearly.\nDeveloper: I will describe the assumptions, the possible consequences, and the evidence we need before choosing the approach that fits this particular workflow.",
    "textTranslate": "我：授予服务账号访问后，本次会话结束还能做哪些动作？\n开发者：取决于权限范围和凭据时效，建议存储位置前会解释二者。\n我：请区分读取与发布权限，因为对账号后果不同。\n开发者：可以只申请当前流程所需范围，并记录以后什么动作需额外权限。\n我：计划动作运行中断线会怎样，如何避免意外重复？\n开发者：需跟踪实际结果并从已知状态恢复，不能把没响应都当失败。\n我：若更简单方式能减少不确定性，请与此设计比较并解释二者限制。\n开发者：会描述假设、可能后果及所需证据，再选符合该流程的方式。"
  },
  {
    "title": "17D Sentence Review",
    "titleTranslate": "第17课D｜讨论可能性与风险",
    "text": "Before changing a system, I ask what could be affected and which assumptions need to be confirmed before the action begins.\nI want to understand the actual scope of that effect rather than treat every unfamiliar operation as either completely safe or automatically dangerous.\nIf an application needs a credential, we should explain what that credential allows and where it will be stored during normal use.\nI use words such as may, might, and could when discussing uncertain outcomes, and I explain which observation would make the judgment stronger.\nAn alternative plan becomes useful when it changes a relevant constraint, rather than simply move the same uncertainty into a different environment.\nWe might keep a local copy of suitable public data, reduce the number of requests, or design a clear way to resume later.\nThis hypothetical statement helps us explore a possibility without claiming that the local copy already exists or is automatically the best solution.\nWhen we compare these possibilities, we are choosing how to handle uncertainty rather than promising that no failure will ever occur.\nIf we give this service access to the account, what actions will it be allowed to perform after the current session has ended?\nPlease distinguish the access required for reading from the access needed for publishing, because those actions have different consequences for the account.\nWhat would happen if the connection failed while a scheduled action was running, and how would we avoid repeating the same action accidentally?\nIf a simpler approach reduces that uncertainty, please compare it with this design and explain the limitations of both options clearly.",
    "textTranslate": "改系统前，我问可能影响什么，以及行动前需确认哪些假设。\n我希望了解实际影响范围，不把陌生操作视作绝对安全或必然危险。\n应用需凭据时，应说明凭据权限及正常使用存储位置。\n讨论不确定后果时用may、might、could，并说明什么观察能加强判断。\n备选计划应改变相关限制，而不是把同一不确定性搬到另一环境。\n我们可以保留合适公开数据的本地副本、减少请求或设计稍后恢复方式。\n这种假设帮助探索可能性，不声称本地副本已存在或必为最佳。\n比较这些可能性是在选择处理不确定性的方式，而非保证永不失败。\n我：授予服务账号访问后，本次会话结束还能做哪些动作？\n我：请区分读取与发布权限，因为对账号后果不同。\n我：计划动作运行中断线会怎样，如何避免意外重复？\n我：若更简单方式能减少不确定性，请与此设计比较并解释二者限制。"
  },
  {
    "title": "17E Vocabulary in Context",
    "titleTranslate": "第17课E｜讨论可能性与风险",
    "text": "The policy explains how to handle spam and protect trust without treating every unfamiliar message as harmful.\nCybersecurity includes understanding the access a token grants, the information it exposes, and the effect of a revoked credential.\nThe account was suspended after suspicious activity, but the actual reason should be checked before making a claim about abuse.\nAn appeal asks for a review of the decision, and repeated appeals should not invent facts that the evidence does not support.\nThe service can encrypt sensitive information, but encryption alone does not establish that the entire system is secure.\nA security policy should explain how the system prevents leaking private information and handles a confirmed violation.\nThe permission was revoked, so the application should explain why a previously available action is now prohibited or disabled.\nUnknown input should remain untrusted until its role is understood, rather than being executed because it resembles a familiar command.\nA non-null result is not proof of safety, and a valid-looking response may still contain fake or unsupported information.\nA protector can provide a shield against some threats, but no single component can guarantee the absence of harmful behavior.\nThe system must not help bots cheat or bypass a boundary that the authorized user has not agreed to change.\nA clear strategy sets quotas for repeated actions and explains why those limits exist.\nThe concern is still unassessed, so we should not describe it as either confirmed harm or a fully resolved issue.\nThe environmental impact and the information risk are different concerns, although both may matter when choosing a service.",
    "textTranslate": "政策解释如何处理垃圾信息并保护信任，不把所有陌生消息视为有害。\n网络安全包括理解令牌权限、暴露信息和凭据撤销影响。\n账号因可疑活动暂停，但指控滥用前应查真实原因。\n申诉请求复核，反复申诉也不得编造无证事实。\n服务可加密敏感信息，但加密不证明全系统安全。\n安全政策应说明如何防泄露及处理已确认违规。\n权限被撤销，应用应解释先前可用动作为何现已禁止或禁用。\n未知输入应先视为不可信，不能像熟悉命令就执行。\n非空结果不证明安全，看似有效响应仍可含伪造或无据内容。\n保护器可防部分威胁，但单组件不能保证无有害行为。\n系统不应助机器人作弊或绕过授权用户未同意更改的边界。\n清晰策略为重复操作设配额，并解释存在理由。\n担忧尚未评估，不能说已证实有害或彻底解决。\n环境影响与信息风险不同，选服务时两者都可能重要。"
  },
  {
    "title": "18A Writing a Clear Partnership Reply",
    "titleTranslate": "第18课A｜撰写邮件与沟通合作",
    "text": "When I receive a partnership enquiry, I first identify what the sender is actually asking for before drafting a reply about prices or availability.\nA request to add a product listing is different from a request to publish an article, update an existing review, or exchange a link.\nI thank the sender for reaching out and ask a focused question if the intended arrangement is still unclear after reading the message.\nThen I explain the available options and include the relevant page links so that the other person can see what each option involves.\nI keep the reply short enough to read quickly while making the next step explicit and the important conditions easy to find.\nIf I mention another website, I make it clear that it is a separate site and explain whether the proposed placement would be paid.\nI do not invent a rate when I have not decided one, and I avoid implying that a publication has already been approved.\nInstead, I can say that I will confirm the price after understanding the scope and the materials that the company wants to provide.\nA useful reply helps both sides decide whether the opportunity fits their needs without creating an accidental commitment or an unclear expectation.\nThe tone can remain friendly and professional even when I need to decline a request or ask for more information before proceeding.",
    "textTranslate": "收到合作询问时，我先确认对方实际需求，再写价格或时间回复。\n新增产品收录不同于发布文章、更新评测或交换链接。\n读完仍不清楚合作方式时，我先感谢联系，再集中询问。\n然后说明选项、附相关页面，让对方了解每项包含内容。\n回复保持简短，同时明确下一步、让重要条件容易找到。\n提到另一个网站时，我说明它独立于当前站点，并解释推广位是否付费。\n未定价时不编造报价，也不暗示发布已获批准。\n可以说了解范围和公司拟提供材料后确认价格。\n有用回复帮助双方判断是否合适，避免意外承诺或模糊预期。\n需要拒绝或进一步了解时，语气仍可友好专业。"
  },
  {
    "title": "18B Discussing Scope and Price",
    "titleTranslate": "第18课B｜撰写邮件与沟通合作",
    "text": "A price discussion becomes easier when the service being priced is described precisely and the other person understands what the payment would cover.\nFor a sponsored placement, I explain the location, the expected format, and whether the arrangement includes writing, editing, or only publishing supplied material.\nI also ask which product page should be linked and whether the sender has a short description that we can review before making a decision.\nIf the sender says they are interested, I summarize that interest accurately instead of treating it as a completed agreement to every condition.\nFor example, they may have asked for our rates without choosing a placement, accepting a price, or approving a final publication date.\nAlthough I want the conversation to move forward, I leave room for questions and make any unresolved details visible in the reply.\nOnce the main terms are understood, I can describe the next action, such as reviewing the supplied copy or confirming the publication schedule.\nIf I need to revise an earlier statement, I explain the correction directly and avoid hiding it inside an unrelated paragraph of friendly language.\nGood commercial communication depends on accurate scope and clear expectations as much as on polite words or an attractive offer.\nI want the final exchange to leave both sides with the same understanding of what has been discussed, agreed, and left open for later confirmation.",
    "textTranslate": "服务范围精确、对方理解付款涵盖内容后，价格讨论更容易。\n赞助推广中，我说明位置、形式，以及包括撰写、编辑还是只发布来稿。\n也询问链接哪个产品页，是否有可先审核的简短介绍。\n对方表示感兴趣时，我准确总结，不当成已同意全部条件。\n例如可能只问报价，还没选位置、接受价格或定发布日期。\n虽然希望推进，我仍留出提问空间，并明确未决细节。\n主要条件理解后，可说明下一动作，如审稿或确认排期。\n要修改先前说法时，应直接解释，不藏在无关客套段落中。\n良好商务沟通既依赖礼貌和有吸引力的提议，也依赖准确范围与清晰预期。\n我希望最终双方一致理解讨论了什么、同意什么、哪些待确认。"
  },
  {
    "title": "18C Working Conversation",
    "titleTranslate": "第18课C｜撰写邮件与沟通合作",
    "text": "Partner: Thanks for restoring the product listing; could you send over the link to your other website and explain your rates for a placement?\nMe: Certainly; I will include the website link and explain the available placement formats, because the price depends on the scope of the work.\nPartner: We are interested in an article, although we have not decided whether we would provide the full text or only a short product description.\nMe: Could you share the description first, so that I can review the fit and clarify whether writing or editing should be included in the quote?\nPartner: Yes; we would also like to know the expected publication date and whether the article can link directly to our product page.\nMe: I can explain those options after reviewing the material, but I have not confirmed a date or accepted the proposed placement yet.\nPartner: Understood; I will send the material and the preferred destination link, and we can discuss the final scope before approving the price.\nMe: Thank you; I will reply with a clear summary of the proposed work, the rate, and the details that still need your confirmation.",
    "textTranslate": "伙伴：谢谢恢复收录，能发另一个网站链接并说明推广报价吗？\n我：可以，附网址并说明推广形式，因为价格取决于工作范围。\n伙伴：我们对文章有兴趣，但还没定提供全文还是简短产品介绍。\n我：能先发介绍，便于判断适配性并明确报价是否含写作编辑吗？\n伙伴：可以，也想知道预计发布日期，以及文章能否直接链接产品页。\n我：审阅材料后可解释选项，但尚未确认日期或接受推广安排。\n伙伴：明白，我发材料和目标链接，批准价格前再讨论最终范围。\n我：谢谢，会回复拟议工作、报价以及仍待你确认的细节。"
  },
  {
    "title": "18D Sentence Review",
    "titleTranslate": "第18课D｜撰写邮件与沟通合作",
    "text": "When I receive a partnership enquiry, I first identify what the sender is actually asking for before drafting a reply about prices or availability.\nI thank the sender for reaching out and ask a focused question if the intended arrangement is still unclear after reading the message.\nI keep the reply short enough to read quickly while making the next step explicit and the important conditions easy to find.\nInstead, I can say that I will confirm the price after understanding the scope and the materials that the company wants to provide.\nA price discussion becomes easier when the service being priced is described precisely and the other person understands what the payment would cover.\nI also ask which product page should be linked and whether the sender has a short description that we can review before making a decision.\nAlthough I want the conversation to move forward, I leave room for questions and make any unresolved details visible in the reply.\nGood commercial communication depends on accurate scope and clear expectations as much as on polite words or an attractive offer.\nThanks for restoring the product listing; could you send over the link to your other website and explain your rates for a placement?\nWe are interested in an article, although we have not decided whether we would provide the full text or only a short product description.\nYes; we would also like to know the expected publication date and whether the article can link directly to our product page.\nUnderstood; I will send the material and the preferred destination link, and we can discuss the final scope before approving the price.",
    "textTranslate": "收到合作询问时，我先确认对方实际需求，再写价格或时间回复。\n读完仍不清楚合作方式时，我先感谢联系，再集中询问。\n回复保持简短，同时明确下一步、让重要条件容易找到。\n可以说了解范围和公司拟提供材料后确认价格。\n服务范围精确、对方理解付款涵盖内容后，价格讨论更容易。\n也询问链接哪个产品页，是否有可先审核的简短介绍。\n虽然希望推进，我仍留出提问空间，并明确未决细节。\n良好商务沟通既依赖礼貌和有吸引力的提议，也依赖准确范围与清晰预期。\n伙伴：谢谢恢复收录，能发另一个网站链接并说明推广报价吗？\n伙伴：我们对文章有兴趣，但还没定提供全文还是简短产品介绍。\n伙伴：可以，也想知道预计发布日期，以及文章能否直接链接产品页。\n伙伴：明白，我发材料和目标链接，批准价格前再讨论最终范围。"
  },
  {
    "title": "18E Vocabulary in Context",
    "titleTranslate": "第18课E｜撰写邮件与沟通合作",
    "text": "The company is seeking stock images for a campaign, but the proposal must explain which usage rights are included.\nA trade publication serves a particular industry, so its audience may differ from that of a general news website.\nA short email can begin with \"Dear Alex\" and end with \"Best regards\" when a professional tone is appropriate.\nThe subject may begin with \"Re:\" when the message is a reply within an existing email thread.\nPlease include the attached description and check that the attachment is the version we intend to share with the partner.\nThe sponsor asked about advertising rates, and the reply explained the pricing without promising an unapproved publication date.\nSeveral sponsors are interested in partnerships, but we need to identify which offers match the site's editorial policy.\nThe marketing page describes the market and the audience, while the accounting record shows what was billed and paid.\nThe lead became a client after the enquiry, but other leads remained interested without agreeing to a paid placement.\nThe content includes post-production advice, and the quote should clarify whether editing the video is part of the service.\nThe participants discussed the proposal, and each participant received a concise summary after the meeting.\nThe website lists the available publications and allows a visitor to compare the offers before sending an enquiry.\nThe proposal was rejected respectfully because the arrangement did not fit the audience, rather than because the sender was unwelcome.\nThe response offers further assistance and says that the material can be reviewed before any commitment is made.\nThe speaker raised an objection to the scope, then explained what would make the proposed arrangement acceptable.",
    "textTranslate": "公司正为活动找现成图片，但提案须说明包含哪些使用权。\n行业刊物服务特定行业，所以受众可能不同于综合新闻网站。\n专业邮件可用Dear Alex开头、Best regards结尾。\n在既有邮件串回复时，主题可能以Re:开头。\n请附描述，并确认附件是拟分享版本。\n赞助者问广告费率，回复说明价格而不承诺未批准日期。\n多个赞助者对合作有兴趣，但需判断哪些符合站点编辑政策。\n营销页描述市场受众，会计记录展示计费和已付内容。\n某潜客询问后成客户，其他潜客感兴趣但未同意付费推广。\n内容含后期建议，报价应明确是否包含视频编辑。\n参与者讨论提案，每人会后收到简洁摘要。\n网站列可用出版内容，访客可在询问前比较提议。\n提案因不适合受众被礼貌拒绝，并非不欢迎发件者。\n回复提供进一步帮助，并说明承诺前可审阅材料。\n发言者对范围提异议，再说明怎样才可接受。"
  },
  {
    "title": "19A Making the Important Point Clear",
    "titleTranslate": "第19课A｜强调、纠正与精确表达",
    "text": "Precise communication sometimes requires more than stating a fact; I may need to correct an assumption or show which condition made a result possible.\nFor example, a successful build does not by itself establish that an updated page is visible in the production environment used by ordinary visitors.\nI can express this limitation with an ordinary sentence and then choose a stronger structure when the distinction deserves particular attention.\nOnly after we checked the production page did we confirm that the update was actually available to the intended audience.\nThe opening phrase limits the condition for confirmation, and the following auxiliary moves before the subject to create partial inversion.\nThis structure sounds more formal than a normal progress report, so it is useful when the emphasis has a clear communicative purpose.\nI can also highlight the cause with a cleft sentence, saying that it was the configuration value that caused the failed request.\nThe emphasis identifies the relevant cause without requiring me to claim that every other part of the system has been examined or proved correct.\nWhen I correct an earlier interpretation, I state the intended meaning clearly and explain which part of the previous statement was too broad.\nThe purpose of emphasis is to make a meaningful distinction easier to understand, not to make an ordinary message sound unnecessarily complicated or impressive.",
    "textTranslate": "精确沟通有时不只陈述事实，还需纠正假设或说明使结果成立的条件。\n例如构建成功本身不能证明普通访客访问的生产页已更新。\n可以用普通句表达限制，特别需要强调时再选更强结构。\n只有检查生产页之后，我们才确认更新确实对目标用户可用。\n开头短语限定确认条件，后面的助动词移到主语前形成部分倒装。\n结构比普通进度报告正式，强调有明确沟通目的时才有用。\n也可以用分裂强调句突出原因：导致请求失败的是配置值。\n强调指出相关原因，不要求声称系统其他部分都已检查证明正确。\n纠正先前理解时，清楚说明本意及先前说法哪部分过宽。\n强调是让重要区别更易理解，不是让普通消息显复杂或炫技。"
  },
  {
    "title": "19B Using Emphasis Without Making Every Sentence Complicated",
    "titleTranslate": "第19课B｜强调、纠正与精确表达",
    "text": "Different sentence structures can express the same basic event while directing the reader's attention toward a different part of the explanation.\nThe ordinary sentence says that I understood the issue only after seeing the actual response returned by the server.\nThe emphasized version begins with only after that check and continues with did I understand, placing the auxiliary before the subject.\nWith a negative opening such as never, rarely, or not until, formal English can use the same kind of auxiliary movement in the main clause.\nNever have I treated a successful push as proof that every page is correct; that sentence emphasizes the speaker's consistent position.\nHowever, when only directly modifies the subject, the sentence normally keeps its ordinary order, as in only this file needs changing.\nI also pay attention to partial negation, because not every feature is necessary does not mean that no feature is necessary at all.\nIn conversation, shorter answers can omit repeated words when the context is clear, but the intended meaning still needs to remain recoverable.\nIf someone asks whether I can review the result, answering yes, I can is complete enough because the action is already understood.\nLearning these contrasts helps me choose between a neutral explanation, a stronger correction, and a concise reply that suits the situation.",
    "textTranslate": "不同句式可以表达相同事件，同时把注意力引向解释的不同部分。\n普通句说，只有看到服务器实际响应后，我才理解问题。\n强调版以only after…开头，再接did I understand，将助动词放主语前。\nnever、rarely、not until等否定成分前置时，正式英文主句可同样移动助动词。\nNever have I…强调说话者从未把推送成功当成每页正确证明的一贯立场。\n但only直接修饰主语时通常不倒装，例如只有此文件需要改。\n我也注意部分否定，因为并非每项都必要不等于任何一项都不必要。\n交谈中语境清楚可省略重复词，但仍需能恢复本意。\n有人问能否检查结果，答yes, I can即可，因为动作已知。\n学这些区别帮助我按场景选择中性解释、强纠正或简短回答。"
  },
  {
    "title": "19C Working Conversation",
    "titleTranslate": "第19课C｜强调、纠正与精确表达",
    "text": "Colleague: The changes were pushed successfully, so does that mean the new page is definitely visible and every related feature has been checked?\nMe: Not necessarily; a successful push confirms that stage, but we still need to distinguish it from deployment and actual behavior on the site.\nColleague: How could you emphasize that difference if a report had already made the result sound broader than the available evidence supports?\nMe: I could say, only after checking the production page did we confirm the update was live, while naming the pages actually reviewed.\nColleague: Would you use that inverted structure in every ordinary update, or is a simpler sentence usually better for a short working conversation?\nMe: A simpler sentence is usually better; inversion is useful when the condition needs emphasis, and the audience can follow the structure comfortably.\nColleague: If only one file needs changing, should we also move an auxiliary before the subject because the sentence begins with the word only?\nMe: No; only modifies the subject there, so the normal order remains, and we should say that only this file needs changing.",
    "textTranslate": "同事：推送成功了，是否新页肯定可见且相关功能都检查了？\n我：未必，推送成功只确认那个阶段，仍需区分部署与站点实际行为。\n同事：若报告已夸大结果，怎样强调这个区别？\n我：可以说只有检查生产页后才确认上线，并列真正检查页面。\n同事：每次普通更新都倒装吗，还是简短工作对话用简单句更好？\n我：通常简单句更好，需要强调条件且读者能跟上时才用倒装。\n同事：只有一个文件需改时，only开头也需助动词移到主语前吗？\n我：不用，only修饰主语，保留正常语序，说only this file needs changing。"
  },
  {
    "title": "19D Sentence Review",
    "titleTranslate": "第19课D｜强调、纠正与精确表达",
    "text": "Precise communication sometimes requires more than stating a fact; I may need to correct an assumption or show which condition made a result possible.\nI can express this limitation with an ordinary sentence and then choose a stronger structure when the distinction deserves particular attention.\nThe opening phrase limits the condition for confirmation, and the following auxiliary moves before the subject to create partial inversion.\nThe emphasis identifies the relevant cause without requiring me to claim that every other part of the system has been examined or proved correct.\nDifferent sentence structures can express the same basic event while directing the reader's attention toward a different part of the explanation.\nThe emphasized version begins with only after that check and continues with did I understand, placing the auxiliary before the subject.\nHowever, when only directly modifies the subject, the sentence normally keeps its ordinary order, as in only this file needs changing.\nIf someone asks whether I can review the result, answering yes, I can is complete enough because the action is already understood.\nThe changes were pushed successfully, so does that mean the new page is definitely visible and every related feature has been checked?\nHow could you emphasize that difference if a report had already made the result sound broader than the available evidence supports?\nWould you use that inverted structure in every ordinary update, or is a simpler sentence usually better for a short working conversation?\nIf only one file needs changing, should we also move an auxiliary before the subject because the sentence begins with the word only?",
    "textTranslate": "精确沟通有时不只陈述事实，还需纠正假设或说明使结果成立的条件。\n可以用普通句表达限制，特别需要强调时再选更强结构。\n开头短语限定确认条件，后面的助动词移到主语前形成部分倒装。\n强调指出相关原因，不要求声称系统其他部分都已检查证明正确。\n不同句式可以表达相同事件，同时把注意力引向解释的不同部分。\n强调版以only after…开头，再接did I understand，将助动词放主语前。\n但only直接修饰主语时通常不倒装，例如只有此文件需要改。\n有人问能否检查结果，答yes, I can即可，因为动作已知。\n同事：推送成功了，是否新页肯定可见且相关功能都检查了？\n同事：若报告已夸大结果，怎样强调这个区别？\n同事：每次普通更新都倒装吗，还是简短工作对话用简单句更好？\n同事：只有一个文件需改时，only开头也需助动词移到主语前吗？"
  },
  {
    "title": "19E Vocabulary in Context",
    "titleTranslate": "第19课E｜强调、纠正与精确表达",
    "text": "I am honestly not sure which change caused the result, and I would rather ask than give an unsupported explanation.\nThe word \"may\" softens a claim by expressing possibility instead of certainty, but it should not hide relevant evidence.\nA clear explanation separates sense from spelling, because a similar-looking phrase may have a different meaning or grammatical role.\nThe statement was wrongfully presented as a confirmed result, so the correction should state the actual evidence directly.\nThe general tone is positive, yet the speaker has a mixed feeling about the amount of unfinished work.\nA slash separates alternatives in a note, while a full sentence usually explains the relationship more naturally.\nNot only did the team restore access, but it also explained why the failure had occurred in the first place.\nThe wording is subtle: \"not all\" leaves some possibilities open, whereas \"none\" excludes every member of the group.",
    "textTranslate": "坦白说不确定哪个修改导致结果，宁愿问也不提供无据解释。\nmay以可能性缓和断言，但不应隐藏相关证据。\n清晰说明区分含义与拼写，形似短语可能意义或语法作用不同。\n该说法被不当地当作已证实结果，纠正应直接说明证据。\n总体语气积极，但说话者对大量未完工作感觉复杂。\n斜杠在笔记分隔选项，完整句则通常更自然解释关系。\n团队不仅恢复访问，还解释故障最初为何发生。\n措辞很细：not all保留一些可能，none排除全组。"
  },
  {
    "title": "20A From the First Request to a Shared Result",
    "titleTranslate": "第20课A｜完成一次项目沟通",
    "text": "A complete project conversation begins with a useful goal and ends with a result that everyone can connect to the original request.\nImagine that we want to improve a learning page so that visitors can understand the task and begin an exercise without unnecessary confusion.\nFirst, I describe the audience, the current difficulty, and the change that I would like the next version to deliver.\nThe developer asks focused questions, and together we separate the core requirement from additional ideas that may be useful in a later release.\nWe compare two options using the same content, then choose the one that gives the clearest path to the main action on mobile.\nDuring implementation, an empty menu appears, so we record the reproduction and investigate the request before changing unrelated parts of the interface.\nAfter correcting the configuration, we review the original example again and confirm that the intended options and lesson content are available.\nThe changes are then committed, pushed, and deployed through the process that this project uses, with each stage reported separately.\nOnce the production result has been checked, I share a concise summary of the change, the reviewed pages, and any remaining follow-up work.\nThe conversation succeeds because every question and explanation helps the team move from an uncertain intention toward a clear and observable outcome.",
    "textTranslate": "完整项目对话从有用目标开始，以大家能对照原请求的结果结束。\n假设想改进学习页，让访客理解任务并顺利开始练习。\n首先描述受众、当前困难，以及希望新版带来的变化。\n开发者集中提问，我们共同区分核心需求与以后可能有用的额外想法。\n用相同内容比较两方案，再选择移动端主要操作最清楚的方案。\n实现中出现空菜单，我们记录复现步骤并查请求，不先改无关界面。\n修正配置后再次检查原例，确认预期选项与课程内容可用。\n随后按该项目流程提交、推送和部署，各阶段分别报告。\n生产结果检查后，我简述改动、检查页面和待跟进事项。\n对话成功在于每个问题和解释都帮助团队从模糊意图走向清晰可见结果。"
  },
  {
    "title": "20B Learning from the Whole Conversation",
    "titleTranslate": "第20课B｜完成一次项目沟通",
    "text": "After finishing a project task, I can use the conversation itself as material for improving how I communicate in English next time.\nI review the requests that were easy to understand and the moments when a vague expression caused another round of unnecessary questions.\nThen I choose a few reusable patterns, such as checking whether something works, explaining why a change matters, or confirming what has been completed.\nI connect each pattern with a real example instead of trying to memorize a long grammar explanation without a situation in which to use it.\nThe same word may return in a different role, so I notice whether review is an action, a process, or a written evaluation in that particular sentence.\nWhen I retell the task, I use past forms for finished actions, present forms for current facts, and future expressions for the next planned step.\nI also keep the scope of my statements accurate, especially when I describe a result that was observed only in one environment or example.\nA useful final exercise is to explain the whole task aloud, answer a few questions, and write a short follow-up message without copying the original.\nIf I can adapt the expressions to another project, I have begun turning the course material into a practical part of my own working language.\nThe next improvement comes from using these patterns again, noticing what remains difficult, and giving that difficulty a clear place in future practice.",
    "textTranslate": "完成项目任务后，我可以把对话本身作为下次改善英语沟通的材料。\n我回顾容易理解的请求，以及含糊表达导致无谓追问的时刻。\n再选择几个可复用结构，比如检查是否可用、解释修改意义或确认已完成事项。\n每个结构关联真实例子，而非脱离场景背长篇语法解释。\n同词可能以不同角色再现，我注意review在句中指动作、过程还是书面评测。\n复述时，过去形式讲已结束动作，现在形式讲当前事实，将来表达讲计划。\n我也保持陈述范围准确，尤其结果只在某环境或例子被观察到时。\n有用的最终练习是不抄原文，口述整个任务、回答问题并写简短跟进。\n若能把表达用于另一个项目，课程材料就开始成为自己的工作语言。\n下次改进来自再次使用结构、发现仍难之处，并在未来练习中明确安排。"
  },
  {
    "title": "20C Working Conversation",
    "titleTranslate": "第20课C｜完成一次项目沟通",
    "text": "Me: I would like to improve the lesson page so that new visitors can understand the goal and begin the exercise without searching through unrelated options.\nDeveloper: Could you describe the current difficulty and show one example, so that we can agree on what the first improved version needs to achieve?\nMe: The main action is difficult to find on mobile; please compare two layouts using the real content and keep the existing navigation style.\nDeveloper: The second layout is clearer, but I found an empty topic menu while reviewing it; I am checking whether the request uses the correct configuration.\nMe: Please investigate that specific failure, then repeat the original steps and report what has been confirmed before moving on to publication.\nDeveloper: The configuration has been corrected and both examples work; the changes have been pushed, and the production deployment is now running.\nMe: Once the deployment is complete, check the updated pages and send me the production link with a short summary of the actual result.\nDeveloper: I will include the reviewed pages and remaining tasks, and we can use that report to plan the next improvement from a shared understanding.",
    "textTranslate": "我：想改课程页，让新访客理解目标，不必找无关选项就开始练习。\n开发者：能描述困难并举例，让我们就首个改进版目标达成一致吗？\n我：移动端主要操作难找，请用真实内容比较两布局，保留现有导航风格。\n开发者：第二版更清晰，但检查时发现主题菜单为空，正在查请求配置。\n我：请查具体故障，重复原步骤，发布前报告确认内容。\n开发者：配置已修正，两例正常；改动已推，正在生产部署。\n我：部署完成后检查更新页面，发线上链接并简述实际结果。\n开发者：会附检查页面和剩余任务，用共同理解规划下次改进。"
  },
  {
    "title": "20D Sentence Review",
    "titleTranslate": "第20课D｜完成一次项目沟通",
    "text": "A complete project conversation begins with a useful goal and ends with a result that everyone can connect to the original request.\nFirst, I describe the audience, the current difficulty, and the change that I would like the next version to deliver.\nWe compare two options using the same content, then choose the one that gives the clearest path to the main action on mobile.\nThe changes are then committed, pushed, and deployed through the process that this project uses, with each stage reported separately.\nAfter finishing a project task, I can use the conversation itself as material for improving how I communicate in English next time.\nThen I choose a few reusable patterns, such as checking whether something works, explaining why a change matters, or confirming what has been completed.\nWhen I retell the task, I use past forms for finished actions, present forms for current facts, and future expressions for the next planned step.\nIf I can adapt the expressions to another project, I have begun turning the course material into a practical part of my own working language.\nI would like to improve the lesson page so that new visitors can understand the goal and begin the exercise without searching through unrelated options.\nThe main action is difficult to find on mobile; please compare two layouts using the real content and keep the existing navigation style.\nPlease investigate that specific failure, then repeat the original steps and report what has been confirmed before moving on to publication.\nOnce the deployment is complete, check the updated pages and send me the production link with a short summary of the actual result.",
    "textTranslate": "完整项目对话从有用目标开始，以大家能对照原请求的结果结束。\n首先描述受众、当前困难，以及希望新版带来的变化。\n用相同内容比较两方案，再选择移动端主要操作最清楚的方案。\n随后按该项目流程提交、推送和部署，各阶段分别报告。\n完成项目任务后，我可以把对话本身作为下次改善英语沟通的材料。\n再选择几个可复用结构，比如检查是否可用、解释修改意义或确认已完成事项。\n复述时，过去形式讲已结束动作，现在形式讲当前事实，将来表达讲计划。\n若能把表达用于另一个项目，课程材料就开始成为自己的工作语言。\n我：想改课程页，让新访客理解目标，不必找无关选项就开始练习。\n我：移动端主要操作难找，请用真实内容比较两布局，保留现有导航风格。\n我：请查具体故障，重复原步骤，发布前报告确认内容。\n我：部署完成后检查更新页面，发线上链接并简述实际结果。"
  },
  {
    "title": "20E Vocabulary in Context",
    "titleTranslate": "第20课E｜完成一次项目沟通",
    "text": "I'm reviewing the result, and I'd like to explain what we've finished before we decide what you'll work on next.\nWe're ready to share the preview, but it's important to explain which parts have actually been checked.\nThe team won the internal comparison by presenting a clear example, not by making the greatest number of promises.\nThe development workspace contains the reviewed materials, the current plan, and the report from the previous session.\nThe creation process includes exploration, implementation, review, and the final decision about what to share.\nA useful exercise asks learners to conduct a short conversation, follow the other person's reasoning, and respond clearly.\nThe final overview connects the original goals with the observed outcome and identifies which assumptions still need attention.\nWe can zoom out to review the overall direction, then return to one detail and tune the next step.\nThe linked resources support further practice, and the suggested exercises can be adapted to a new project without copying the entire example.\nThe profile shows a registered user, the selected level, and the progress recorded during the last session.\nThe interface displays a star next to a saved item, a tag for its theme, and a pin for important notes.\nThe final outline gives each topic a clear place, while the detailed outline explains the order of the related sections.\nA summary can extract the key point from a long discussion, but it should not omit the condition that made the conclusion valid.\nThe final note keeps a short list of mistakes and explains how the next lesson will help us avoid repeating them.",
    "textTranslate": "我正检查结果，想在决定你下一步任务前说明已完成内容。\n我们准备分享预览，但应说明实际检查哪些部分。\n团队以清晰例子赢得内部比较，而非作最多承诺。\n开发工作区含已审材料、当前计划和上次报告。\n创作过程含探索、实现、审阅及最终分享决定。\n有用练习要求进行短对话、跟随对方推理并清楚回应。\n最终概览连接原目标与所见结果，并指出哪些假设仍需关注。\n可以拉远审视总体方向，再回到细节调整下一步。\n关联资源支持进一步练习，建议练习可适配新项目，不必全抄。\n资料页展示已注册用户、所选等级和上次进度。\n界面以星标表示收藏、标签表示主题、固定标记表示重要笔记。\n最终提纲给主题明确位置，详细提纲解释区块顺序。\n总结可提取讨论重点，但不应省略使结论成立的条件。\n末尾笔记保留错误短表，并解释下课如何避免重犯。"
  }
]