7 Surprising Lessons to Turn Your Tech Expertise into Career Growth

Architect Da Liu, a senior engineer who became a company architect, feels bewildered as his former colleague Lao Tian, whom he once recommended, rises to become his manager with a much higher salary.

Through a candid conversation over dinner, Lao Tian shares the habits that helped him advance, and Da Liu reflects on his own shortcomings.

1. Read More Code from Others

Da Liu enjoys reading high‑quality open‑source code but dismisses his own company’s code as "code mountains" and avoids studying it. Lao Tian, however, knows the internal code deeply and can quickly locate problems.

Reading all code, regardless of quality, helps you identify bad patterns and become irreplaceable.

2. Accurately Judge Project Direction

Lao Tian continuously improves a monitoring system, turning it into a valuable APM product that wins new business, while Da Liu’s own scheduling framework suffers from poor tooling and low adoption.

The ability to foresee a project’s potential and align it with market needs distinguishes successful engineers.

3. Proactively Manage Meetings

Lao Tian consolidates meetings into a single block, prepares agenda and solutions in advance, and skips unimportant gatherings, preserving uninterrupted time for deep work.

4. Master Version Control Tools

Lao Tian enforces strict version‑control guidelines, provides training, and documents best practices, resulting in a one‑third increase in development speed for his team.

5. Avoid Over‑Engineering Solutions

Both recognize that unnecessary complexity harms delivery; Lao Tian intervenes early to prevent over‑design, ensuring simple internal tools remain maintainable.

6. Organize Tasks Systematically

Lao Tian prioritizes tasks based on impact, communicates clearly with stakeholders, and confidently says no to low‑value work, whereas Da Liu often lets urgency dictate his schedule, leading to fragmented efforts.

7. Write Flexible, Thoughtful Code

Beyond avoiding bugs, engineers should consider how users and operations will actually use features, anticipating edge cases and future requirements to prevent costly rework.