Tagged articles
team organization
42 articles · Page 1 of 1
Meta's AI agent Muse reached 5M US downloads in 22 days by focusing on personal use cases over coding, rigorously engineering reliability across 100+ behaviors, keeping the team under 200 people, leveraging meme-driven marketing, and building user trust through a gradual delegation ladder.
AI agentAlexandr WangMeta
0 likes · 16 min read

The article argues that AI lowers cross-stack execution costs, prompting a shift from frontend/backend separation back to full-stack—redefined as end-to-end business capability ownership with AI assistance—while professional judgment, risk decisions, and independent verification remain essential and must be allocated based on task complexity and risk.
AI-assisted developmentbusiness capability teamsfull-stack development
0 likes · 20 min read

The article argues that AI agents are transforming specialized development roles into unified delivery owners who orchestrate multiple agents to achieve business goals, requiring skills in task decomposition, parallel scheduling, multi-layer result review, and quality control rather than just coding.
AI AgentsDelivery OwnershipQuality Control
0 likes · 19 min read

The article analyzes Boris Cherny’s five talent prototypes for the AI era, explains how he flips the product‑lifecycle axis to replace traditional front‑end/back‑end/PM roles, presents supporting data from Anthropic, critiques the framework, and shows how companies and individuals can apply the model in practice.
AIAnthropicClaude Code
0 likes · 19 min read

The article analyzes when microservices add value versus unnecessary complexity, outlining common pain points, team and operational requirements, and a five‑question checklist to help architects decide if breaking a monolith into independent services is justified.
DevOpsmicroservicesscalability
0 likes · 7 min read

The article analyzes how AI‑generated code reshapes software teams, urging a new organizational contract that defines ownership, realistic productivity expectations, role re‑definition, reinforced quality gates, and end‑to‑end process changes—from demand concretization to release monitoring—to sustain high‑quality delivery.
AIBackendDevOps
0 likes · 23 min read

The article explains why the backend team built three BFF services without serverless or GraphQL, basing the decision on business logic, team expertise, and organizational structure, and shows how the architecture aligns with different e‑commerce lines.
BFFBackend For Frontendarchitecture
0 likes · 7 min read

The article examines how engineering team structures—illustrated by Adobe's functional silos and Spotify's cross‑functional squads—shape information flow, decision‑making, and delivery speed, explains Conway's Law, outlines common organizational patterns and their traps, and offers a systematic approach to diagnosing and redesigning team topologies.
AdobeConway's LawR&D management
0 likes · 13 min read

The article critically examines the hype around microservices, arguing that their true value lies in promoting modularity, clear ownership, and organizational clarity rather than solving inherent technical problems, and it traces these ideas back to classic software engineering principles and modern operational challenges.
distributed systemsmodularityscalability
0 likes · 22 min read

Collapsing the talent stack—having leaders wear multiple hats—creates a sustained unfair competitive edge, especially in the era of large‑model AI where small, tightly‑coupled teams can prototype and iterate far faster than traditional, role‑segmented organizations.
Innovation SpeedLarge Model AIR&D management
0 likes · 6 min read


DevOpsJun 16, 2024 · Operations
The article examines how the shift to Software‑Defined Vehicles introduces complex performance engineering challenges across software, hardware, and organizational domains, and proposes an engineering‑driven, continuous‑observability approach—including modeling, monitoring, iterative optimization, and specialized team structures—to sustainably improve automotive software performance.
SDVautomotive softwareobservability
0 likes · 17 min read

The article details how DeWu’s technology organization scaled from a few hundred to over a thousand engineers by adopting the custom Type‑P framework—emphasizing value‑orientation, small‑step rapid iteration, bi‑weekly sprints, unified domain‑level agile processes, metric‑driven governance, and an evolving PMO that shifted from throughput‑first to value‑first objectives.
Agile ScalingMetricsPMO
0 likes · 16 min read


21CTOMay 5, 2023 · Product Management
The article compares traditional software project teams with product‑mode teams, highlighting how long‑lived, cross‑functional product teams improve responsiveness, reduce cycle time, preserve knowledge, maintain architectural integrity, and deliver higher business value through continuous iteration and ownership.
AgileDevOpssoftware development
0 likes · 32 min read


