Tagged articles
team dynamics
39 articles · Page 1 of 1
This article categorizes four types of conflicts product managers face—resource, cognitive, boundary, and emotional—and provides a practical framework for resolution through shared interests, role-specific communication, emotional bank accounts, and six diagnostic questions to turn disputes into trade-offs without damaging long-term collaboration.
communication strategiesconflict resolutioncross-functional collaboration
0 likes · 19 min read


ITPUBJun 15, 2026 · Industry Insights
The article recounts multiple real‑world anecdotes showing that non‑technical stakeholders often believe a software project can succeed with only a single coder, but the author explains that such projects actually require a full technical team—including architects, analysts, testers, and operations—highlighting the gap between perception and reality across industries.
industry insightproject managementsoftware development
0 likes · 7 min read

Many engineers consider moving into management because they are tired of coding, but the article explains that management brings its own complexities, requires a shift in responsibility, and should only be pursued after honest self‑assessment and small experiments.
R&Dcareer transitionengineering
0 likes · 11 min read

A 2026 ThoughtWorks retreat explored how AI is reshaping software engineering, revealing a shift of rigor from code to specifications, the emergence of a new supervisory "middle loop," evolving roles, security gaps, and the need for new organizational and technical foundations.
AIDevOpsfuture of work
0 likes · 29 min read


TonyBaiFeb 1, 2026 · Backend Development
The article recounts a developer’s successful rewrite of a Python/Flask API gateway in Go that delivered ten‑fold throughput, one‑third memory usage, and seconds‑level deployment, but caused no user‑visible latency gain, created a single point of failure, and sparked a broader discussion on technical decisions, business value, and team bus factor.
API gatewayGoPython
0 likes · 8 min read

The author recounts their first month at a 20‑person IT startup, exposing chaotic onboarding, absent development processes, unreliable testing environments, ad‑hoc code releases, and misaligned product specifications, ultimately illustrating why such disorganized practices drive engineers to resign.
deploymentstartupteam dynamics
0 likes · 8 min read

This article outlines five common flaws of ineffective technical managers—ranging from clueless direction‑setting and superficial reporting to credit‑stealing and information silos—and explains what qualities define a good tech leader who respects expertise and supports the team.
R&D managementleadershipsoftware engineering
0 likes · 5 min read

A senior engineer shares his personal journey of being abruptly promoted to technical manager, struggling with team leadership, facing repeated incidents, and ultimately being reassigned to his original developer role, offering practical insights for programmers and product managers facing similar career turbulence.
Careerleadershipmanagement
0 likes · 7 min read

The article argues that measuring developer productivity should focus on real business impact rather than individual output, using the story of Tim Mackinnon—an unproductive‑on‑paper programmer whose mentorship and team‑building skills dramatically boosted overall team performance.
AgileDORADeveloper Productivity
0 likes · 5 min read

A recent workplace story shows that firing a few low‑performers can shake the entire team's morale, leading to a wave of voluntary resignations as employees lose trust, belonging, and confidence in the company's direction.
Employee Moralelayoffsmanagement
0 likes · 6 min read

A reader shares troubling experiences with a technical director, and the author outlines four concrete incidents and five key leadership flaws—lack of leading by example, unfair performance reviews, insufficient expertise, constant criticism without solutions, and poor character—advising anyone who sees these signs to consider leaving promptly.
career adviceleadershipmanagement
0 likes · 7 min read

The article warns that misguided pragmatism in software development—mistaking supporting tools for core products, imposing excessive documentation and metrics, copying architecture without context, and obsessing over raw performance—leads to wasted effort, and highlights Enterprise WeChat’s efficient team as a model for learning from these pitfalls.
Pragmatismarchitecturemanagement
0 likes · 18 min read

The article recounts a consultant’s experience with a large retail chain, exposing how “pseudo‑high‑EQ” employees flatter leaders, avoid responsibility, and betray trust, while outlining the traits of genuine high‑EQ staff such as emotional stability, accountability, and teamwork.
corporate cultureemotional intelligenceleadership
0 likes · 13 min read


