致谢 开源开发者的贡献

by Luciano Strika

通过卢西亚诺·斯特里卡(Luciano Strika)

对开源做出的贡献如何使我成为更好的开发人员，以及如何做到这一点 (How contributing to open source made me a better developer — and how you can do it, too)

So you’ve been learning how to code. You are studying Algorithms and Data Structures. You are getting up to date on the latest Frameworks and their quirks. You can already smell some code smells, or even design solutions to real problems.

因此，您一直在学习如何编码。 您正在研究算法和数据结构。 您正在了解最新的框架及其怪异之处。 您已经可以闻到一些代码的味道，甚至可以设计出针对实际问题的解决方案。

But you haven’t worked in the Software industry yet. Or you’re in your first job and see how everyone’s awesome and full of experience. Yet you feel like you’re the noobest of noobs. Impostor’s syndrome is a thing, and we’ve all been there.

但是您还没有在软件行业工作过。 或者，您在第一份工作中，看到每个人都很棒并且经验丰富。 但是，您感觉自己是菜鸟中的白痴。 冒名顶替综合症是一回事，我们都去过那里。

There’s a way to get experience working in real codebases, nailing down the skills a book won’t teach you.

有一种方法可以获取在实际代码库中工作的经验，确定一本书无法教给您的技能。

These are some of the things we can experience through Open Source:

这些是我们可以通过开源体验的一些东西：

• Reading other people’s code
  阅读别人的密码
• Understanding complex systems, one piece at a time
  一次了解一件复杂的系统
• Using versioning software (like git) in a proper way, with clear commit messages, atomic commits, and all those good, juicy practices.
  以正确的方式使用版本控制软件(如git)，并提供清晰的提交消息，原子提交以及所有这些好的多汁做法。

If you’ve read this post’s title, you know where this is going. As a Medium reader, you’ve read many times that contributing to Open Source is awesome. It will teach you a lot, and may even get you noticed by some Big-N recruiter or something. I won’t say all those things are guaranteed, but I can definitely vouch for the first two.

如果您已经阅读了该帖子的标题，那么您将知道前进的方向。 作为中型读者，您已经读过很多遍了，对开源做出的贡献真是棒极了。 它会教给您很多知识，甚至可能会让某些Big-N招聘人员注意到您。 我不会说所有这些东西都是可以保证的，但是我绝对可以保证前两个条件。

我的故事 (My story)

Let me tell you a story. When I started my first job, the repositories overwhelmed me. They had thousands of lines of code, they had conventions or lack of them, and the clashing styles. I had only worked on small college assignments. These assignments had 10000 lines tops, written by people I knew, over the span of a month.

让我告诉你一个故事。 当我开始第一份工作时，存储库使我不知所措。 他们有成千上万行代码，有或没有约定，以及样式冲突。 我只从事小型大学任务。 这些作业在一个月的时间里有10000行顶部，由我认识的人写。

I had never seen what a repository could fester into (or thrive into, if well maintained, but this is the industry we’re talking about here) after a couple of years of chaos and git reset - -hard‘s.

在经历了几年混乱和git reset - -hard的混乱之后，我从未见过存储库会恶化(或兴旺发展，如果维护得当的话，但这是我们在这里谈论的行业)。

Learning to navigate that codebase was a skill in and of itself, which I gained after months of practice. But then when I started browsing GitHub, looking for a place to crash (or push), I started seeing how other repositories where organized.

学习导航该代码库本身就是一项技能，这是我在几个月的练习后获得的。 但是，当我开始浏览GitHub，寻找崩溃(或推送)的地方时，我开始看到其他存储库的组织方式。

Now, I am by no means an expert. My experience on GitHub so far has mostly been that of what, in some circles, would be called a lurker. I read the code, see what code does, read the issues, and think ‘geez, I wish I had any idea where to start’.

现在，我绝不是专家。 到目前为止，我在GitHub上的经验主要是在某些圈子中被称为潜伏者。 我阅读了代码，看看代码做了什么，阅读了这些问题，然后想到“老兄，我希望我有从哪里开始的任何想法”。

But then something awesome happened: some guy on Reddit posted a small project he had been working on. Not that many lines of code, mostly in Python (my favorite language), and maintained mostly by himself, with the help of a couple more people. I saw my chance and caught it. Studied the code, saw that some of the Python scripts worked perfectly, but they were a bit ugly: bad practices, repetition, really basic stuff the kind of person that actually gets things done may not stop to think about while coding the first draft, but comes to bite you in the leg afterward. So I set out to refactor.

但是随后发生了一件令人敬畏的事情：Reddit上的某个人发布了他一直在从事的一个小项目。 并没有太多的代码行，主要是Python(我最喜欢的语言)，并且在更多人的帮助下，大部分都是由他自己维护的。 我看到了机会并抓住了它。 研究了代码，发现某些Python脚本可以很好地工作，但是它们有点丑陋：不良做法，重复，非常基础的东西可能真正完成工作的人在编写初稿时可能不会停止思考，但之后会咬你的腿。 所以我着手重构。