DevOpsApr 24, 2023 · Backend Development
The article shares a chief architect’s experience designing a hybrid “big waterfall + small agile” delivery approach, microservice architecture, BFF layer, and team organization principles such as Conway’s law to address application boundary challenges in a massive state‑owned enterprise project.
BFFarchitecturemicroservices
0 likes · 11 min read


DevOpsFeb 13, 2023 · Backend Development
The article shares a chief architect's experience on combining a large‑scale waterfall approach with agile iterations, detailing microservice and BFF design, team organization aligned with Conway's law, and practical application‑boundary principles for a distributed enterprise system.
BFFdelivery modelmicroservices
0 likes · 11 min read

The article discusses various expert approaches to microservice decomposition, highlighting vertical and horizontal splits, business logic, stability, reliability, performance considerations, and team size implications, offering practical guidance for backend architects in design.
backend architectureservice decompositionsoftware design
0 likes · 10 min read

This article critically examines the microservices movement, tracing its historical roots, debunking common hype, and arguing that the true value lies in modular design, clear team ownership, and disciplined architectural practices rather than merely scaling distributed systems.
distributed systemsmicroservicesmodularity
0 likes · 23 min read

This article outlines the evolving trends in terminal devices and software architecture, argues for unified cross‑platform containers, proposes a streamlined organizational model with fewer, more versatile roles, and introduces the KUN project—a high‑performance, extensible Flutter‑based rendering engine aimed at boosting mobile development efficiency.
Fluttercross-platformmobile development
0 likes · 23 min read

This interview reveals how ByteDance’s AppInfra team builds and evolves mobile infrastructure, performance optimization, automated testing, and talent strategies to support a growing portfolio of high‑traffic apps like Douyin and Toutiao, offering insights into cross‑platform toolchains, team organization, and future technology trends.
Automation TestingInfrastructureapp performance
0 likes · 18 min read

The article explains how breaking a monolith into microservices can introduce data consistency challenges, discusses the CAP theorem and Conway's law, and provides practical guidelines—such as single‑responsibility division, team‑aligned service boundaries, and appropriate use of BASE and distributed transactions—to split services responsibly.
CAP theoremConway's LawSingle Responsibility
0 likes · 11 min read


ITPUBFeb 11, 2022 · R&D Management
The article shares a senior engineer’s practical experience on combining open‑source and self‑developed components, analysing their advantages, lifecycle stages, and concrete strategies—including problem definition, selection, source‑code control, and ten actionable tips—to help teams balance cost, innovation, and stability.
Performance TuningR&D managementproduct lifecycle
0 likes · 37 min read

The article explains how feature teams—cross‑functional, long‑lived groups that own end‑to‑end customer features—can improve user experience, technical excellence, and operational efficiency, while outlining the cultural and organizational changes required for successful adoption.
Feature Teamsagile developmentcross-functional
0 likes · 7 min read


DevOpsMar 9, 2021 · R&D Management
The article explains how adopting a "special forces" style organizational structure—small, cross‑functional squads with clear goals and boundaries—can improve R&D efficiency, adaptability to changing business needs, performance assessment, and career development within modern software companies.
DevOpsSpecial Forcesteam organization
0 likes · 7 min read

The article argues that merging microservices back into a monolith can be justified when service boundaries no longer align with team structures, emphasizing that microservices address both technical load and people‑organization problems, and that the right size of a service depends on context rather than the misleading notion of "micro".
Conway's Lawmonolithscalability
0 likes · 11 min read


58UXDOct 20, 2020 · Game Development
This article outlines the full workflow of a game art team, covering its organizational structure, each phase of game development from project initiation to post‑launch, and the detailed art production steps—including style definition, 2D and 3D creation, UI animation, special effects, asset integration, testing, and launch.
3D modelingUI designart pipeline
0 likes · 10 min read

This article compares three seasoned experts' approaches to microservice splitting—vertical vs. horizontal, business‑driven, stability‑driven, and performance‑driven—highlighting trade‑offs, team size considerations, and practical guidelines for achieving scalable, maintainable architectures.
backend architecturemicroservicesservice decomposition
0 likes · 9 min read

The article examines microservice architecture as an abstract concept and presents three practical decomposition strategies—vertical/horizontal business split, business‑driven and team‑oriented considerations, and criteria based on logic, stability, reliability and performance—while also discussing cost, release frequency, and team size implications.
backend architectureservice decompositionsoftware design
0 likes · 8 min read

