This article shares a senior technical director’s hard‑won lessons on balancing hands‑on development, non‑functional requirements, architecture design, training, and management to boost team productivity and product quality in software projects.
lead engineernon-functional requirementssoftware development
To build a scalable CRM, the article proposes a four‑step framework—defining goals, applying a full‑process digitalization methodology, designing a flexible, component‑based architecture that emphasizes configuration and light databases, and assembling an execution‑focused team—while detailing revenue‑maximizing levers, digitalization layers, and a closed‑loop feedback system.
This article shares a first‑hand account of how Vipshop’s infrastructure group introduced Scrum, detailing the motivations, role adjustments, optimal team composition, practical challenges, and take‑aways for other technical teams considering agile adoption.
The article reflects on the three career stages of software developers—junior, intermediate, and senior/architect—highlighting their evolving technical choices, team responsibilities, and the importance of experience, broad knowledge, and management skills for becoming an effective software architect.
The article explains how many founders over‑estimate a CTO’s ability to solve every technical problem, outlines six common CTO expectations in startups, and offers practical advice on aligning those expectations with the reality of technology leadership, team building, and data‑driven decision‑making.
The article explains how companies can foster an engineer‑driven culture through open workspaces, thoughtful benefits, hiring top talent, lean organizational structures, rapid product iteration, and continuous learning, ultimately boosting team performance and product outcomes.
The article explains the concept of facilitation, defines a facilitator as someone who inspires team energy and wisdom to achieve consensus and commitment, and outlines five key roles—including architect, pilot, guide, midwife, and observer—while recommending an IIFAC video for deeper insight.
The article shares practical lessons from a year of backend R&D experiments at Weibo, describing how a bottom‑up hybrid‑cloud solution, cross‑team collaboration, and systematic team‑building transformed the Feed service’s scalability, cost efficiency, and alignment with business goals.
The article lists fifteen common workplace obstacles—such as endless meetings, email overload, misguided productivity metrics, technical debt, non‑technical managers, poor documentation, distracting environments, and a relentless chase for the newest tools—that hinder developers from writing high‑quality code efficiently.
This article outlines the key qualities a Chief Technology Officer needs—including deep technical expertise, strategic vision, strong leadership, effective management, continuous learning, team culture building, cross‑department coordination, and clear communication with CEOs—to drive successful product development and company growth.
The article explains how internet startups can design and evolve a scalable web architecture—through service separation, clustering, load balancing, distributed caching, database replication, and effective team organization—to handle rapid user growth and avoid performance bottlenecks.
This article explores why efficient operations are hard to achieve, identifies common pitfalls such as unclear responsibilities, communication gaps, and resource mismatches, and presents a practical framework—including clear roles, professional processes, and a good service interface—to help operations teams become more effective and satisfied.
A seasoned operations leader discusses how e‑commerce operational support differs from general internet applications, covering longer support chains, consistency models, seasonal traffic spikes, team role separation, mobile‑internet challenges, future planning, and the rise of enterprise‑level ops services.
This article outlines practical communication techniques, environment choices, active listening, and emotional control for operations teams, then details how to define standards, build robust processes, and ensure reliable business continuity through clear responsibilities, monitoring, automation, and continuous improvement.
Process Standardsincident responseoperations best practices
This article shares NetEase Youdao Note’s practical Scrum experience, outlining when agile development fits, how to scale Scrum teams, the role of Scrum Masters, metrics for team performance, and tips for efficient sprint planning and cross‑team collaboration.
This article examines how Tuniu’s CTO leveraged architectural redesign, user‑experience enhancements, and a data‑driven team culture to build a scalable travel platform, automate packaging, and align technology with business goals in a fiercely competitive online tourism market.
This article explores how operations managers can define their positioning, adopt multiple leadership roles, and implement effective performance management practices—including clear goal setting, task allocation, coaching, and systematic review—to boost team efficiency and stability.
JD.com’s management philosophy, based on Liu Qiangdong’s view that team quality determines success, is explained through four core HR frameworks—Capability‑Values matrix, ABC authority hierarchy, 8‑12‑20 staffing ratios, and the 2N rule—detailing how the company selects, evaluates, and retains its 75,000‑plus workforce.
The article explains how startup engineers can design and evolve a scalable web architecture—through service separation, clustering, load balancing, distributed caching, database replication, and effective team organization—to handle rapid user growth and maintain performance without compromising user experience.
This article outlines ten practical management principles—from clarifying structure and goals to visualizing work and demanding results—that help leaders improve team accountability, transparency, and continuous improvement in operational environments.
This article outlines ten practical management principles—including clear structure, defined goals, appropriate delegation, visual tracking, and continuous improvement—to help leaders build high‑performing, accountable teams and avoid common pitfalls.
This article offers practical advice for aspiring lead developers, emphasizing personal responsibility, servant leadership, essential traits, leading by example, embracing accountability, fostering communication, and helping every team member succeed to create a high‑performing development team.
A seasoned CTO shares six recurring problems—from unfamiliar tools and over‑planning to poor stack choices and ignored patterns—offering practical advice on fostering learning, focusing on MVPs, encouraging code reuse, and promoting continuous development within engineering teams.
This article explains how to identify the root causes of low team efficiency, poor execution, and weak cohesion, offering practical steps such as diagnosing employee issues, creating clear HR policies, documenting problems, and fostering a trustworthy environment to address and eliminate troublemakers.
This article debates whether compact, full‑stack engineering teams are inherently unstable compared to larger, low‑tech “valley” teams, arguing that stability depends on a team's ability to nurture talent and continuously attract experts rather than relying on crude, static practices.
This article explores the characteristics, causes, and practical strategies for managing difficult or “thorny” team members in operations, offering case studies and step‑by‑step recommendations to mitigate risks while maintaining team performance.
The interview with Douban's chief architect Hong QN details the platform's online and offline architecture, including load balancing, the DAE PaaS, the BeansDB key‑value store, the DPark big‑data processing engine, and the team organization and operational practices that support these systems.