“为什么”文档的重要性 #6904
Merged
“为什么”文档的重要性 #6904
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
|
认领校对 |
|
@todaycoder001 好的呢 🍺 |
|
校对认领 |
|
@Raoul1996 妥妥哒 🍻 |
Raoul1996
reviewed
Apr 13, 2020
| * Lacking resources on a project | ||
| * Known bugs we’d like to mitigate | ||
| * User-traffic patterns | ||
| * 紧迫的截止期限。 |
…ortance-of-why-docs.md
…ortance-of-why-docs.md
…reading suggestions
|
@Raoul1996 感谢校对😄。已经根据你的意见提交了修改，看看改得合不合适？ |
evanzme
reviewed
Apr 16, 2020
| > * 校对者： | ||
|
|
||
| # The Importance of “Why” Docs | ||
| # “为什么”文档的重要性 |
There was a problem hiding this comment.
Suggested change
| # “为什么”文档的重要性 | |
| # “为什么”文档很重要性 |
|
|
||
|  on [Unsplash](https://unsplash.com/s/photos/why?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)](https://cdn-images-1.medium.com/max/10368/1*2KhDOt8Dgcq17b-8rlMsig.jpeg) | ||
|
|
||
| Many of us have, at one time or another, blindly followed a pattern we noticed, thinking that must be the way to do it. We do so without questioning if that pattern is the best fit for our particular situation or if that pattern was ever a good idea to begin with. | ||
| 我们中的许多人曾经盲目地遵循我们所被告知的模式，认为那一定是做这件事情的正确方式。我们就这样照做了，而没有怀疑那个模式对于我们所处的特殊情形是不是最佳选择，或者那个模式从一开始就不够好。 |
There was a problem hiding this comment.
Suggested change
| 我们中的许多人曾经盲目地遵循我们所被告知的模式，认为那一定是做这件事情的正确方式。我们就这样照做了，而没有怀疑那个模式对于我们所处的特殊情形是不是最佳选择，或者那个模式从一开始就不够好。 | |
| 我们中的许多人曾经盲目地追随我们所被告知的样子，认为那样做是对的。我们那样做时，不会质疑那样做在特定条件下是不是最佳选择，或者那个样子一开始就不是自己想要的。 |
TODO1/the-importance-of-why-docs.md
Outdated
|
|
||
| In doing this, we rob ourselves of the opportunity to learn and deepen our understanding, to be intentional with our work, and, ultimately, to get better at our craft. Even more, we set yet another precedent for colleagues to do the same, instead of encouraging them to dig deeper. | ||
| 在我们盲目照做的时候，我们放弃了学习和深化理解、专心工作以及最终提高技术的机会。甚至我们为同事树立了另一个照做的先例，而不是鼓励他们更深入其中。 |
There was a problem hiding this comment.
Suggested change
| 在我们盲目照做的时候，我们放弃了学习和深化理解、专心工作以及最终提高技术的机会。甚至我们为同事树立了另一个照做的先例，而不是鼓励他们更深入其中。 | |
| 在这样做时，我们剥夺了自己学习和加深理解的机会，去有意识地对待我们的工作，并最终提高我们的技能。 | |
| 更何况，我们为同事们树立了另一个先例，而不是鼓励他们更深入地学习。 |
|
|
||
| We’ll also go over how Bytebase makes sharing and finding the “why” behind your team’s work easy. | ||
| 我们也会复盘 Bytebase 是如何让发现和分享团队工作中隐藏的“为什么”变得容易的。 |
There was a problem hiding this comment.
Suggested change
| 我们也会复盘 Bytebase 是如何让发现和分享团队工作中隐藏的“为什么”变得容易的。 | |
| 我们还将讨论 Bytebase 如何使共享变得容易，并找到团队工作背后的“为什么”。 |
|
@QinRoc 校对完毕 |
evanzme
approved these changes
Apr 19, 2020
|
@QinRoc 我在您的 fork 里提了个 pr，您 merge 一下哈 |
|
@QinRoc 已经 merge 啦~ 快快麻溜发布到掘金然后给我发下链接，方便及时添加积分哟。 掘金翻译计划有自己的知乎专栏，你也可以投稿哈，推荐使用一个好用的插件。 |
Merged
|
@todaycoder001 感谢校对，根据你的意见所做的改动，在这里哈 #6942 |
|
@lsvih @Raoul1996 @todaycoder001 文章已发布： |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
译文翻译完成，resolve #6869