1. 把东西从一个地方移到另一个地方。 大多数事物只有在特定位置时才有价值。 食物、衣服和住所只有在靠近您碰巧所在的地方时才对您有价值。 因此，您只需将无用的东西从无用的地方转移到有用的地方，就可以创造财富。 这听起来很简单，但这是航运业的基础。 2. 存放东西。 正如事物的价值往往与它们的位置有关，价值也往往与特定的时间有关。 例如，冬衣在冬天比在夏天更有用。 让东西保持可用状态直到它们变得有用通常是一项非常重要的工作（考虑在过季时保持水果和蔬菜可用的问题）。 因此，你可以简单地通过坚持某样东西并将其保持在工作状态直到它对某人有用为止来创造价值。 正如移动物品是航运业的基础一样，存储物品是零售业的基础。 商店之所以称为商店，是因为它们曾经是存放东西的地方，而不一定是出售东西的地方。 3. 以化学或机械方式改变事物。这是制造业的基础。实际上，事实证明我确实需要多说一点。 这确实是制造业... [更多...]

工具 免费的ocr软件（图片转文字） https://github.com/hiroi-sora/Umi-OCR 一款功能强大的电子书管理工具。它是集下载、格式转化、制作、管理于一体的电子书工具，比如可以将 txt 文本，转化成包含作者信息和书籍封面的 mobi 文件，制作完成后还可以直接发送到 Kindle 设备上。 https://github.com/kovidgoyal/calibre   资源分享 一个声音博物馆 http://savethesounds.info/ ICON搜索 https://icongo.github.io/ 言论 不必记恨说坏话的人，因为他们用另一种方式让你看清楚自己。 很多时候，虽然错过了一个站台，却可以收获一片风景。 在乡土社会中法律是无从发生的。... [更多...]

能够立即有效地浏览整个代码库意味着很容易找到相关的库来重用和好的例子来复制。 Most of the time, developers won’t notice when indices are out of date. They only care about a small subset of code, and even for that they generally won’t know whether there is more recent code. However, for the cases in which they wrote or reviewed the corresponding change, being out of sync can cause a lot of confusion. It tends not to matter whether the ... [更多...]

In all of this thinking, we’re assigning special significance to the trunk branch. But of course, “trunk” in your VCS is only the technology default, and an organization can choose different policies on top of that. Perhaps the default branch has been abandoned and all work actually happens on some custom development branch—other than needing to provide a branch name in more operations, there’s no... [更多...]

Our discussion of deprecation begins from the fundamental premise that code is a liability, not an asset. After all, if code were an asset, why should we even bother spending time trying to turn down and remove obsolete systems? Code has costs, some of which are borne in the process of creating a system, but many other costs are borne as a system is maintained across its lifetime. These ongoing co... [更多...]

Unit tests are limited by the imagination of the engineer writing them. That is, they can only test for anticipated behaviors and inputs. However, issues that users find with a product are mostly unanticipated (otherwise it would be unlikely that they would make it to end users as issues). This fact suggests that different test techniques are needed to test for unanticipated behaviors.（单元测试受到编写它们的... [更多...]

Writing testable code requires an upfront investment. It is especially critical early in the lifetime of a codebase because the later testability is taken into account, the more difficult it is to apply to a codebase. Code written without testing in mind typically needs to be refactored or rewritten before you can add appropriate tests.（编写可测试代码需要前期投入。在代码库生命周期的早期，这一点尤其重要，因为越晚考虑可测试性，就越难应用到代码库中。在没有考虑... [更多...]

At Google, we’ve found that engineers sometimes need to be persuaded that testing via public APIs is better than testing against implementation details. The reluctance is understandable because it’s often much easier to write tests focused on the piece of code you just wrote rather than figuring out how that code affects the system as a whole. Nevertheless, we have found it valuable to encourage s... [更多...]

Unlike the QA processes of yore, in which rooms of dedicated software testers pored over new versions of a system, exercising every possible behavior, the engineers who build systems today play an active and integral role in writing and running automated tests for their own code. Even in companies where QA is a prominent organization, developer-written tests are commonplace. At the speed and scale... [更多...]

Instead, before you begin writing, you should (formally or informally) identify the audience(s) your documents need to satisfy. A design document might need to persuade decision makers. A tutorial might need to provide very explicit instructions to someone utterly unfamiliar with your codebase. An API might need to provide complete and accurate reference information for any users of that API, be t... [更多...]