A satirical look at seven destructive management practices—excessive reporting, nonstop meetings, rigid work attitudes, manipulative leadership, forced team‑building, dubious bonus distribution, and chaotic performance reviews—that can quickly dissolve any team.
The article outlines ten actionable strategies—optimizing iteration speed, relentless automation, building proper abstractions, rigorous code reviews, fostering respectful environments, shared code ownership, investing in automated testing, allocating 20% time, cultivating continuous learning, and hiring top talent—to create a thriving engineering culture.
The author reflects on a recent departmental restructure that changed his direct manager, analyzes how a new leader reshapes career growth, decision‑making authority, and team dynamics, and shares a 3P1T framework and three practical steps for gaining trust, decision resources, and feedback.
A software engineering manager shares a candid account of handling a team member’s resignation, describing the warning signs, one‑on‑one discussion, transition planning, personal reflections on communication and support, and the broader lesson of fostering graceful exits in a fluid tech industry.
The article profiles veteran front‑end engineer Moonshadow, tracing his early JavaScript learning, leadership of ByteDance’s front‑end middle‑platform team, his views on empowering business, continuous learning, community involvement, and strategies for technical influence and talent development.
The interview with veteran frontend engineer Moonshadow (Wu Liang) shares his journey from early JavaScript adoption, leading ByteDance’s tech‑platform frontend team, his thoughts on empowering business units, maintaining curiosity, community building, and fostering technical influence and talent development.
The article shares ten practical operations principles—from avoiding duplicate work and embracing mistakes to establishing backup roles, monitoring bottlenecks, valuing platform tools, clarifying responsibilities, encouraging knowledge sharing, holding regular meetings, balancing performance metrics, and continuously optimizing processes for reliable, efficient system management.
The article analyzes common obstacles that prevent effective use of design patterns and code standards in everyday software development—such as performance overhead, class explosion, team skill gaps, project constraints, agile timelines, and staff turnover—and offers practical strategies to balance quality with productivity.
This article outlines four frequent errors that cloud teams make—misaligned skills, lacking backup plans, insufficient processes, and poor communication—and offers practical guidance on how to address each to ensure cloud projects stay on track.
The author, a PhD‑trained algorithm lead at NetEase Yanxuan, shares how his seven‑person team categorizes work, allocates resources, discovers problems, runs side experiments, and learns from failures to drive continuous improvement and business impact.
The article examines why design patterns and code standards matter, analyzes common pain points such as performance overhead, class explosion, team skill gaps, and rapid iteration, and offers practical recommendations for balancing maintainability and productivity in everyday software projects.
The article reflects on a Java backend developer's seven‑year journey, examining how efficiency, community ecosystem, and team preferences influence technology choices across front‑end frameworks, big‑data platforms, databases, and open‑source tools.
The article explores how Conway’s Law and the entropy increase principle explain the dynamic nature of organizational structures in tech companies, highlighting the impact of communication patterns on system design, resource allocation, and team efficiency.
The article explains how agile teams can thrive amid VUCA conditions by aligning clear goals, fostering intrinsic motivation, and developing diverse capabilities, offering practical management principles and four key practices—goal transparency, capability building, self‑organization, and motivation extraction—to achieve high‑performance outcomes.
This article presents a bottom‑up, self‑consistent team management system that categorizes over sixty practices into ten modules across two dimensions, offering actionable insights on time, project, technical, process, institutional, goal, performance, recruitment, talent development, and team building.
The speaker shares a decade‑long observation of why certain engineers continue to excel after graduation, outlining five key traits—curiosity, optimism toward uncertainty, refusal to settle for mediocrity, delayed gratification, and sound judgment—that distinguish high‑performing professionals from their peers.
In this talk, former Amazon and Alibaba chief architect Chen Hao shares practical ideas on why high‑efficiency teams matter, how to create them through people selection, processes, leadership, and automation, and offers concrete management tactics such as clear goals, small‑team structures, and data‑driven decision making.
This article discusses the challenges faced by frontend developers in startup companies and offers practical solutions such as coding standards, design guidelines, component libraries, documentation, project infrastructure, collaboration processes, and team culture to improve professionalism, coordination, and productivity.
This article presents a comprehensive team management framework built from the ground up, outlining two overarching dimensions and ten distinct modules—ranging from time and project management to talent recruitment and team building—to help organizations systematically improve their management practices.
This article outlines a bottom‑up approach to constructing a comprehensive, self‑consistent team management system, detailing its two dimensions, ten interrelated modules—from time and project management to talent recruitment and team building—plus visual maps and key practices for improving organizational effectiveness.
This article shares a former programmer’s journey to technical leadership, outlining essential competencies, the shift in mindset from individual contributor to manager, practical ways to boost team efficiency and cohesion, communication and emotion‑control techniques, self‑growth strategies, and energy‑management tips for sustainable success.
The author, a former programmer turned tech manager, humorously lists thirteen counter‑productive practices—ranging from fake agile enthusiasm and lack of coaching to cultural neglect and tool misuse—that can sabotage a development team when agile is applied without genuine understanding or respect.
This satirical guide lists seven counterproductive tactics—like hiring big‑company talent for a startup, misusing agile, ignoring proper role ratios, over‑managing, false startup culture, line‑count performance metrics, and unnecessary middle‑platforms—that can cripple a small software team.
This article examines common pitfalls in giving feedback, outlines five levels of feedback quality, introduces the concept of feedforward as a future‑oriented alternative, and provides practical guidelines for both delivering and receiving constructive communication within teams.
The article humorously outlines seven destructive tactics—such as poaching talent from big firms, misapplying agile, enforcing unrealistic role ratios, neglecting proper technical management, promoting false startup culture, using line‑count performance metrics, and building unnecessary middle‑platforms—to illustrate how to deliberately cripple a small‑to‑mid‑size tech team.
The article explains how Azure DevOps and Azure DevOps Server adopted agile principles, detailing team organization, cultural shifts, planning hierarchies, defect‑limit practices, and new health‑preserving methods that together improve collaboration, transparency, and delivery cadence.
In this talk, Zhang Yiming shares his personal journey from a junior engineer to a team leader, explains the "Stay hungry, Stay young" mindset, and outlines five key traits—curiosity, optimism, refusing mediocrity, humility, and good judgment—that distinguish successful young professionals and guide long‑term career development.
This article outlines how a beauty‑industry frontend team tackled diverse tech stacks, team fragmentation, and code‑quality challenges by establishing a unified code review SOP, defining clear evaluation dimensions, and later platformizing the process for automation, visualization, and sustainable improvement.
This guide explains how to identify suitable test scenarios for Selenium automation, select the right tools and team structure, eliminate flaky tests, and ensure ongoing effectiveness by aligning automation choices with business goals and technical constraints.
The article explores why peers with similar early abilities diverge over time, shares the author’s own rapid rise after graduation, and outlines five key characteristics—curiosity, optimism, refusing mediocrity, humility, and sound judgment—that consistently distinguish high‑performing young professionals.
The author reflects on personal experiences with agile adoption, emphasizing the importance of documentation, distinguishing true teams from loosely organized groups, clarifying Scrum role requirements, and discussing the unique challenges and advantages small teams face when practicing agile methodologies.
This article examines the most common obstacles agile testing teams encounter—from constantly changing requirements and neglecting cross‑browser testing to lack of automation, over‑emphasis on speed, unclear definitions of done, poor estimation, skill gaps, and technical debt—offering practical insights to address each issue.
This article explains how agile teams can run productive retrospective meetings to capture successes, identify problems, and implement actionable improvements, sharing real‑world experiences, common pitfalls, and concrete guidelines for moderating, prioritizing, and tracking outcomes across iterations.
Celebrating Supercell's tenth anniversary, this article shares ten practical lessons on fostering a culture of small, autonomous teams, hiring for quality, trusting employees, embracing failure, and focusing on long‑term player engagement to create timeless games.
This article presents a structured debate on the effectiveness of positive and negative incentives in team management, featuring expert viewpoints, real‑world case studies, practical Q&A, a concise summary of key takeaways, and recommended reading for leaders seeking to motivate high‑performing teams.
The article outlines a set of practices for creating a small, self‑managing engineering team that continuously ships code, emphasizing no middle management, outsourcing non‑core work, short weekly tasks, pair accountability, single‑owner projects, and letting underperformers go.
The article shares practical insights on the role of a technical leader, outlines a streamlined R&D workflow and team responsibilities for fast‑moving startups, and discusses technology selection, architecture components, and management practices to help early‑stage companies build effective engineering teams.
The article shares practical insights on managing technical teams in mature companies, covering recruitment strategies, effective interview evaluation, comprehensive training programs, and fostering a positive team culture through democratic decision‑making, balanced freedom, challenging work, innovation encouragement, and mutual support.
This article explains the benefits of weekly (and daily) reports for managers and employees, why many dislike them, and shares Alibaba’s practical five‑step method—strict word limits, highlighting key progress, avoiding redundancy, fostering discussion, and regular self‑review—to turn reports into a valuable team‑collaboration tool.
The article shares practical experiences and advice from Ant Financial and a startup founder on why remote work should be adopted, how to overcome communication and productivity challenges, and key management practices that foster autonomy, competence, and belonging in distributed engineering teams.
This article shares Ant Financial's experience and structured approach to managing remote software development teams, covering planning, communication, toolchains, daily routines, and the benefits and challenges of distributed work to help technical leaders optimize remote collaboration.
The article shares how to prepare for interviews, extract technical, business, and team insights from candidates, and systematically reflect on each interview to improve personal skills, hiring practices, and overall project outcomes.
The article clarifies the concept of self‑organization in Scrum, compares it with Hackman’s power‑matrix levels, describes the ideal self‑organizing team, examines its benefits and pitfalls, and analyzes how Scrum would function if self‑organization were removed.
This article shares practical insights and a structured framework for frontend team leaders on recruiting, cultivating talent, managing performance, building culture, and leveraging data to scale a mid‑size frontend group from a few members to over fifty engineers while aligning with business goals.
The author, a former technical director, recounts a three‑month period managing a 20‑person R&D team across four legacy projects, analyzes four critical management mistakes—including over‑estimating team skill, under‑estimating project difficulty, spreading resources too thin, and neglecting dedicated management—and shares concrete reflections and actionable lessons for future leaders.
YouZan’s efficiency‑improvement framework treats people as the catalyst, uses data‑driven finance, streamlines product flow, recruits responsible evangelists, builds trust‑based authority, and aligns departmental interests, creating a guide‑dog‑like, patient approach that boosts human efficiency and safeguards operations during growth and downturns.
In this interview, former Facebook Tech Lead Ge Jun shares how rapid yet sustainable development, trust‑based culture, and practical DevOps practices boost R&D efficiency, offering concrete process, engineering, personal, and management strategies along with measurable metrics for tech teams.
This article introduces seven practical retrospective meeting techniques—Thermometer, Emotion Meter, Emotion Journey, Practice Box, Problem‑Solution Board, and more—explaining their purpose, execution steps, and visual examples to help agile teams foster continuous improvement and stronger collaboration.
This article shares eight actionable guidelines for non‑technical colleagues to better understand, assess, and collaborate with programmers, covering technical judgment, time estimation honesty, clear work boundaries, openness to dissent, commit‑history reading, delivery mindset, technical debt handling, and staff turnover strategies.
The article explains how developers who produce negative value—by writing unreadable code, resisting new methods, or making harmful decisions—waste countless hours, harm team morale, and how poor hiring practices exacerbate the problem.
The article argues that the primary reason agile, DevOps, and practices like TDD struggle to take root is team laziness, emphasizing that solid methods alone are insufficient without disciplined, persistent execution and proper management rituals.
A startup founder hires a high‑paid P8 engineer expecting a full‑stack miracle, only to discover the mismatch between specialist expertise and the broad, unrealistic demands of a full‑stack role, highlighting the pitfalls of hiring for breadth over depth in fast‑growing teams.
The article describes Tubi's three‑month experiment to replace traditional waterfall and rigid sprint models with a flexible Release Train system, outlining the motivations, principles, team roles, tooling choices, successes, and areas needing improvement for a fast‑growing startup.
This article traces the career of Yu Bo, from his early doubts at the Chinese Academy of Sciences to leading Ant Financial’s Experience Technology team, highlighting his open‑source contributions, his views on frontend value, and the management principles that drive today’s enterprise‑grade UI ecosystems.
A former intern describes how a top Chinese internet firm suffers from messy code, duplicated libraries, inconsistent logging, poor configuration management, and inefficient development processes, while senior staff defend these practices as necessary adaptations to the company's scale and history.
This article examines how Alibaba Cloud’s frontend engineers evolved from a resource‑constrained role with shallow business insight to a strategic, horizontally‑aligned team that builds reusable engineering platforms, leverages serverless and BaaS, and delivers measurable business value across marketing, commerce, and sales.
This article shares practical guidance on conducting effective retrospective meetings in software development, outlining their purpose, three common misconceptions, core principles, step‑by‑step procedures, and typical pitfalls, while emphasizing continuous improvement over blame and aligning with agile and DevOps practices.
This article presents a detailed case study of a mid‑size development team’s front‑end and back‑end technology stack, server environment, project workflow, and management practices, aiming to share practical solutions and lessons learned for building and maintaining enterprise‑grade Java applications.
In this interview, PingCAP co‑founder and CTO Huang Dongxu shares how his team recruits talent, cultivates engineers through open‑source contributions, uses OKR instead of KPI for performance, and leverages community events to grow the TiDB distributed database project, while also promoting the upcoming GIAC conference.
This article shares a former Google engineer’s journey to CTO at a game studio, highlighting the challenges of leaving the programming comfort zone, mastering communication, choosing the right technologies, abandoning side projects, and navigating complex team‑management decisions.
The article compares internet‑focused teams with traditional ones, highlighting differences in work mindset, leadership focus, user‑centric goals, rapid feedback loops, and the qualities needed for managers to thrive in fast‑changing, user‑driven environments.
This article examines various recruitment channels, their advantages and disadvantages, and offers management insights on building efficient technical teams, including goal setting, process control, and strategic use of internal referrals, job boards, social media, and headhunters to optimize hiring outcomes.
This article recounts a real‑world Kanban board improvement performed by a software development team, describing the initial problems, a 15‑minute, four‑step redesign process, and the resulting clearer task visibility, better WIP control, and stronger team alignment.
The article explains how effective software architecture depends on clearly defined business and development roles, the importance of a skilled developer collaborating with the architect, and the need for communication and negotiation to bridge the gap between theoretical design and real‑world project execution.
The author reflects on a ten‑year‑old Windows application, recounts rewriting it from tens of thousands of lines to a few thousand, shares insights on programmer productivity, the Mythical Man‑Month, and why larger software teams can hinder rather than help development.
Drawing on ten years of experience at leading firms like NetEase, Baidu, and Tencent, the author shares practical insights on the critical role of development processes, disciplined coding, pragmatic architecture, effective bug handling, and regular self‑review for software teams.
This article summarizes Yu Shiwei’s “Building High‑Performance Teams”, outlining team concepts, types, three essential elements, conflict handling, organizational dynamics, and practical incentives to help managers create cohesive, autonomous, and results‑driven teams.
The article argues that project success depends more on execution than strategy and outlines three essential pillars—people, management, and culture—detailing how each contributes to building a team that can automatically and effectively deliver results.
This article explains why a robust engineering culture is essential for delivering the right work quickly, outlines practical steps to define core values, establish execution mechanisms, and nurture continuous improvement, while highlighting real‑world examples from companies like Spotify and Google.
This article explores how the evolving titles for software creators—from programmer to developer to engineer—reflect shifting expectations, responsibilities, and cultural perceptions within teams and management, offering guidance on choosing the right model for modern development groups.
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.
The article reflects on the evolution of frontend engineering, emphasizing team growth, pragmatic management, and the role of a middle‑platform in delivering stable, service‑oriented solutions, while sharing insights from Alibaba D2 about balancing innovation with practical business needs.
The article presents Zhang Qi's insights on end‑to‑end quality assurance for JD's POP platform and 7FRESH stores, covering pre‑, during‑, and post‑release testing measures, big‑data‑driven automation, tester roles, team growth strategies, and knowledge‑sharing initiatives.
The article argues that relying on a single technical leader stifles team growth, explains the drawbacks of centralized decision‑making, and proposes servant‑style, collaborative leadership practices that empower the whole team to innovate and take ownership.
The article recounts how a brilliant but isolated developer named Rick became a bottleneck, leading the team to miss deadlines, and how firing him forced a shift to collaborative development that dramatically improved productivity and reduced technical debt.
This article outlines eight key responsibilities for CTOs—from strategic thinking and rapid decision‑making to effective communication, team management, and staying ahead of technology trends—to help leaders guide their teams and deliver valuable products.
The article explains why a startup CTO must still code, manage teams, stay adaptable, understand business strategy, and act as a bridge between technology and market, emphasizing continuous learning and long‑term vision over merely writing software.
This essay explores why a strong engineer culture—rooted in freedom and efficiency—is essential for tech firms, compares operation‑driven, product‑driven, and technology‑driven companies, and offers practical steps to embed such a culture through hiring, performance, and organizational design.
The author reflects on three major challenges—staff turnover, project‑schedule control, and software‑quality improvement—and argues that mastering software‑engineering techniques, tooling, and domain knowledge is essential for effective technical team management.
The article shares a senior engineer’s experience transitioning a traditional QA group into an Engineering Productivity (EP) team, discussing organizational challenges, core values, role definitions, team structure, and practical strategies for improving software development efficiency in fast‑changing internet companies.
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.
This article shares the end‑to‑end design and development experience of a startup e‑commerce platform, covering business requirement analysis, efficient development practices, security measures, performance and architecture optimizations, as well as team‑building lessons learned.
This narrative chronicles a DevOps professional’s day, illustrating cloud project planning, efficient meeting practices, network security remediation, automation platform design, multi‑site architecture, incident response, team dynamics, and the contrast between traditional and internet‑scale operations, while inviting reader interaction and reflection.
This article shares practical Scrum experiences, covering the current development challenges, Scrum fundamentals, team composition, role responsibilities, daily rituals, product management tools, versioning rules, backlog handling, and key takeaways for adapting agile processes in modern software projects.
This article presents a series of agile process‑improvement case studies—including flexible response to change, effective communication, goal‑aligned teams, and robust engineering culture—offering practical guidance for software teams seeking to adopt and sustain agile transformations.
Ele.me’s ‘big front‑end’ team, led by Lin Jianfeng, explains why the team was created, its evolving responsibilities spanning web, Node, and native apps, the culture of autonomous ‘scatter‑raised’ management, technology adoption strategies, and the pros and cons of this organizational model.
The author recounts his nine‑year journey at Alibaba, detailing four career stages, the evolution of front‑end architecture for B‑class e‑commerce, internationalization challenges, team‑management insights, and practical advice for front‑end engineers seeking growth and resilience.
This article compiles a comprehensive list of interview questions tailored for software engineers, technical managers, and company leadership, explaining the purpose behind each question and offering follow‑up queries to help candidates evaluate a team's processes, culture, and overall health.
The author recounts a three‑year career path from a fresh Android developer in Shanghai to a CTO, sharing interview struggles, project experiences, hiring strategies, agile management insights, and personal growth reflections that can guide aspiring software engineers and tech leaders.
This article explains how to make Kanban process rules explicit by organizing them around value‑flow, periodic events, and daily collaboration, ensuring the team collectively owns these rules, and continuously improving them to support autonomous decision‑making and sustainable quality.
This article shares a senior technical director’s hard‑won lessons on balancing hands‑on development, non‑functional requirements, architecture design, training, and management to boost team productivity and product quality in software projects.
To build a scalable CRM, the article proposes a four‑step framework—defining goals, applying a full‑process digitalization methodology, designing a flexible, component‑based architecture that emphasizes configuration and light databases, and assembling an execution‑focused team—while detailing revenue‑maximizing levers, digitalization layers, and a closed‑loop feedback system.
This article shares a first‑hand account of how Vipshop’s infrastructure group introduced Scrum, detailing the motivations, role adjustments, optimal team composition, practical challenges, and take‑aways for other technical teams considering agile adoption.
The article reflects on the three career stages of software developers—junior, intermediate, and senior/architect—highlighting their evolving technical choices, team responsibilities, and the importance of experience, broad knowledge, and management skills for becoming an effective software architect.
The article explains how many founders over‑estimate a CTO’s ability to solve every technical problem, outlines six common CTO expectations in startups, and offers practical advice on aligning those expectations with the reality of technology leadership, team building, and data‑driven decision‑making.
The article explains how companies can foster an engineer‑driven culture through open workspaces, thoughtful benefits, hiring top talent, lean organizational structures, rapid product iteration, and continuous learning, ultimately boosting team performance and product outcomes.
The article explains the concept of facilitation, defines a facilitator as someone who inspires team energy and wisdom to achieve consensus and commitment, and outlines five key roles—including architect, pilot, guide, midwife, and observer—while recommending an IIFAC video for deeper insight.
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.
The article lists fifteen common workplace obstacles—such as endless meetings, email overload, misguided productivity metrics, technical debt, non‑technical managers, poor documentation, distracting environments, and a relentless chase for the newest tools—that hinder developers from writing high‑quality code efficiently.
This article outlines the key qualities a Chief Technology Officer needs—including deep technical expertise, strategic vision, strong leadership, effective management, continuous learning, team culture building, cross‑department coordination, and clear communication with CEOs—to drive successful product development and company growth.
