Beyond Coding: How Engineers Can Iterate Their Careers and Lead Teams Effectively

Redefining Success for Engineers

Three categories of professional success are defined:

Self‑success : achieving personal goals and mastering one’s own tasks.

Cooperation success : delivering complex outcomes together with other team members.

Empowerment success : leading a team so that members can perform better with minimal direct effort from the leader.

The focus of the talk is on how engineers can move from cooperation to empowerment.

1.1 Cooperation Success – The Small “T‑shaped” Engineer

A small T‑shaped engineer combines deep expertise (the vertical bar) with a modest breadth of knowledge (the horizontal bar). The depth dimension requires:

Systematic learning : continuously acquire related knowledge across the domain (e.g., video coding, transmission, distributed computing).

Deep understanding : apply the knowledge to real projects, not just theory.

To expand breadth, concentrate on three practical steps:

Key concepts : learn the terminology of adjacent fields (cloud‑native, databases, etc.).

Shared language : build a common vocabulary within the organization so that everyone can understand each other.

Interaction interface : align communication patterns so that both sides can express and receive information effectively.

These steps embody the principle “know the other, let the other know you.”

1.2 Empowerment Success – The Big “T‑shaped” Engineer

A big T‑shaped engineer extends the vertical bar to cover multiple technical domains (product, operations, infrastructure) and adds non‑technical capabilities:

“Art” (術) : communication, writing, logical reasoning, and self‑control.

“Way” (道) : problem‑driven mindset, result orientation, and an “end‑to‑beginning” (reverse‑engineering) philosophy.

You can change yourself through continuous iteration; leaders facilitate this process rather than impose change.

Managerial Practices – “Three Meetings and One Understanding”

Effective managers master four capabilities:

Set goals : make them Specific, Measurable, Acceptable, Result‑oriented, Time‑bound (SMART).

Hold meetings :

Regular sync meetings follow the “five‑yes, five‑no, four‑framework” rules and avoid deep detail.

Topic‑focused meetings define participants, decision‑makers, note‑takers, and executors.

Conduct retrospectives :

Small‑scale, timely reviews for minor issues.

Stage‑based periodic reviews (weekly, bi‑weekly, monthly) for larger initiatives.

Comprehensive post‑project reviews after delivery.

Understand trade‑offs : strategically decide what to attack (focus) and what to defend (avoid).

2.1 The “WWH” Perspective

Team members are grouped by role, each asking a different question:

Engineer – How : practical execution, avoiding pitfalls, experimenting, engineering, iterating.

Team Leader – What : evaluating alternatives, comparing technologies, assessing maturity and industry adoption.

Director – Why : strategic justification, using techniques such as “5 Why” to uncover root causes.

2.2 Iterating Toward Management

Career progression requires shifting emphasis:

Senior engineers deepen “what” and “how” while beginning to understand “why”.

Experts focus on “why” while maintaining breadth in “what” and “how”.

Managers prioritize strategic “why”.

The goal is a balanced awareness across all three layers.

AIGC Era and the “Jellyfish” Development Model

Generative AI (AIGC) excels at structured, repetitive tasks. The proposed “jellyfish” model assigns the human (the head) to define problems, design solutions, and set goals, while AIGC (the tentacles) assists with selection, code generation, testing, and other auxiliary work.

Key takeaways:

AIGC is a tool that amplifies human capability; it does not replace human judgment.

Adopting AIGC lowers entry barriers, democratizing technical knowledge.

Engineers should maintain a growth mindset, stay optimistic, and continuously iterate their skills.

Code example

相关阅读：