Re: [Outreachy] Blog Post Submission

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Dec 18, 2020, 11:41 UTC
Message-ID: <5fdc958199da4_104e15208fe@natae.notmuch>
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