Growth of a Technical Leader: Lessons from My Years as an Architect at Dangdang

What is Technical Leadership

The author defines technical leadership as the ability to guide a team toward shared goals, drawing on Amazon’s leadership principles and emphasizing the importance of “getting things done” together.

My Years at Dangdang as an Architect

From 2012 to 2016, the author participated in major projects such as the recruitment platform reconstruction, order system planning, architecture planning, technology‑stack migration, and the creation of a foundation platform, while also leading open‑source initiatives like DDFrame, DubboX, Elastic‑Job, and Sharding‑JDBC.

Recruitment Platform Reconstruction

In 2012 the author joined a fragmented system landscape and helped redesign the third‑party merchant onboarding platform, aiming to integrate it with Dangdang’s self‑operated sales flow and reduce duplicated components.

Order Refactoring Planning

The author clarified that the order system, originally built on .NET + SQL Server, needed decoupling for flexibility, and leveraged cross‑system projects in 2013 to enhance order functionality.

Architecture Planning and Technology Stack Selection

By 2014 the author led the architecture department, producing business‑level and technical architecture blueprints, introducing multiple technology stacks (PHP, .NET, Java) and promoting a middleware‑centric “technical middle‑platform” with MQ, caching, databases, scheduling, search, and big‑data components.

Application Framework and Open‑Source Components

The team built DDFrame to unify the tech stack, created DubboX (a REST‑enabled fork of Dubbo), developed Elastic‑Job for distributed task scheduling, and later contributed Sharding‑JDBC (now Apache ShardingSphere) to the open‑source community.

Foundation Platform

In 2016 the author helped establish a foundation platform to digitize the software lifecycle—project management, automated deployment, monitoring, alerting, and issue tracking—supporting agile processes and improving team efficiency.

Four Elements of Growth

The author distills personal growth into four progressive elements: learning (understanding business and industry), adapting (integrating into the team and processes), collaborating (building trust through joint outcomes), and driving (sharing knowledge, influencing decisions, and promoting the organization).

How to Learn

Study competitors, analyze business processes, read industry books and watch documentaries, and collect conference materials to broaden perspective.

How to Adapt

Familiarize yourself with the org chart, understand department responsibilities, actively participate, observe, and document insights.

How to Collaborate

Offer help without seeking credit, compromise when resources are limited, communicate openly, and build trust through delivered results.

How to Drive

Take ownership, share knowledge internally and externally, mentor newcomers, influence key stakeholders, and showcase achievements through industry talks.

Point‑Line‑Plane‑Body

The growth process follows a geometric metaphor, expanding influence from a point to a line, plane, and finally a three‑dimensional body, reflecting increasing impact.

Regrets

The author reflects on missed opportunities, such as limited decision‑maker focus on architecture, insufficient impact on search/mobile/data platforms, incomplete platformization, and not fostering broader open‑source participation.

Acknowledgements

Gratitude is expressed to HR, the architecture department leadership, and colleagues for enabling the author’s transition from traditional IT to internet‑scale engineering.