How Top Tech Experts Design Learning Plans and Master Their Craft

1. How does Yu plan and set his learning schedule?

Yu: He suggests starting from a big goal, such as a six‑month target, then breaking it down into three‑month and one‑month milestones. Learning should be combined with work; if you claim no time for practice, you need to examine where the problem lies and adopt a "learn‑by‑doing, do‑by‑learning" approach.

2. How to become an expert in a specific area? Deliberate practice?

Yu: The 10,000‑hour rule highlights deliberate practice, especially with a mentor and feedback loop. To become a high‑concurrency expert, study real systems like Tmall or JD. Real‑world challenges drive progress; understanding distributed transaction concepts and repeatedly applying them can lead to successful interviews.

3. What is your view on full‑stack learning?

Yu: Being a "one‑person multi‑skill" is useful for efficiency and combination, but depth in core competencies remains essential. Full‑stack can be pursued, and his company is experimenting with it, achieving some results while still emphasizing strong primary skills.

4. What principles guide your book selection?

Yu: He advocates a broad, inclusive knowledge base and cross‑domain learning. Recommended reading includes distributed systems theory, protocols, and architecture. He also stresses listening to developers' needs and balancing architectural rigor with human factors.

5. How to handle interruptions that prevent plan completion?

Yu: Interruptions are normal; prioritize work by addressing important‑but‑not‑urgent tasks early. Use rotating on‑call or weekly shifts to let team members focus without constant disruptions, and adjust tasks as needed.

6. How to break through a growth plateau after working for a while?

Yu: Focus on output, identify problem domains, allow rest periods, and seek fresh perspectives—new topics, teams, or even a job change can reignite growth.

7. Which three books would you recommend to a junior architect?

Yu: He suggests books on analysis patterns and visual modeling to bridge analysis and design, the "Programmer's Apprentice" series for understanding developers, and practical distributed architecture books from colleagues at Taobao.

8. Which technology area is suitable for deep‑dive consulting work?

Yu: Leverage your internet experience to consult traditional enterprises, focus on technology management, or specialize in distributed systems where you have strong expertise.

9. What code‑review format and cadence do you recommend?

Yu: Provide timely feedback after a feature is completed; there is no fixed cycle due to cost considerations. Pair reviews after each feature and occasional walkthroughs work well, especially in financial contexts.

10. How to choose a technology with long‑term viability?

Yu: Most languages endure; aim to learn a new language each year, mixing mainstream (e.g., Java) with functional languages to broaden thinking. No silver bullet—choose based on the problems you want to solve.

11. How can senior engineers stay advanced amid rapid tech change?

Yu: Combine technical depth with managerial or entrepreneurial paths. Specialize in a niche, stay curious, and treat learning as a lifelong hobby rather than a survival necessity.

12. Do you feel a mid‑career crisis? Why are you called a "director"?

Yu: He does not feel a crisis; the "director" label is just a title. Focus on the role of architect rather than titles, and avoid letting labels dictate perception.

13. How to learn and add value while handling seemingly trivial tasks?

Yu: Use spare moments for learning and reflection, regularly review and improve processes, and extract key insights from routine work to drive personal growth.