Writing
Technology, work, leadership, and field notes.
“Last updated” prefers the update date; posts never updated are sorted by publication date.
Don't lay metrics flat on the dashboard: prioritize them by task relevance, scope of impact, actionability, and data trustworthiness, and choose what to watch at each stage.
Short
4 min read
Part of the column “Data Metrics Guide” · Chapter 3
A publicly reusable metric dictionary: from requests and users to tasks, explaining how availability, error, latency, performance, and feedback data should be defined, combined, and interpreted.
Short
13 min read
Part of the column “Data Metrics Guide” · Chapter 2
Metrics are not numbers on a report; they are the shared language a team uses to describe the same thing. Only after defining the object, event, denominator, and time can data participate in decisions.
Short
6 min read
Part of the column “Data Metrics Guide” · Chapter 1
When you don't know how to open or what to talk about, begin by defining the problem clearly. A question-and-answer checklist that managers and reports alike can follow.
Short
2 min read
Part of the column “One-on-One Conversations” · Chapter 2
Solve one problem per conversation, with each theme lasting 30 to 60 minutes. How to use this series, an overview of its topics, and the three closing principles.
Short
2 min read
Part of the column “One-on-One Conversations” · Chapter 1
A sense of achievement comes not only from results or praise from others; it also comes from keeping commitments, identifying with your profession, helping others, and believing that what you do matters.
Short
5 min read
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.
Short
5 min read
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.
Short
6 min read
Turn technical sharing from a regular talk into a knowledge-collaboration system that connects topic selection, research, discussion, and consolidation.
Short
5 min read
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.
Short
7 min read
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.
Short
5 min read
Part of the column “Documentation & Knowledge” · Chapter 2
An old signpost written for frontend beginners: information gathering, study logs, algorithm practice, interviews, and internships are all just the beginning.
Method
2 min read
An old case from a Double Eleven shopping scenario: before rushing to a solution, first identify the problem the user is actually facing.
Case
1 min read
An index of interview and engineering fundamentals compiled after the spring 2018 job search; keeping it as a reminder that interview questions are never just interview questions.
Method
1 min read
A sci-fi short written in early university: when a bug in a two-dimensional network gains three-dimensional knowledge, what it loses is not ignorance but the ability to act.
Short
2 min read