请问HN：如何让工程师理解他们所交付的代码？
现在每个人都在使用人工智能。公司正在推动以人工智能为首的战略，鼓励在我们工作的各个环节中采用人工智能。<p>人工智能用于规划，人工智能用于请求评论（RFC），人工智能用于编写代码，人工智能用于创建拉取请求（PR）。当然，我们可以通过使用工具和测试来确保没有出现问题。但我们如何确保工程师对他们所交付的代码有深入的理解呢？<p>我们的团队提出了一些常见的建议：先写计划，先写测试用例等等。但在这个时代，我们如何验证工程师没有简单地将这些任务委托给大型语言模型（LLM）呢？<p>我也真心担心，如果这是未来，初级工程师的成长会受到影响。
查看原文
Everyone is using AI for everything now. Company is pushing for AI-first and encourages the adoption of AI in every part of our work.<p>AI for planning, AI for RFC, AI for writing code, AI for creating PRs. Sure we can have harnesses and tests to ensure nothing breaks. But how do we enforce engineers to have a deep understanding of the code that they are shipping?<p>Our team has the usual suggestions: write a plan first, write test cases first, etc. But in this age, how do you verify that the engineer did not simply delegate these tasks to an LLM first?<p>Also genuinely worried about junior engineers' growth if this is the future.