Tagged articles
team scaling
24 articles · Page 1 of 1
The article argues that while individual FDE expertise is hard to replicate, organizations can scale delivery by codifying domain knowledge into reusable platforms and models, enabling tiered collaboration and AI-augmented efficiency rather than relying on heroic individuals.
AI-assisted deliveryFDEForward Deployed Engineer
0 likes · 13 min read

The article shares three hard‑learned principles for dividing microservices—isolating core applications, avoiding delivery slowdown as teams grow, and defining service boundaries with concrete examples—illustrating why each rule matters and how it prevents outages.
core application isolationmicroservicesservice decomposition
0 likes · 3 min read

This article analyzes how organizational structure must evolve across three company sizes during AI transformation: 3-person teams focus on rapid validation with composite roles, 10-person companies need stable replication through shared governance and templates, and 30-person companies require autonomous delivery pods with centralized governance to enable parallel execution while maintaining standards.
AI agentsAI transformationR&D management
0 likes · 20 min read

The article explains why monolithic architecture is the optimal choice for early‑stage, low‑traffic projects due to its speed, simplicity, and low overhead, but later suffers from release coupling, resource contention, and team conflicts, outlining clear criteria for when to migrate to microservices.
deploymentmicroservicesmonolith
0 likes · 3 min read

This article shares practical insights from frontline managers on scaling teams, evolving decision processes, fostering cross‑functional collaboration, choosing market models, and optimizing pricing, helping founders and leaders navigate the typical challenges of growing a startup.
cross-functional collaborationdecision-makingmarket strategy
0 likes · 9 min read

This article outlines a comprehensive R&D management framework—covering background, pain points, goals, and a five‑dimensional approach (Dao, Fa, Shu, Qi, Shi)—to help technical leaders design culture, principles, processes, standards, tools, and incentives that enable high‑performing teams of dozens to thousands of engineers.
CultureProcess OptimizationR&D management
0 likes · 38 min read


21CTOJul 7, 2022 · R&D Management
This article outlines how technical leaders can construct a comprehensive R&D management system for teams of hundreds to thousands by addressing cultural foundations, process standardization, tool integration, talent lifecycle, and strategic momentum, ultimately enabling focused, high‑performing development organizations.
R&D managementleadershipperformance evaluation
0 likes · 39 min read


21CTOFeb 6, 2022 · R&D Management
This article outlines a systematic approach for technical leaders to construct a comprehensive R&D management framework—covering culture, processes, tools, standards, and strategic alignment—to scale teams beyond 100 members while maintaining focus, efficiency, and high performance.
Cultureleadershipprocess standardization
0 likes · 35 min read

This article outlines a comprehensive R&D management framework—covering culture, processes, people, tools, and strategy—to help technical leaders scale teams beyond a hundred members, align goals, improve efficiency, and sustain high‑performance delivery while fostering growth and motivation.
R&D managementengineering leadershipprocess standardization
0 likes · 37 min read

This article explains why, when, and how to split a monolithic application into microservices, covering the goals of splitting, timing decisions, guiding principles, granularity considerations, functional and non‑functional strategies, merging practices, and associated risks.
DDDarchitecturecloud native
0 likes · 18 min read


21CTOSep 18, 2021 · Cloud Native
This article explains why and when to break a monolithic application into micro‑services, outlines practical splitting strategies, essential design principles, and the risks involved, while providing concrete guidelines for teams, business scale, and technical readiness.
Best PracticesDDDarchitecture
0 likes · 20 min read

This article examines the transition from monolithic to microservice architectures, outlining the advantages and costs of microservices, the conditions under which they should be adopted, practical implementation options, risk assessments, service‑splitting strategies, and a concise comparison with SOA.
architecturerisk assessmentservice decomposition
0 likes · 17 min read