(By the way, that project was cheat.sh, an interactive, web cheat-sheet for developers. Here’s the GitHub project. It’s been an awesome project to contribute to, and I’d recommend you to check it out.)

(顺便说一句，该项目是cheat.sh ，这是一个面向开发人员的交互式Web备忘单。这是G itHub项目。这是一个很棒的项目，值得推荐，我建议您检查一下。)

教程 (A tutorial)

Along with this article, I made a tutorial so you can brush up on your git. I will assume we’re using a GitHub repo, as that’s what most of you may end up doing in your jobs. For this tutorial, I’ve set up a small example repository so you can follow along. Instructions are also present in the README.md file.

与本文一起，我编写了一个教程，以便您可以复习git。 我会假设我们正在使用GitHub存储库，因为这可能是大多数人最终在工作中所做的事情。 在本教程中，我建立了一个小的示例存储库，以便您可以继续。 README.md文件中也包含说明。

Here’s what you’ll have to do on this small assignment:

这是您在这项小任务上要做的：

• Visit the repository’s link, and hit the fork button. This will create a copy of the project’s history up until this point under your own profile.

  访问存储库的链接，然后单击fork按钮。 这将在您自己的个人资料下创建该项目历史的副本，直到此刻为止。

• Make a local directory in your computer
  在您的计算机中建立本地目录
• Add both my project, and the one you created, as remote repositories. In order to do this, open your terminal in the directory you’ve created and use the following command:
  将我的项目和您创建的项目都添加为远程存储库。 为此，请在创建的目录中打开终端，然后使用以下命令：

git remote add *name* *link*

It’s customary for the name of my project’s link to be ‘upstream’, and yours to be ‘origin’.

通常，我的项目链接的名称为“ 上游 ”，而您的链接的名称为“ 起源 ”。

• Pull my project:

  拉我的项目：

git pull origin master

• Add your name to the contributors list in the README.md using your favourite text editor (I like Vim, for instance). Don’t forget to save your changes!
  使用您喜欢的文本编辑器(例如，我喜欢Vim)将您的名字添加到README.md的贡献者列表中。 不要忘记保存您的更改！

• commit the changes:

  提交更改：

git add . && git commit -m ‘Your awesome message to me here’

• Go to your Github account, visit your copy of the project and hit ‘pull request’, choosing to merge your master branch with mine.

  转到您的Github帐户，访问该项目的副本并点击“ pull request ”，选择将您的主分支与我的合并。

I promise I will accept requests as soon as I can, probably on the same day… And that’s it! No different to how it would have worked if you were making a big contribution!

我保证我会尽快(可能在同一天)接受请求。就是这样！ 如果您做出了巨大的贡献，它的工作原理没有什么不同！

呼吁采取行动 (Call to action)

Now you have no excuse, go find a project you actually like or care about and add some lines to it! It doesn’t matter if your changes are small, as long as you’re helping and learning through them. My first contribution was correcting a typo in a README.

现在，您没有任何借口，找到您真正喜欢或关心的项目，并在其中添加一些行！ 只要您正在帮助并从中学习，更改的大小就无关紧要。 我的第一个贡献是纠正自述文件中的错字。

I am trying new things this year, and writing on Medium has been on my bucket list for a while now.

我今年正在尝试新事物，而在Medium上写东西已经有一段时间了。

This was my first ever article, and I will be glad if you give me any feedback or opinions on anything you’ve read.

这是我的第一篇文章，如果您对所读内容有任何反馈或意见，我将感到高兴。

Also as I am new to Open Source software, please tell me if there’s anything important you feel I’ve missed. Finally, if you’ve already made Open Source contributions, I’d like to hear some stories and opinions. What are the best projects to contribute to, and the ones you’ve liked the most/least? It would be nice if we could compile a list for beginners.

另外，由于我是开源软件的新手，请告诉我您是否错过了重要的事情。 最后，如果您已经做出了开源贡献，那么我想听听一些故事和观点。 什么是最好的项目，哪些是您最喜欢/最不喜欢的项目？ 如果我们可以为初学者编写一个列表，那将是很好的。

Thanks for reading this far, I’ll see you soon!

多谢您阅读本文，我很快就会再见！

Follow me for more articles about programming and Data Science, and check out my latest (probably better) articles.

关注我以获取更多有关编程和数据科学的文章，并查看我的最新文章(可能更好)。

翻译自: https://www.freecodecamp.org/news/how-contributing-to-open-source-made-me-a-better-developer-and-how-you-can-do-the-same-89929cd9f497/

致谢 开源开发者的贡献