From: Felipe Contreras <felipe.contreras@gmail.com>
To: Sangeeta <sangunb09@gmail.com>, Git List <git@vger.kernel.org>
Cc: Christian Couder <christian.couder@gmail.com>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Subject: Re: [Outreachy] Blog Post Submission
Date: Fri, 18 Dec 2020 05:41:53 -0600 [thread overview]
Message-ID: <5fdc958199da4_104e15208fe@natae.notmuch> (raw)
In-Reply-To: <CAHjREB7UonP7TPCd9dvXLX2ho+rJP07JM8nk33AYj9K=Mi7EYw@mail.gmail.com>
Hello Sangeeta,
Sangeeta wrote:
> Here's my second blog post on "everybody struggles".
> https://sangu09.github.io/everybody-struggles/
>
> Do give it a read let me know if you have any suggestions.
Just a few obsevations.
1. Don't feel bad about the lack of code. In my professional experience
I've seen situations where a developer spent one month working on a
problem, and the solution is *one line* of code. It's not the amount
of code that matters; it's the amount of effort that was put into
it, and in fact; once you have a solution that works, putting more
work can make it cleaner (less code), which is appreciated.
2. There is a concept called "the curse of knowledge" [1] that everybody
who is an expert in an area suffers. Certainly many old-timers in
Git development do.
That's why newcomers are always appreciated; fresh eyes usually spot
issues many of us don't. You have a unique vantage point, so it's
good that you document your struggles; they may give us an insight
that otherwise we would be blind of.
3. Once you have some code you would like to bounce off on Git
developers, you might want to try git-related [2] (that's my tool
but there are others). For example, I just did this:
git related master..mergetool
To find people to CC regarding the branch I'm currently working on
(they have worked on the lines of code I'm changing).
That's it, I hope you find that useful.
Cheers.
[1] https://en.wikipedia.org/wiki/Curse_of_knowledge
[2] https://github.com/felipec/git-related
--
Felipe Contreras
next prev parent reply other threads:[~2020-12-18 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 6:29 [Outreachy] Blog Post Submission Sangeeta
[not found] ` <CAP8UFD2AOaPC+7+qcJHQ4+Q5=dhY7ReNbRfJQ=HCS6=4bTPuVA@mail.gmail.com>
[not found] ` <CAHjREB6ynLFW46C9s8D_nvUpavkugo7syegGuvCMdnfVNiZ+0Q@mail.gmail.com>
[not found] ` <3bd5cef1-cda7-5118-07ac-a2f91cc80371@gmail.com>
2020-12-18 10:12 ` Sangeeta
2020-12-18 11:41 ` Felipe Contreras [this message]
2021-01-08 16:54 ` Sangeeta
2021-01-26 7:31 ` Sangeeta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5fdc958199da4_104e15208fe@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--cc=sangunb09@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).