10 Essential Principles Every Engineer Should Follow to Accelerate Growth

The original article, titled “10 Advice for Engineers,” is written by Yunpeng, a Meituan engineer who joined in 2014 and now leads travel CRM and core information services.

Principle One: Owner Mindset

Owner mindset involves two aspects: a responsible attitude and proactive spirit. Responsibility means delivering high‑quality design documents, code, and tests, and being accountable for system architecture, interfaces, logs, databases, and caches. Proactivity means actively solving customer issues, suggesting performance improvements, and taking initiative in cross‑team collaborations.

Principle Two: Time Awareness

Effective time management requires planning and prioritization. Break projects into fine‑grained tasks (at least to the pd level) to create accurate schedules, define checkable deliverables, and set key milestones. Use the Eisenhower matrix to distinguish urgent‑important work from less critical tasks, ensuring timely delivery.

Principle Three: Begin With the End in Mind

Define clear goals before starting work. In performance‑optimization projects, set concrete targets (e.g., TP99 < X ms, QPS > Y) based on business needs. In learning, ask what specific knowledge you aim to acquire, such as Redis persistence or cluster architecture, to guide efficient study.

Principle Four: Closed‑Loop Thinking

Ensure every task has a clear outcome, feedback, and verification. After meetings, confirm minutes, track To‑Do items, and verify completion. Regularly report progress to leaders to avoid information asymmetry and build trust.

Principle Five: Maintain Reverence

Respect established norms—code style, design standards, deployment procedures—because they are the result of accumulated experience. Learn and follow team conventions early to avoid costly rework, and propose updates only after thorough discussion.

Principle Six: No More Than Two Iterations

Limit reviews to at most two rounds to prevent endless discussions and preserve development time. If a review fails twice, conduct a case study to identify root causes and prevent recurrence.

Principle Seven: Design First

Prioritize thorough architecture design. Write clear, logical design documents that are easy for others to understand, using abstract‑to‑concrete structure and detailed module relationships. Review designs with senior engineers or PMs before implementation.

Principle Eight: Balance Output and Capacity (P/PC)

Ensure the value delivered (output) matches the team’s ability to sustain it (capacity). Continuously optimize system architecture to support business growth, and invest in personal skill development to maintain high productivity without burnout.

Principle Nine: Ask Good Questions

Be curious and ask questions during design or code reviews. Use critical thinking to evaluate arguments, verify evidence, and deepen understanding. Asking insightful questions drives better decisions and collective learning.

Principle Ten: Empty‑Cup Mindset

Stay humble and continuously self‑evaluate. Seek feedback, compare with peers, and be open to suggestions. A humble attitude turns confidence into sustainable growth rather than complacency.

Conclusion

The ten principles—owner mindset, time awareness, beginning with the end, closed‑loop thinking, reverence for norms, limiting iterations, design first, output‑capacity balance, asking good questions, and an empty‑cup mindset—are distilled from years of experience and aim to guide engineers and teams toward stronger performance and continuous improvement.