32位系统能够识别多达内存_向多达17位用户学习
32位系統能夠識別多達內存
by Jacob Evelyn
雅各布·伊夫林(Jacob Evelyn)
四個開源課程—來自多達17個用戶 (Four open source lessons—from a whopping 17 users)
I have an open-source project. It has 17 users.
我有一個開源項目 。 它有17個用戶。
It actually has somehow scraped together a few hundred stars on GitHub, managing to be the most-starred repository for a few wildly popular tags like relationships, human-readable, and journaling (but, alas, not journal). You’re probably very impressed. You may be thinking something like, “What useless piece of code could possibly be at the intersection of those things?” or “GitHub has tags?”
實際上,它在某種程度上在GitHub上拼湊了幾百個星星,成為了一些最受歡迎的標簽(如relationships , human-readable和journaling (但可惜的是,不是journal ),成為最受關注的存儲庫。 您可能會留下深刻的印象。 您可能會想,“這些東西的交匯處可能有什么無用的代碼?” 或“ GitHub有標簽?”
But don’t be intimidated by my extraordinary success. Three years ago, all this was just a few lines of code and an idea. I wanted to see if I could visualize the ebbs and flows of my relationships with the people I care about.
但是不要被我的非凡成就所嚇倒。 三年前,所有這些只是幾行代碼和一個想法。 我想看看我是否可以形象化我與所關心的人的關系的起伏。
I also wanted to have a program tell me who I haven’t talked to in a while, so I could be better at staying in touch. Okay, and I also wanted to store all of this information in a way that was easy to see, edit, and play with. I guess it was more than one idea after all.
我還希望有一個程序可以告訴我我已經一段時間沒有與誰交談了,因此我可以更好地保持聯系。 好的,我還想以一種易于查看,編輯和使用的方式存儲所有這些信息。 我想那畢竟不只是一個主意。
That should have been the first clue that I didn’t have the clearest idea what I was doing. But I’m strong-willed and felt confident that I’d figure out the details later.
那應該是我沒有最清楚自己在做什么的第一個線索。 但是我很愿意并且有信心以后再去弄清楚細節。
So I hacked together a program that I called friends (tagline: Spend time with the people you care about. Introvert-tested. Extrovert-approved.) and used it regularly for a year, at which point I assumed that its (minimal) featureset was complete. On a whim, I posted it to Hacker News, where it briefly made the front page for the first and only time in my life. (Side note: if you ever see a post on Hacker News in which a calm comment reads something like, Maintainer here. I'm glad to see this on the front page, and happy to answer any questions. don’t believe for a second that that person isn’t shaking with uncontrollable nervousness and excitement.)
因此,我共同編寫了一個程序,稱為“ friends (標語: 與您關心的人一起度過。內向測試。完成了。 我一時興起, 將其發布到Hacker News ,在該新聞中 ,這是我一生中第一次也是唯一一次登上首頁。 (旁注:如果您在Hacker News上看到過一篇平靜的評論,內容類似“ Maintainer here. I'm glad to see this on the front page, and happy to answer any questions.其次,那個人沒有因無法控制的緊張和激動而發抖。)
And then an interesting thing happened. I got suggestions.
然后發生了一件有趣的事情。 我有建議。
第1課:用戶有很好的想法 (Lesson 1: Users have really good ideas)
My friends and coworkers, bless them, will tell you I have no problem “sharing my opinion.” Translation: I usually think I’m right and can have a hard time accepting input from others. (Not cookies though, I accept those fine.)
我的朋友和同事們,祝福他們,會告訴您我“分享意見”沒有問題。 翻譯:我通常認為我是對的,很難接受別人的意見。 (盡管不是cookie,我接受那些罰款。)
I thought I knew about my own project. However, my pompousness disappeared pretty much immediately when I started reading users’ suggestions. To date, I’ve had 16 (!!!) GitHub issues opened by someone other than me. (Out of a total of 110. I need to get out more.) And almost every one of those has been a suggestion that I would never have thought of and that makes friends unequivocally better. In fact, counter-intuitively, these new features have been so spot-on that they’ve often led to much simpler code.
我以為我知道自己的項目。 但是,當我開始閱讀用戶的建議時,我的自負很快就消失了。 到目前為止,我有16個(!!!)GitHub問題由除我之外的其他人提出。 (總共110個 。我需要更多。)而且幾乎每個建議都是我從未想過的建議,這無疑使friends變得更好。 實際上,與直覺相反的是,這些新功能非常受關注,以至于它們常常導致代碼簡單得多。
What has amazed me the most is how these users often seem to “get” the idea of friends better than I do.
最令我驚訝的是,這些用戶似乎常常比我更好地“理解” friends的想法。
I consider friends to only have 17 users despite all of its downloads and GitHub stars. This is because only 17 people have cared enough to share their feedback with me or offer to contribute a pull request. I don’t know if others are using it in perfect bliss or downloaded it once and then forgot about it. But 17 people have dedicated time and energy to show they care. I love every single one of them.
我認為,盡管有所有下載和GitHub明星,但friends只有17個用戶。 這是因為只有17個人足夠關心與我分享他們的反饋或主動提出拉取請求。 我不知道其他人是在極樂中使用它還是下載一次然后忘了它。 但是有17個人有時間和精力來表示自己的關心。 我愛他們每個人。
第2課:友善回報 (Lesson 2: Being nice pays off)
From the beginning, I wanted to be a friendly, supportive, patient, mentoring maintainer. Not the gruff maintainer who says “this feature should not be added” with no further explanation.
從一開始,我就想成為一個友好,支持,耐心和指導的維護者。 不是粗魯的維護者說“不應添加此功能”,而沒有進一步的解釋。
So I added this friendly note to the top of the README:
所以我在README的頂部添加了這個友好的注釋:
NOTE: Participation is encouraged! Make issues, ask questions, submit pull requests (even if it’s your first time contributing to open-source — you’ll get lots of help), and give feedback!
注意:鼓勵參與! 提出問題,提出問題,提交請求(即使這是您第一次為開源做貢獻-您將獲得很多幫助),并提供反饋!
I adopted the Contributor Covenant. I added friendly contribution instructions. I made sure friends followed all of GitHub’s best practices.
我通過了《 貢獻者公約》 。 我添加了友好的貢獻說明 。 我確保friends遵循GitHub的所有最佳做法 。
And I put in the time and effort to be friendly when responding to users. I knew that was the right decision when users started leaving comments like:
在回應用戶時,我投入了時間和精力來保持友好。 我知道當用戶開始發表如下評論時,這是正確的決定:
“Excellent. Thanks for your patience and suggestions. I’m pretty green with this stuff.”
“優秀的。 感謝您的耐心等待和建議。 這些東西我挺綠的?!?
“This my first pull request to an open source. I learn Many things from your Comments. Thank you So much for that.”
“這是我對開源的第一個請求。 我從您的評論中學到了很多東西。 對此感激不盡?!?
“Thanks for the explanation! … Also, I gotta say, your cheeriness is great! ?”
“感謝您的解釋! …另外,我得說,您的高興很棒! ?”
Being nice doesn’t feel like work to me (though I get that it can for others) but either way, it pays off. It lets me have deeper conversations with my users. Discussing their suggestions often reveals other ideas they have but didn’t think to bring up. I even had a video call with a user halfway across the world!
變得友善對我來說并不意味著工作(盡管我認為這對其他人也可以),但是無論哪種方式,它都會有所回報。 它使我可以與用戶進行更深入的對話。 討論他們的建議通常會揭示出他們有其他想法,但并沒有想到提出。 我什至與世界各地的用戶進行了視頻通話!
Being nice also lets me ask users unsolicited questions, which at first I was afraid to do. Maybe they’d be annoyed that I’m bothering them? That fear was silly. People like sharing their opinions!
友好也讓我問用戶一些自發的問題,起初我不敢這樣做。 也許我會打擾他們,讓他們煩惱? 這種恐懼是愚蠢的。 人們喜歡分享意見!
第3課:用戶可以在任何地方 (Lesson 3: Users can be anywhere)
I’m not sure why I expected this (other than my apparent geocentrism) but I’d assumed my users would all live in my home country. Not even close! My 17 users don’t even all live in countries where my native language is particularly common. (And why should they?)
我不確定為什么會這樣(除了明顯的地理中心論之外),但是我假設我的用戶都將生活在我的祖國。 差遠了! 我的17個用戶甚至都沒有生活在母語特別普遍的國家/地區。 (為什么呢?)
My 17 users live on four different continents.
我的17個用戶居住在四個不同的大陸 。
That humbling fact boggles my mind.
那令人毛骨悚然的事實令我震驚。
第4課:賺錢很難 (Lesson 4: Making money is hard)
I was spurred by success stories of open source projects being sustained by donors. So I recently put up a few donation badges onto the project README. I’d love to be able to spend more time with friends, and even a small amount of money is a clear signal that it’s worth my time.
捐助者支持的開源項目的成功故事使我大受鼓舞。 所以我最近在項目README上貼了一些捐贈徽章 。 我希望能夠與friends一起度過更多的時間,即使少量的錢也明確表明這是值得的。
So how many donations has GitHub’s most-starred human-readable project received? Exactly zero. (And honestly, I’m not sure how to change that.) It is, I admit, a little discouraging.
那么,GitHub最受歡迎的human-readable項目收到了多少捐款? 完全為零。 (老實說,我不確定該如何更改。)我承認,這有點令人沮喪。
Still, if I was in it for the money I wouldn’t have spent so much time building, well, this. And donations are just one way to contribute. If you give me as much feedback, love, and help as my 17 users, you don’t need to give me a cent.
不過,如果我愿意花錢,我不會花太多時間來建造這個 。 捐贈只是一種捐款方式。 如果您給我的反饋,愛心和幫助與我的17個用戶一樣多,那么您就不必給我一分錢。
翻譯自: https://www.freecodecamp.org/news/learning-from-a-whopping-17-users-50ddfe748c26/
32位系統能夠識別多達內存
總結
以上是生活随笔為你收集整理的32位系统能够识别多达内存_向多达17位用户学习的全部內容,希望文章能夠幫你解決所遇到的問題。
                            
                        - 上一篇: 迅捷画图怎样画思维导图、流程图
 - 下一篇: 饮品自动贩卖机系统 c语言,自动贩卖机控