清除缓存代码_清除代码著名报价。

清除缓存代码

The phrase “software engineering” was terms at conferences organized by NATO in 1968 and 1969 to discuss the ‘software crisis’. If we consider 1968 as the starting point of software engineering as a profession, it is over 50+ years of engineering practice.

“ 软件工程 ”一词是北约在1968年和1969年组织的讨论“软件危机”的会议上的用语。 如果我们将1968年作为软件工程专业的起点，那么它已经有50多年的工程实践经验。

“ Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn’t have to be that way ” from Clean Code: A Handbook of Agile Software Craftsmanship.

“即使错误的代码也可以起作用。 但是，如果代码不干净，它可能会使开发组织屈服。 每年，由于编写不良的代码而浪费了无数的时间和大量的资源。 但这并不一定就是这种方式”，它来自《 清洁代码：敏捷软件技巧手册》。

It is not enough for code to work.

代码工作还不够。

Redundant comments are just places to collect lies and misinformation.

多余的评论只是收集谎言和错误信息的地方。

So if you want to go fast, if you want to get done quickly, if you want your code to be easy to write, make it easy to read.

因此，如果您想快点做，如果想快速完成，要使代码易于编写，请使其易于阅读。

A long descriptive name is better than a short enigmatic name. A long descriptive name is better than a long descriptive comment.

长的描述性名称比短的神秘性名称更好。 长描述性名称胜于长描述性注释。

SRP is one of the more important concept in OO design. It’s also one of the simpler concepts to understand and adhere to. Yet oddly, SRP is often the most abused class design principle.

SRP是面向对象设计中更重要的概念之一。 它也是易于理解和坚持的简单概念之一。 但是奇怪的是，SRP通常是最滥用的类设计原则。

You should name a variable using the same care with which you name a first-born child.

命名变量的命名方式应与头胎孩子的命名方式相同。

Don’t Use a Comment When You Can Use a Function or a Variable

可以使用函数或变量时不要使用注释

When you see commented-out code, delete it!

当您看到注释掉的代码时，将其删除！

Truth can only be found in one place: the code.

真理只能在一个地方找到：代码。

Indeed, the ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code. …[Therefore,] making it easy to read makes it easier to write.

确实，读与写所花费的时间比例远超过10：1。作为编写新代码的一部分，我们不断读取旧代码。 …[因此，]使其易于阅读使其易于书写。

So if you want to go fast, if you want to get done quickly, if you want your code to be easy to write, make it easy to read.

因此，如果您想快点做，如果想快速完成，要使代码易于编写，请使其易于阅读。

Of course bad code can be cleaned up. But it’s very expensive.

当然可以清除不良代码。 但这非常昂贵。

It is not the language that makes programs appear simple. It is the programmer that make the language appear simple!

并不是使程序看起来简单的语言。 是程序员使语言显得简单！

There are two parts to learning craftsmanship: knowledge and work. You must gain the knowledge of principles, patterns, practices, and heuristics that a craftsman knows, and you must also grind that knowledge into your fingers, eyes, and gut by working hard and practicing.

学习Craft.io分为两部分：知识和工作。 您必须了解工匠知道的原理，模式，实践和启发式知识，并且还必须通过努力工作和练习将这些知识磨成手指，眼睛和内脏。

O

Ø

Programmers must avoid leaving false clues that obscure the meaning of code.

程序员必须避免留下掩盖代码含义的错误线索。

The proper use of comments is to compensate for our failure to express ourself in code. Note that I used the word failure. I meant it. Comments are always failures.

注释的正确用法是为了弥补我们未能在代码中表达自己的意愿。 请注意，我使用了失败一词。 我是真的 评论总是失败。

Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best.

编写干净的代码是您必须称呼自己为专业人士。 没有什么比做最好的事情合理的借口了。

If the discipline of requirements specification has taught us anything, it is that well-specified requirements are as formal as code and can act as executable tests of that code!

如果需求规范的学科教会了我们任何东西，那就是明确规定的需求就像代码一样正式，并且可以充当该代码的可执行测试！

Honesty in small things is not a small thing.

在小事上诚实不是一件小事。

谢谢阅读！ 🍻 (Thanks for reading! 🍻)

翻译自: https://medium.com/swlh/clean-code-famous-quotes-6d62d396cfe0

清除缓存代码