The article compares large‑scale, highly regimented development teams with small, autonomous squads, explaining how the latter achieve faster delivery, higher innovation, and better resource efficiency while still handling complex projects, and discusses Conway's Law and practical implications for modern software organizations.
Conway's Lawlarge teamsproject management
0 likes · 12 min read

The article explains how designing autonomous, end‑to‑end responsible teams—by minimizing inter‑team collaboration, adopting full‑process or cross‑functional squads, and leveraging automation tools—leads to better software architecture, aligns with Conway’s law, and improves efficiency in modern DevOps environments.
AgileConway's LawDevOps
0 likes · 6 min read

The article explores various microservice decomposition approaches—vertical vs. horizontal, business‑driven, stability‑based, reliability‑focused, and performance‑oriented—highlighting trade‑offs, team size considerations, and practical guidelines for achieving scalable, maintainable service architectures.
microservicesservice decompositionsoftware architecture
0 likes · 9 min read

This article examines microservice decomposition by presenting three expert‑derived splitting approaches—vertical/horizontal, business‑driven cost‑aware, and responsibility‑based—and discusses how factors such as team size, maintenance cost, scalability, stability, reliability and performance influence the optimal service boundaries.
backend architecturemicroservicesscalability
0 likes · 8 min read

The 7FRESH mobile app team at JD transformed its organization into product‑oriented cross‑functional squads, refined task splitting and estimation, expanded automated testing, enforced strict test‑in criteria, and allocated time for technical debt reduction, resulting in markedly higher delivery quantity, frequency, and quality while improving stakeholder satisfaction.
AgileProcess Improvementmobile development
0 likes · 6 min read

This article explains how Conway's law guides functional team division in microservice architectures, describes decentralized governance, outlines various interaction and composition patterns, discusses fault‑tolerance mechanisms such as isolation, circuit breaking, rate limiting, and provides guidance on choosing appropriate service granularity.
architecturefault tolerancemicroservices
0 likes · 32 min read

The article examines how adopting microservice architecture reshapes companies into flat, small-team clusters, arguing that microservices function more as an organizational design than a pure technical pattern, and outlines principles for aligning teams with business, embracing uncertainty, and simplifying inter‑team integration.
Conway's LawR&D managementteam organization
0 likes · 13 min read

This article explains how microservice architecture reshapes functional team organization, promotes decentralized governance, defines interaction contracts such as tolerant reader and consumer‑driven contracts, and outlines service decomposition and composition patterns like proxy, aggregation, and chaining to improve agility and reduce cross‑team friction.
Service ContractsService Governancemicroservices
0 likes · 16 min read

This talk outlines how China’s Guangfa Bank built, refined, and scaled its big‑data platform since 2014, covering data positioning, system architecture optimization, delivery model improvements, team restructuring, and real‑world use cases that demonstrate the platform’s impact on risk control, marketing and operational efficiency.
bankingbig datamicroservices
0 likes · 14 min read


21CTODec 15, 2016 · R&D Management
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.
R&D managementbudgetingengineering hiring
0 likes · 4 min read


21CTOJun 5, 2016 · R&D Management
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.
R&D managementsoftware engineeringstartup scaling
0 likes · 7 min read

This article outlines the fundamental principles, overall architecture, scope, and detailed components of an IT operations service system, covering policies, processes, organizational structure, platform tools, and management workflows such as incident, problem, change, and configuration management.
Configuration ManagementIT Operationschange management
0 likes · 19 min read


21CTOJan 16, 2016 · R&D Management
The article examines Digg’s former software development workflow, detailing its team structure, Git‑Gerrit code review, Jenkins testing, Puppet deployments, evolving practices, and how Conway’s Law shaped its architecture, offering lessons for modern engineering teams.
Continuous IntegrationConway's LawDeployment Automation
0 likes · 8 min read

The article recounts Riley Newman's five‑year journey at Airbnb, describing how the data science team evolved from a small, centralized group to an embedded, cross‑functional partner that treats user behavior as data, democratizes insights, and drives product and business decisions at scale.
AirbnbUser‑Centric Datadata science
0 likes · 10 min read

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.
FacebookR&D managementdecentralization
0 likes · 17 min read
