Writing archive
Writing organized by creation date.
A practical way to write technical documents: state the conclusion and problem clearly first, then use the right structure to carry the plan, progress, and details.
Part of the column “Documentation & Knowledge” · Chapter 1
The value of an engineering retrospective is not in retelling what happened or blaming individuals, but in turning an experience into improvements that can be verified, maintained, and reused.
Turn technical sharing from a regular talk into a knowledge-collaboration system that connects topic selection, research, discussion, and consolidation.
A mentor's value lies not in planning everything for the new hire, but in jointly building goals, feedback, and a rhythm of gradually stepping back; a workable 90-day plan makes this traceable.
Part of the column “Building Teams” · Chapter 6
An entry page is not a pile of links, but the shared memory a constantly changing project leaves for its team: it helps readers enter by task, judge whether information is still valid, and find the people responsible for maintaining it.
Part of the column “Documentation & Knowledge” · Chapter 2