DevOpsJul 11, 2023 · R&D Management
This article explains how facilitation techniques can improve group decision‑making efficiency and quality in agile teams, outlining common challenges, the facilitation process, guiding principles, facilitator responsibilities, core skills such as questioning, listening, and feedback, and practical steps for effective meetings.
facilitationgroup decisionleadership
0 likes · 15 min read


DevOpsJan 30, 2023 · R&D Management
This article analyzes common team collaboration challenges, maps them to Patrick Lencioni's five dysfunctions, and presents concrete agile practices—such as welcome/farewell rituals, life‑journey sharing, pair metrics, speedback, and rotating on‑call duties—to build trust, encourage healthy conflict, increase engagement, avoid responsibility avoidance, and focus on results, ultimately fostering a high‑performing, self‑organizing team culture.
R&D managementagile-practicesteam collaboration
0 likes · 20 min read

This article explores how seeking underlying patterns, leveraging positive events, avoiding negative setbacks, and cultivating a self‑driven growth mindset can help engineers and professionals continuously improve their skills, impact, and career trajectory.
Career Growthleadershipprofessional development
0 likes · 18 min read


DevOpsDec 6, 2022 · R&D Management
The article analyzes why team members resist agile transformation, classifies them into four roles based on perceived benefits and impact, and proposes a phased, benefit‑focused implementation strategy to increase acceptance and reduce opposition.
R&D managementTransformationchange management
0 likes · 6 min read

The article examines how a stubborn personality influences software engineers' career trajectories, arguing that while such traits can drive higher quality code and perseverance, they may also create management challenges and affect team dynamics, ultimately shaping professional advancement.
Personalitycareer developmentmanagement
0 likes · 9 min read

The article examines how design patterns serve as intermediate code conventions, discusses their performance impact, class‑explosion risk, team skill gaps, project environment, and agile constraints, and offers practical advice for balancing code quality with business realities.
code standardsperformancesoftware architecture
0 likes · 12 min read


DevOpsMay 27, 2022 · R&D Management
This article explores the concept of insight in team facilitation, defining it, examining neuroscientific research on aha moments, outlining four key traits that foster insight, and presenting four practical pathways for cultivating individual and collective insights within collaborative processes.
Design Thinkinginsightneuroscience
0 likes · 11 min read

This article examines design patterns as a form of code standard, discussing their definition, relevance in everyday business development, common pain points such as performance overhead, class explosion, team skill gaps, project constraints, and offers practical recommendations for balancing best practices with real‑world constraints.
Design Patternscode standardsperformance
0 likes · 11 min read


DevOpsDec 31, 2021 · R&D Management
In a satirical yet insightful piece, the author outlines thirteen deliberately harmful practices a leader can employ to sabotage a core employee, illustrating how misguided management decisions can erode talent, morale, and organizational health over time.
R&D managementcore employeeorganizational behavior
0 likes · 7 min read

The author, a seasoned Java backend developer, shares personal experiences and insights on evaluating efficiency, ecosystem, and team dynamics when selecting technologies—from legacy frameworks and databases to modern big‑data tools like Spark and Flink—offering practical guidance for developers and teams navigating today’s rapidly evolving tech landscape.
big datasoftware engineeringteam dynamics
0 likes · 11 min read


21CTOAug 1, 2021 · R&D Management
Drawing from recent training and classic management books, this article shares twenty actionable lessons for CTOs, covering general management principles, effective meeting practices, team structuring, performance evaluation, and technical leadership to boost productivity and align technology with business goals.
CTOOKRmanagement
0 likes · 9 min read

This article outlines common disruptive behaviors of "pig teammates" in project teams and provides concrete strategies—clarifying responsibilities, reducing conflicts, improving communication, confronting stubborn members, and motivating lax contributors—to help project managers maintain progress and team cohesion.
R&D managementcommunicationconflict resolution
0 likes · 6 min read

Interruptions and poor management practices—such as frequent meetings, vague requirements, shifting project scopes, and unrealistic time compression—drastically reduce developers' focus, increase frustration, and lead to more bugs, making it essential to recognize and address these common workplace pitfalls.
Developer Productivityinterruptionsmanagement
0 likes · 5 min read

