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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
