loniecc commented on a change in pull request #386:
URL: https://github.com/apache/flink-web/pull/386#discussion_r620874392
##########
File path: contributing/code-style-and-quality-preamble.zh.md
##########
@@ -1,25 +1,23 @@
---
-title: "Apache Flink Code Style and Quality Guide — Preamble"
+title: "Apache Flink 代码风格和质量指南 — 序言"
---
{% include code-style-navbar.zh.md %}
+这是一次为了保证那些被我们维护的代码和质量标准的尝试
-This is an attempt to capture the code and quality standard that we want to
maintain.
+一次代码贡献(或者任何代码片段)可以从很多角度进行评价：一组评判标准是代码是否正确和高效。这需要正确且良好的解决逻辑或者算法问题。
-A code contribution (or any piece of code) can be evaluated in various ways:
One set of properties is whether the code is correct and efficient. This
requires solving the _logical or algorithmic problem_ correctly and well.
+另一组评判标准是代码是否使用了简洁的设计和架构，不管是通过概念分割实现了良好的结构，还是使用了简单易懂的代码。该评判标准需要良好的解决软件工程问题。一个好的解决方案需要代码是容易被测试的，可以被除了原作者之外的其他人维护的（因为突然中断之后再维护是非常困难的），同时还需要能够高效的迭代演进的。
-Another set of properties is whether the code follows an intuitive design and
architecture, whether it is well structured with right separation of concerns,
and whether the code is easily understandable and makes its assumptions
explicit. That set of properties requires solving the _software engineering
problem_ well. A good solution implies that the code is easily testable,
maintainable also by other people than the original authors (because it is
harder to accidentally break), and efficient to evolve.
+不过第一组标准有相当客观的达成条件，相比之下要达到第二组评判标准更加困难，但是对于 Apache Flink
这样的开源项目来说却非常重要。为了基础的代码能够邀请到更多开发者，为了的开源贡献能够更容易被开发者理解，同时也为了众多开发者同时开发时代码的健壮性，良好工程化的代码是至关重要的。对于良好的工程代码来说，更加容易保证代码的正确性和高效不会随着时间的推移受到影响
-While the first set of properties has rather objective approval criteria, the
second set of properties is much harder to assess, but is of high importance
for an open source project like Apache Flink. To make the code base inviting to
many contributors, to make contributions easy to understand for developers that
did not write the original code, and to make the code robust in the face of
many contributions, well engineered code is crucial.[^1] For well engineered
code, it is easier to keep it correct and fast over time.
+当然，本指南并不是一份如何写出良好的工程代码的全方位指导。有相当多的书籍尝试说明如何实现良好的代码。本指南仅仅尝试作为最佳实践的检查单，因为模式，反模式和常见错误我们都在开发Flink的时候遇见过。
Review comment:
确实，已修改
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
