

<feed xmlns="http://www.w3.org/2005/Atom">
  <id>/</id>
  <title>Chang Wan</title>
  <subtitle>The Personal Website of Chang Wan.</subtitle>
  <updated>2026-04-08T18:47:15+01:00</updated>
  <author>
    <name>Chang Wan</name>
    <uri>/</uri>
  </author>
  <link rel="self" type="application/atom+xml" href="/feed.xml"/>
  <link rel="alternate" type="text/html" hreflang="en"
    href="/"/>
  <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator>
  <rights> © 2026 Chang Wan </rights>
  <icon>/assets/img/favicons/favicon.ico</icon>
  <logo>/assets/img/favicons/favicon-96x96.png</logo>


  
  <entry>
    <title>Harness Engineering：AI代理时代的新工程范式</title>
    <link href="/posts/Harness-Engineering/" rel="alternate" type="text/html" title="Harness Engineering：AI代理时代的新工程范式" />
    <published>2026-03-30T04:51:00+01:00</published>
  
    <updated>2026-04-05T18:47:36+01:00</updated>
  
    <id>/posts/Harness-Engineering/</id>
    <content src="/posts/Harness-Engineering/" />
    <author>
      <name>Chang Wan</name>
    </author>

  
    
    <category term="AI Agents" />
    
    <category term="Software Engineering" />
    
  

  
    <summary>
      





      OpenAI团队最近发布了一篇关于”Harness Engineering”的文章，描述了他们如何通过”完全不手动编写代码”的方式，使用AI代理构建和维护一个超过100万行代码的大型应用。这种新的工程范式正在重新定义我们如何构建和维护软件系统。本文深入探讨Harness Engineering的核心概念、实践方法及其对未来软件开发的影响。


  AI 生成内容声明： 
本文的内容由生成式 AI 研究、编写和审查。由于大型语言模型可能存在”幻觉”，信息可能包含一些不准确之处。建议读者自行判断技术信息的准确性和相关性。




 目录 





  什么是Harness Engineering？
  Harness的三大核心组件
    
      1. 上下文工程（Context Engineering）
      2. 架构约束（Architectural Constrain...
    </summary>
  

  </entry>

  
  <entry>
    <title>Harness Engineering：OpenAI的智能体优先开发实验启示录</title>
    <link href="/posts/Harness-Engineering-OpenAI%E7%9A%84%E6%99%BA%E8%83%BD%E4%BD%93%E4%BC%98%E5%85%88%E5%BC%80%E5%8F%91%E5%AE%9E%E9%AA%8C/" rel="alternate" type="text/html" title="Harness Engineering：OpenAI的智能体优先开发实验启示录" />
    <published>2026-03-22T17:07:00+00:00</published>
  
    <updated>2026-04-04T11:26:08+01:00</updated>
  
    <id>/posts/Harness-Engineering-OpenAI%E7%9A%84%E6%99%BA%E8%83%BD%E4%BD%93%E4%BC%98%E5%85%88%E5%BC%80%E5%8F%91%E5%AE%9E%E9%AA%8C/</id>
    <content src="/posts/Harness-Engineering-OpenAI%E7%9A%84%E6%99%BA%E8%83%BD%E4%BD%93%E4%BC%98%E5%85%88%E5%BC%80%E5%8F%91%E5%AE%9E%E9%AA%8C/" />
    <author>
      <name>Chang Wan</name>
    </author>

  
    
    <category term="AI Agents" />
    
    <category term="Software Engineering" />
    
  

  
    <summary>
      





      OpenAI最近发表了一篇开创性的文章，详细介绍了他们为期五个月的”Harness Engineering”实验——构建一个完全没有人工编写代码的完整软件产品。本文将对这项实验进行全面分析，从空仓库到百万行代码库的旅程，揭示智能体优先开发、上下文管理以及AI驱动世界中软件工程未来的关键洞察。


  AI 生成内容声明： 
本文的内容由生成式 AI 研究、编写和审查。由于大型语言模型可能存在”幻觉”，信息可能包含一些不准确之处。建议读者自行判断技术信息的准确性和相关性。



 目录 





  引言：软件工程的范式转移
  实验概况：从零到百万行的旅程
  智能体优先开发的核心理念
  上下文管理：最大的挑战
  为智能体设计的架构：约束赋能速度
  质量保证的演化
  开发工作流程的革命
  技术债务与AI”残渣”管理
  关键教训与最佳实践
  智能体优先开发的未来
  结...
    </summary>
  

  </entry>

  
  <entry>
    <title>Harness Engineering: Lessons from OpenAI's Agent-First Development Experiment</title>
    <link href="/posts/Harness-Engineering-Lessons-from-OpenAIs-Agent-First-Development/" rel="alternate" type="text/html" title="Harness Engineering: Lessons from OpenAI&amp;apos;s Agent-First Development Experiment" />
    <published>2026-03-22T16:57:00+00:00</published>
  
    <updated>2026-04-04T11:26:08+01:00</updated>
  
    <id>/posts/Harness-Engineering-Lessons-from-OpenAIs-Agent-First-Development/</id>
    <content src="/posts/Harness-Engineering-Lessons-from-OpenAIs-Agent-First-Development/" />
    <author>
      <name>Chang Wan</name>
    </author>

  
    
    <category term="AI Agents" />
    
    <category term="Software Engineering" />
    
  

  
    <summary>
      





      OpenAI recently published a groundbreaking article detailing their five-month experiment in “harness engineering” - building a complete software product with zero human-written code. This comprehensive analysis explores their journey from an empty repository to a million-line codebase, revealing key insights about agent-first development, context management, and the future of software engineeri...
    </summary>
  

  </entry>

  
  <entry>
    <title>Best Practice of Microservices Architecture</title>
    <link href="/posts/Best-Microservices/" rel="alternate" type="text/html" title="Best Practice of Microservices Architecture" />
    <published>2024-10-11T13:07:00+01:00</published>
  
    <updated>2024-10-11T14:07:14+01:00</updated>
  
    <id>/posts/Best-Microservices/</id>
    <content src="/posts/Best-Microservices/" />
    <author>
      <name>Chang Wan</name>
    </author>

  
    
    <category term="(CS) Learning Note" />
    
    <category term="Architecture" />
    
  

  
    <summary>
      





      Currently, microservice architecture is very popular, which also led to many teams to adopt microservices in practice without thinking ( not considering the size of the team, nor the development of the business, nor the support of the underlying technology ). However, there are also many problems after blindly using microservices.



 Contents 





  Pitfalls of Implementing Microservices
    ...
    </summary>
  

  </entry>

  
  <entry>
    <title>What is the Relationship Between Microservices and SOA?</title>
    <link href="/posts/SOA-Microservices/" rel="alternate" type="text/html" title="What is the Relationship Between Microservices and SOA?" />
    <published>2024-10-07T12:12:00+01:00</published>
  
    <updated>2024-10-07T12:12:00+01:00</updated>
  
    <id>/posts/SOA-Microservices/</id>
    <content src="/posts/SOA-Microservices/" />
    <author>
      <name>Chang Wan</name>
    </author>

  
    
    <category term="(CS) Learning Note" />
    
    <category term="Architecture" />
    
  

  
    <summary>
      





      Microservices include the concept of “service”, and SOA (Service Oriented Architecture) also has the concept of “service”, we will naturally ask: what is the relationship between microservices and SOA? Why do we still need microservices when we have SOA?

If you are going to use microservices architecture, it is important to understand the above questions. If you don’t understand these question...
    </summary>
  

  </entry>

</feed>