DevOpsMar 15, 2021 · R&D Management
This article describes how Worktile introduced Scrum, built an 8‑person self‑organizing Scrum team for the Lesschat product, iterated through two‑week Sprints, identified and solved scaling challenges, and eventually evolved into a multi‑team, hundred‑person agile R&D organization with continuous delivery practices.
Continuous DeliveryDevOpsScrum
0 likes · 9 min read


DevOpsJan 25, 2021 · R&D Management
The article explains how to design and evolve agile R&D organization structures—from a small startup team to medium, large, and multinational groups—by applying high‑cohesion, low‑coupling, and full‑functionality principles, using Spotify’s squad‑tribe‑chapter‑guild model and rotation mechanisms to eliminate bottlenecks and single points of failure.
DevOpsLeadership RotationR&D Organization
0 likes · 26 min read

This article examines the transition from monolithic to microservice architecture, outlining the benefits and drawbacks of each, the conditions under which microservices should be adopted, the necessary technical and team resources, risk assessments, and practical guidance on service decomposition and migration.
architecturemicroservicesrisk assessment
0 likes · 18 min read

This article chronicles the five‑year evolution of Gaode Maps' application front‑end team, detailing how it grew from a handful of engineers handling short‑term activity development to a 100‑plus‑person group supporting five major business lines with dynamic rendering, performance optimization, and a robust engineering platform.
Amapcase studydynamic rendering
0 likes · 12 min read


21CTOSep 17, 2019 · R&D Management
The article examines the evolving technical leadership needs of a fast‑growing beauty social‑ecommerce startup, contrasting the roles of senior developer, technical manager, technical director, architect and CTO, and explains why a founder may actually need a technical manager rather than a CTO at early stages.
CTOarchitecturesoftware engineering management
0 likes · 12 min read

This article explores how small, focused teams can scale to multiple coordinated groups while preserving agility, comparing approaches like business‑unit feature teams and unrestricted feature teams through real cases from Alibaba, Spotify, and Alibaba Health.
Multi‑team DevelopmentProduct OrganizationSpotify Model
0 likes · 12 min read

This article explains how to determine the appropriate number of microservices for a large system and outlines four practical splitting strategies—by business logic, scalability, reliability, and performance—while emphasizing team size and service granularity to balance maintainability and efficiency.
System Designbackend architecturemicroservices
0 likes · 6 min read


21CTOMar 28, 2017 · R&D Management
Long‑running projects inevitably see their initial excitement with new frameworks fade as codebases grow, builds slow, and teams expand, leading to architectural decay; this article explains the causes, stages, and practical strategies—such as modularization, progressive builds, and disciplined technology adoption—to mitigate the problem.
Build OptimizationContinuous Integrationcodebase decay
0 likes · 24 min read


DevOpsMar 8, 2017 · Backend Development
This article recounts how a rapidly growing payment team split off from its original department, faced scaling, performance, and maintainability issues with a legacy SSH‑based Java architecture, and chose a micro‑service redesign, detailing the problems encountered, the restructuring approach, and the insights gained.
Backend Developmentlegacy systemperformance optimization
0 likes · 15 min read

This article explains how startup engineers can design and implement a scalable web architecture—covering server clustering, load balancing, distributed caching, database replication, and team organization—to handle rapid user growth without compromising performance or reliability.
Database ReplicationDistributed CachingWeb Scaling
0 likes · 15 min read


21CTOJun 17, 2016 · Backend Development
This article explains how startup engineers can design a scalable web system by separating services onto multiple servers, using load balancers, distributed caches, master‑slave replication, and team‑splitting strategies, ensuring performance and reliability as user traffic and data volumes surge.
Backend DevelopmentDatabase Replicationdistributed cache
0 likes · 15 min read

This article explains how startup engineers can design and evolve a scalable web architecture—covering server partitioning, load balancing, distributed caching, database replication, and team organization—to handle rapid user growth without compromising performance or reliability.
Database ReplicationDistributed Cachingload balancing
0 likes · 16 min read
