The Tale of Zhang Dapeng’s Tech Sharing Initiative and Its Lessons
This narrative recounts how Zhang Dapeng, after self‑studying Docker and Kubernetes, launched a series of technical sharing sessions that initially failed, prompting his manager to impose a strict review process that ultimately led to superficial compliance, a managerial award, and a reflection on three attitudes toward learning.
Zhang Dapeng spent his spare time learning Docker and Kubernetes and volunteered to give a technical sharing session, which was well received initially.
The manager, hearing about this, assigned Zhang a task to organize further sharing sessions.
Despite sending emails to invite participants, no one responded, and the first sharing session attracted little interest.
Subsequent sessions were equally poorly attended, with the third session drawing no audience at all.
Late at night, after work, Zhang drafted a detailed process for technical sharing.
He presented the flowchart to his manager, who quickly formed a review committee.
The new process was implemented, rigorously filtering most topics.
Zhang hoped the incentive would motivate people, but the first month saw no activity, nor the second month.
By the third month, the situation had not improved, and the quarterly cycle returned to its original state, with each person merely fulfilling the manager’s KPI.
At year‑end, the manager received a company award for promoting technical sharing.
Postscript: The author reflects on three types of people in learning—"prisoners" who are forced to attend, "passersby" who are indifferent, and "explorers" who are genuinely motivated, like Zhang. Many corporate tech‑sharing sessions fall into the "prisoner" category, leaving participants without a sense of achievement.
What is your company’s tech‑sharing culture like? Feel free to comment.
IT Services Circle
Delivering cutting-edge internet insights and practical learning resources. We're a passionate and principled IT media platform.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.