0 views collected around this technical thread.
In this interview, NVIDIA founder Jensen Huang shares his management philosophy, emphasizing the value of tackling difficult tasks, maintaining a small yet empowered team, avoiding layoffs, fostering a zero‑market mindset, navigating the early challenges of CUDA, and leveraging AI to drive future innovation.
This article examines technical debt at four time scales—annual, monthly, weekly, and daily—explaining their characteristics, why teams often postpone remediation, and proposes a 25% rule that allocates dedicated time for each type to foster a culture of continuous improvement.
This article explores the concept of leadership within project management, outlining its definition, the L‑E‑A‑D elements (Listen, Efficiency, Action, Development), the value it brings to team culture, collaboration, innovation and risk management, and practical ways to improve leadership skills.
The article defines R&D efficiency as the effective use of human and time resources to deliver high‑quality software quickly, and outlines a systematic, multi‑dimensional approach—including culture, structure, architecture, process design, engineering systems, and measurement—to enhance it.
The article examines continuous deployment, its benefits and challenges, how team incentives and culture shape developers' responses to speed versus quality, and why rapid, incremental releases improve learning, productivity, and morale while avoiding wasteful batch processes.
Technical debt, the hidden cost of shortcuts across code, business, and team practices, grows from evolving technology, rapid business changes, and weak standards, but can be managed through disciplined analysis, standardized design, iterative planning, metric‑driven reviews, dedicated resources, and a professional, top‑down mindset.
This article summarizes key insights from the book “Continuous Delivery 2.0”, covering the double‑loop model, organizational culture principles, practical team processes, software architecture guidelines, requirement collaboration, deployment pipelines, branch strategy, configuration management, low‑risk releases, and real‑world case studies.
This article shares a practical guide on establishing a feedback culture in agile teams, explaining the background, benefits for both team and individuals, step‑by‑step speed‑feedback procedures, common challenges, and actionable tips for giving and receiving constructive feedback.
This article details Vivo's internet platform product R&D team's experience introducing OKR, outlining cultural prerequisites, positive and negative impacts, practical steps, pilot execution, common challenges, and guidance for other organizations seeking to adopt the framework.
This article outlines how technical leaders can construct a systematic R&D management framework—covering background, pain points, goals, and the five dimensions of Dao, Fa, Shu, Qi, and Shi—to foster culture, standardize processes, develop talent, leverage tools, and align with strategic trends for high‑performing engineering teams.
The article explains continuous deployment, using IMVU as a case study to illustrate how rapid release cycles affect software quality, team incentives, and culture, and argues that frequent, small deployments improve learning, reduce waste, and boost morale while challenging traditional batch‑oriented development practices.
The 2021 Accelerate State of DevOps report by Google DORA, based on over 32,000 professionals, reveals that elite teams dramatically outperform low‑performing teams across four classic delivery metrics, introduces a new reliability metric, and highlights the impact of team culture, SRE practices, cloud adoption, secure software supply chains, and high‑quality documentation on software delivery and organizational performance.
The article reflects on how most members of technical teams are passively driven, examines the unsustainable management practices that try to force active drive, draws parallels with education and economic sustainability, and proposes a more balanced, sustainable team culture that respects individual differences and long‑term growth.
The article examines the rapid rise of remote work, presents key statistics on employee preferences and productivity, highlights major challenges such as constant online expectations and loneliness, and offers practical guidance on fostering a collaborative culture, selecting appropriate tools, measuring engagement, encouraging healthy habits, and investing in remote teams.
In this talk, Ant Researcher and Experience Technology Lead Yu Bo shares his personal journey and philosophy on becoming a simple, free, and loving technologist, offering practical insights on frontend career growth, team culture, product thinking, and the importance of professionalism, responsibility, and genuine care.
This article examines how stable, non‑startup companies can develop their technical teams by addressing recruitment, personnel development, team culture, technology stack decisions, project management practices, and promotion pathways, offering practical insights for effective R&D management.
The article explains how thorough requirement analysis, disciplined daily planning, proactive risk communication, and a strong team project culture enable testers to actively contribute to project success, improve delivery quality, and align product outcomes with business value in fast‑changing mobile‑internet environments.
This article explains how Fangduoduo’s R&D team creates an empowering platform by gathering creative talent, fostering a self‑driven culture, integrating product thinking into engineering, and applying DevOps, OKR, and Scrum practices learned from leading Silicon Valley companies.
The article explores why operations professionals often feel exhausted, unrecognized, and low, identifying six systemic shortcomings—lack of a holistic ops framework, unclear positioning, closed mindset, insufficient authority, stagnant improvement, and missing cultural integration—and offers practical guidance to transform these weaknesses into strengths.
The article explores personal heroism in operations, defining it as reliance on individual effort to keep flawed systems appearing normal, examines its short‑term benefits and long‑term drawbacks for companies, teams, and the heroes themselves, and offers practical strategies to eliminate this risky mindset.