This article outlines three essential principles for responsibly deflecting responsibility in software teams, highlights three scenarios where blame shifting is inappropriate, and provides role‑specific tactics for developers, testers, product managers, and ops to navigate workplace conflicts effectively.
R&D managementblame shiftingcommunication
0 likes · 7 min read


21CTONov 8, 2019 · Product Management
This article dissects Toutiao’s 2012‑2013 B‑round financing, its early product positioning, the tension between information efficiency and social ties, team dynamics, growth metrics, and the broader lessons for entrepreneurs and product managers navigating rapid scale.
ByteDanceToutiaogrowth metrics
0 likes · 13 min read

This article adapts William J. Donovan’s sabotage manual to reveal how easy it is to undermine an agile team’s efficiency and how practical tactics—like over‑reliance on supervisors, ignoring feedback, and over‑building features—can silently destroy true agility.
ProductivityScrummanagement
0 likes · 9 min read


DevOpsDec 28, 2018 · Operations
The article explains how mixing old and new work methods creates distinct team dynamics, identifies four participant types, outlines two major transformation challenges, and shows how a sand‑box simulation can safely guide teams toward a stable, flow‑based agile/DevOps paradigm.
AgileParadigm ShiftTransformation
0 likes · 11 min read


21CTOJul 5, 2018 · Fundamentals
This reflective essay examines how strict adherence to clean‑code principles, TDD, and SOLID can clash with personal well‑being and team dynamics, urging developers to consider empathy, context, and real‑world constraints when applying coding standards.
Clean CodeTDDsoftware craftsmanship
0 likes · 6 min read


21CTOMar 21, 2018 · R&D Management
This article outlines nine recurring problems—from mismatched teams and unrealistic requirements to relentless overtime and ignored personal lives—that drain developers' energy and sabotage software projects, offering insight into how these issues arise and why they persist.
Burnoutproject managementrequirements
0 likes · 11 min read

The article argues that making "architect" a permanent job title is misguided, advocating instead that architecture be treated as a flexible role shared by senior developers who stay involved in coding and collaborate on design decisions to avoid over‑design and team friction.
engineering leadershiprole vs positionsoftware architecture
0 likes · 6 min read


DevOpsMar 28, 2017 · Product Management
The article uses a bicycle analogy to explain why teams should first faithfully follow Scrum, then experiment with modifications only after sufficient practice, recommending a 100‑hour disciplined trial before deciding to trim the framework.
Process ImprovementScrumproduct management
0 likes · 7 min read

A corporate dragon‑boat race on the Duanwu Festival turned into a vivid lesson on project management, highlighting how unclear roles, poor communication, lack of team harmony, and member inactivity can derail a project and offering practical tips to strengthen leadership and teamwork.
Agilecommunicationleadership
0 likes · 7 min read


DevOpsJun 2, 2016 · Fundamentals
The article argues that the long‑standing construction metaphor for software development is fundamentally flawed because software lacks the physical constraints, stable materials, and predictable processes of building, making it far more adaptable, iterative, and dependent on people than any architectural project.
agilityconstruction metaphorflexibility
0 likes · 8 min read


21CTOFeb 16, 2016 · R&D Management
The article argues that a successful development team always includes a less‑skilled member, and how treating that person with respect and support reflects the team’s culture, improves morale, and ultimately enhances overall project quality.
leadershipmanagementsoftware development
0 likes · 5 min read

The article humorously categorizes programmers into eight distinct “extreme” types—ranging from the single‑technology‑obsessed to the isolated code‑only worker—illustrating each stereotype with vivid descriptions, typical remarks, and illustrative images.
industry insightsprogrammer personalitysoftware culture
0 likes · 9 min read

After two years as an intern and eight months as a full‑time engineer at Microsoft Azure, I reflect on nine often‑overlooked corporate practices—from missing documentation and low enthusiasm to limited code review and reliance on outdated tools—that shape daily life for developers in large tech firms.
Azurecode reviewcorporate culture
0 likes · 7 min read
