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