https://shizhi3620.github.io/en/tags/projects/Recent content in Projects on Jim's NotesHugoen-USMon, 07 Sep 2026 00:00:00 +0000https://shizhi3620.github.io/en/posts/notes-from-a-public-project-retrospective/Mon, 07 Sep 2026 00:00:00 +0000https://shizhi3620.github.io/en/posts/notes-from-a-public-project-retrospective/<p>A retrospective for a public project can easily collapse into outcomes: what shipped, what feedback arrived, and what might come next. The more useful part is whether people can understand and revisit the trade-offs made along the way.</p> <p>I separate a retrospective into three layers. The first is verifiable fact, such as public commits, documentation, issue records, and release notes. The second is the judgment at the time: why one problem came first and another option was postponed. Only the third is personal feeling. It can clarify context, but it cannot stand in for evidence.</p> <p>This approach helps in two ways. Collaborators get a project history rather than a collection of disconnected links. I get a record of the conditions behind a choice when facing similar constraints again, instead of relying on a vague memory of success or failure.</p>