loniecc commented on a change in pull request #386:
URL: https://github.com/apache/flink-web/pull/386#discussion_r620874828
##########
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.
+另一组评判标准是代码是否使用了简洁的设计和架构，不管是通过概念分割实现了良好的结构，还是使用了简单易懂的代码。该评判标准需要良好的解决软件工程问题。一个好的解决方案需要代码是容易被测试的，可以被除了原作者之外的其他人维护的（因为突然中断之后再维护是非常困难的），同时还需要能够高效的迭代演进的。
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
