The Development Department's fifth division organized an Agile R&D workshop showcasing Scrum practices using TFS electronic Kanban boards, covering work item, personnel, and time management, daily stand‑up demonstrations, discussion outcomes, and future agile development requirements.
This article shares practical leadership lessons from a keynote delivered to over 3,000 tech decision‑makers, focusing on developers' psychology, the shortcomings of traditional management, and actionable ways to inspire high‑quality software teams.
The article discusses how Snowball cultivates an engineer‑focused culture by defining core values such as proactiveness, professionalism, efficiency and empathy, establishing robust infrastructure tools, and implementing balanced punishment and reward systems to motivate continuous improvement and retain talent.
Transitioning from an individual contributor to a technology manager requires abandoning static mindsets, giving team members opportunities, feedback, and support, and learning from examples at companies like Google, while reflecting on personal habits to become an effective R&D leader who fosters continuous growth.
This article explains Scrum's Definition of Done (DoD) and Acceptance Criteria (AC), illustrates common pitfalls through daily stand‑up examples, presents excerpts from the Scrum Guide, compares DoD and AC, and offers practical recommendations for teams to establish clear definitions before the first sprint.
Alibaba’s newly launched DAMO Academy, unveiled at the 2017 Cloud Expo, aims to invest 100 billion yuan over three years in frontier technologies—from AI and quantum computing to cloud services—by establishing global research centers, fostering academic partnerships, and aligning scientific breakthroughs with commercial growth.
The article reflects on the deep divide between core and business development teams, emphasizing the need for thick‑skinned communication, structured feedback channels, realistic expectations, and proactive platform management to turn criticism into constructive collaboration.
This article explains how systematic coordination of design tasks—from daily routines to user behavior, demand planning, production workflows, and quality checks—can transform serial and parallel processes into efficient, habit‑forming practices that boost individual and team productivity.
This essay explores why many programmers feel confused and powerless, linking personal career anxiety to a lack of understanding of the business‑technology‑software value chain, and proposes a value‑driven architectural mindset to align learning, work, and true impact.
The article reflects on programmers' sense of bewilderment, explains how understanding the business‑technology‑software value chain and adopting a value‑driven architectural mindset can help engineers prioritize learning, align with business goals, and reduce wasted effort while enhancing system service capability.
This guide explains how to identify, attract, and evaluate top developer talent, covering candidate sourcing, crafting clear job descriptions, structuring interview panels, asking the right technical and cultural questions, avoiding common hiring pitfalls, and making informed hiring decisions.
The article explains how JD is responding to the VUCA‑driven fourth retail revolution by shifting from a tightly integrated model to an open, modular organization that combines flexible orchestration, open empowerment, and on‑demand customization to create a collaborative retail ecosystem.
The article explains how JD is reshaping its organization into a modular, plug‑in‑based structure to meet the volatile, uncertain, complex and ambiguous (VUCA) environment of the fourth retail revolution, emphasizing flexible combination, open empowerment, and on‑demand adaptability.
The article describes how a large, budget‑constrained software project with vague requirements can be successfully delivered by adopting Scrum, clarifying requirements through collaborative backlog grooming, handling defects immediately, splitting stories vertically, and coordinating multiple feature and platform teams to ensure incremental value delivery.
The article chronicles CTO Wei Xiangjun's journey from Microsoft to Kingsoft and Sina Weibo, highlighting his team‑building strategies, agile product development, architecture innovations, and practical career advice for engineers seeking growth and effective management.
This article explains Alibaba’s middle‑platform strategy, its evolution from a shared service model to a comprehensive business platform, and how it accelerates cross‑service integration, speeds up new‑business rollout, and supports the company’s broader “Five New” initiatives.
This article explores why technical experts often lack management skills, outlines the typical career stages of engineers, and provides practical guidance on developing the mindset, responsibilities, and core competencies needed to become a successful technical manager.
In this talk from the GTLC Global Technology Leadership Summit, senior CTO Xiang Jiangxu shares practical lessons on shifting from business‑driven to technology‑driven strategies, the real impact of AI, AR/VR, smart retail, and how companies like Microsoft, Google, and Suning turn innovation into competitive advantage.
This article recounts how the Taobao Live team applied agile practices over three months, tracking capacity, lead time, quality, and predictability, and demonstrates measurable improvements in delivery speed, defect reduction, and business metric alignment through focused goals, rapid hypothesis testing, and continuous delivery.
This article outlines the core stages of product development, details the architect's responsibilities across these stages, and presents growth and competency models—including the Chuck Kilmer model—illustrating how developers transition from specialists to full‑system architects while emphasizing the need for broad skills and experimentation.
The author shares a candid journey from low‑paid outsourcing coding to senior roles in design, analysis, and big‑data architecture, revealing how understanding value networks, leveraging cloud and data trends, and expanding beyond pure coding can dramatically increase a technologist’s personal and market value.
This article examines how a startup’s Kanban board was redesigned to visualize end‑to‑end value flow, improve cross‑team collaboration, expose bottlenecks, and enable product managers to track and accept work more effectively.
Through two vivid workplace scenarios, this article illustrates how delegating problems can transfer responsibility—symbolized by a ‘monkey on the shoulder’—and analyzes why passing issues to others undermines trust and effectiveness in R&D management.
The article examines the paradox of having many developers but little output, identifying causes such as misaligned roles, poor code quality, communication overhead, mistrust, unclear requirements, and outdated architectures, and offers practical suggestions to improve efficiency in software projects.
This guide explains how to define yearly engineering objectives, estimate required staff by system count, design an organizational chart, and identify hiring gaps while avoiding common pitfalls in headcount budgeting for tech teams.
This article recounts a decade-long journey from a network administrator to a chief architect, sharing personal experiences, career milestones, and three key lessons—self‑reflection, thoughtful action, and embracing change—that can guide developers aspiring to senior technical and leadership roles.
The article explains the definition of software architecture, the multifaceted responsibilities of architects, and eight principles of personal cultivation that help architects make better decisions, communicate effectively, and sustain high‑quality designs over time.
The article explains how to use the User Story Mapping technique on the TFS platform, describing both a direct one‑to‑one mapping approach and a conversion method that transforms business‑level story maps into technical TFS work items for efficient DevOps team collaboration.
An insider critique reveals how Huawei's complex hierarchy, rigid processes, outdated tools, and management culture hinder software development efficiency and quality, urging a shift toward flatter, more agile R&D practices.
The article reflects on a misleading interview about aspiring architects, critiques duplicated logic and tight coupling in enterprise systems, and argues that a true software architect should provide holistic design, reduce redundancy, and possess both technical and coordination skills.
This article explores how engineers can leverage their unique technical language, focus on mastering a single technology, navigate management or expert career tracks, and overcome societal stereotypes to build fulfilling, impactful careers in today's rapidly evolving tech landscape.
This article explains how internet companies can design and evolve technical team hierarchies—from flat, three‑level startups to large, multi‑team enterprises—by aligning roles, responsibilities, and communication flows to product scale and business goals.
The article explains how to successfully launch and drive large‑scale architecture refactoring by translating technical jargon into plain language, using data‑driven arguments, empathizing with stakeholders, and employing structured escalation and win‑win negotiation tactics to align cross‑functional teams.
This article shares practical insights on interviewing software engineers, exposing hiring biases, recommending interview structures, small‑talk techniques, broad and specific technical questions, project‑based assessments, and how to create a fair, inclusive process that reveals true talent.
The article explains how software architects combine technical architecture responsibilities with people‑focused management duties, emphasizing the importance of nurturing talent, sharing a clear product vision, encouraging collaboration, and balancing technical excellence with team motivation to achieve successful, high‑impact projects.
In this talk, a former Google global R&D director shares how demand‑driven reform, strong infrastructure foundations, and hiring the best talent shaped Google’s architecture evolution, offering practical insights for startups on balancing design, evolution, and business versus technology drivers.
The article explains Google’s rigorous talent‑acquisition strategy—hiring only candidates who outperform you, using a slow, data‑driven process, talent decision committees, structured interviews, and continuous feedback—to illustrate how startups can build a high‑quality team.
The article shares practical lessons from a year of backend R&D experiments at Weibo, describing how a bottom‑up hybrid‑cloud solution, cross‑team collaboration, and systematic team‑building transformed the Feed service’s scalability, cost efficiency, and alignment with business goals.
This article explores the true mission of a CTO, how to evaluate their performance, the optimal split between internal and external duties, and the five core responsibilities that drive technology strategy, engineering culture, sales, business development, and marketing within an organization.
The article chronicles Zhang Yiming’s journey from early failures to founding ByteDance, detailing the company’s rapid growth, product‑centric culture, funding milestones, recommendation engine technology, and the strategic decisions that turned a small engineering team into a multi‑billion‑dollar media powerhouse.
The article argues that a CEO’s strategic thinking—forecasting trends, identifying breakthrough points, and committing all resources—outweighs sheer execution, illustrating the concept with examples from Chinese tech firms and offering a three‑step framework for sustainable growth.
The article explains Alibaba's continuous delivery theory, tools, and best‑practice pipeline—including integration, testing, deployment, and release—illustrated with diagrams and a detailed description of how the platform improves software quality, collaboration, and operational resilience in large‑scale cloud environments.
An experienced Facebook engineer explains that promotions rely on sustained technical excellence, measurable impact, peer feedback, and a transparent calibration process rather than office politics, outlining the review steps, criteria, and the importance of helping others.
This article summarizes the core concepts of "The Geek and the Team", highlighting humility, respect, and trust as pillars for effective software team collaboration, and provides practical guidance on culture, leadership, handling disruptive members, organizational influence, and user relationships.
In this article, the COO of Shimo shares real‑world observations and interviews with senior engineers to reveal that high salaries and free meals satisfy only basic needs, while meaningful work, growth opportunities, and a strong company culture are the true drivers that motivate top technical talent in startups.
This article presents 22 fundamental Scrum questions covering roles, artifacts, events, benefits, limitations, and practical guidance, offering a comprehensive overview for anyone preparing to become an effective Scrum Master and deepen their understanding of agile project management.
The article reflects on the evolving role of a software architect through personal experiences at Tieto, Sony, and a bank, highlighting responsibilities, team organization, project leadership, and the broader mindset that makes anyone a de‑facto architect in both technology and life.
The article chronicles Wang Tao’s journey from a modest Hangzhou upbringing and early fascination with flight to founding DJI, detailing his education, early prototypes, strategic product decisions, funding challenges, and how the Phantom drone propelled the company to dominate the global UAV market.
This article outlines ten practical management principles—including clear structure, defined goals, appropriate delegation, visual tracking, and continuous improvement—to help leaders build high‑performing, accountable teams and avoid common pitfalls.
The article recounts a themed team‑building competition where various “sect” groups presented management insights on talent development, employee motivation, KPI‑driven evaluation, and execution, culminating in a vote that crowned the winning strategies and highlighted the value of practical, collaborative learning for R&D teams.
Google’s research on meeting efficiency reveals nine practical rules—assign a decision‑maker, prepare thoroughly, define a clear owner, keep meetings easy to cancel, limit size, attend only when needed, be punctual, stay focused, and shut down devices—to transform wasted time into productive outcomes.
The article examines why software engineers are often seen as hard to communicate with, shares Nicholas C. Zakas' experiences and analogies, and offers practical advice such as involving engineers early, minimizing interruptions, granting creative space, and providing timely appreciation to foster better collaboration.
The article examines why technically brilliant founders often fail to grow their companies, highlighting mindset shifts, market‑oriented product thinking, team‑building, capability bridging, and the creation of open industry ecosystems as keys to turning technical talent into successful CEOs.
The article shares Kevin Scott’s insights on building high‑performing engineering teams during rapid company growth, emphasizing the difference between technology and company building, the importance of asking "how" before "what", and how a cultural manifesto can guide and sustain a thriving R&D culture.
This article debates whether compact, full‑stack engineering teams are inherently unstable compared to larger, low‑tech “valley” teams, arguing that stability depends on a team's ability to nurture talent and continuously attract experts rather than relying on crude, static practices.
The article outlines Douban's R&D management philosophy, describing three core constraints—product contribution, proper methods, and technical goals—how they translate into rules, the democratic rule‑making process, cross‑team collaboration incentives, and a balanced performance and reward system.
The talk explains Facebook's early engineering culture—emphasizing rapid "Hack" iterations, a decentralized organization that avoids dependencies, open code‑base ownership, data‑driven debate, and the strategic hiring of strong engineers—to illustrate how these practices drive high‑speed product development.
From 2011 to 2014 Ctrip shifted from a 25% online, 75% offline model to a mobile‑centric approach, reorganizing its 16 business units, decoupling systems, and adopting new engineering practices to improve performance, scalability, and team autonomy.
Huawei’s shift from a pure telecom operator to a full‑stack IT company reveals the challenges of ecosystem complexity, open‑source adoption, talent restructuring, and strategic focus, offering valuable insights for R&D managers navigating large‑scale digital transformation.
The article shares a founder’s hard‑earned lessons on preventing code‑base entropy, hiring the right first engineer, and gradually improving code quality so that a growing startup can transition from a solo coder to a well‑structured engineering team.
