2 views collected around this technical thread.
This article analyzes Google’s large‑scale code review practices, showing how lightweight processes, tool‑driven automation, and a culture of knowledge transfer turned code review from a time‑consuming task into a productivity engine that scales across tens of thousands of engineers.
The DeWu Technology Department’s algorithm team outlines its project‑management evolution, confronting shifting business demands and technical complexity, and proposes six strategies—hybrid agile‑waterfall methods, rigorous requirements prioritization, standardized experiment processes, unified documentation, strengthened cross‑team collaboration, and data‑driven outcome quantification—to boost efficiency and business value.
The article explains how AI agents, integrated into transaction systems, automate log analysis, generate test data via natural-language tools, and preserve expert knowledge, achieving at least a 50 % boost in issue-tracing efficiency, reducing debugging time, and empowering developers to focus on feature development and stability.
The 2023 Pujiang Innovation Forum highlighted the rapid rise of generative AI, its associated security and privacy risks, and presented Ant Group's multi‑stage, multi‑layered approach—including data, training, and inference controls and three core defense technologies—to achieve safe, reliable, and open knowledge sharing in the era of large language models.
The article maps four primitive learning scenarios—fire, water source, cave, and life—to modern organizational training, outlines a quantifiable skill‑matrix assessment process, and illustrates its impact through two real‑world cases, showing how targeted environments boost individual and team capability growth.
This article shares the author’s experience and practical guidance on writing technical articles, covering why it matters, how to overcome initial hesitation, methods for continuous improvement, and detailed tips on content completeness, logical flow, structure, visual design, and daily habits.
Building a strong technical culture in engineering teams requires top‑down commitment to respect engineers, fostering knowledge sharing, automating tools, hiring curious innovators, and rewarding experimentation, so that contributions are valued, innovation thrives, talent is retained, and teams become more productive and satisfied.
In this interview, Qunar's Technology Committee chair Wang Zhimeng shares how the company built its technology brand over the past two years, detailing the challenges, strategies, achievements, and future plans for fostering a strong technical community and enhancing talent attraction.
This article presents a practical re‑design of the DAMA‑DMBOK data management framework, integrating Huawei's data approach and over a decade of governance experience, and details twelve knowledge domains with resources, examples, and guidance for building a comprehensive data governance system.
Senior database engineer Yang Jianrong recounts his 2,100‑day daily technical‑sharing journey, emphasizing programmer soft‑skills—steady learning, clear communication, and open mindset—while offering four practical tips on planning, avoiding technical silos, using fragmented time, and engaging communities, and outlining future focus on AIOps, modern languages, and advanced database technologies.
This article explains the importance of code review for improving software quality, outlines the benefits of using Gerrit as a CR tool, describes the detailed workflow and promotion strategies, and discusses future extensions such as CI integration, issue tracking, and metric‑driven improvements.
The article explains why code review is essential for software teams, describing how systematic reviews catch bugs, spread knowledge, reduce bus factor risk, align trends, improve communication, create useful history, enable precise discussions, strengthen team cohesion, and enhance code readability.
The article explores Randy Shoup’s insights on Google’s DevOps model, focusing on Dr. Spear’s four capabilities—especially the ways high‑efficiency companies rapidly detect issues, swarm to resolve them, disseminate new knowledge company‑wide, and adopt a development‑led leadership approach.