4 ms·

> None of their engineering staff have anything visible on their GitHub accounts - not even a project that they got two lines into and then threw away, which I

> None of their engineering staff have anything visible on their GitHub accounts - not even a project that they got two lines into and then threw away, which I honestly accept as a sign of baseline competence these days As much as I want to contribute to FOSS I have kids to take care of, and want to parent. While I’m not star dev, I am certainly competent.

gambiting 2y ago
I've been a C++ dev for more than a decade and every single project I've ever worked on has been confidential and closed source, there is nothing for me to put on GitHub, other than personal stuff but then why would I ever do that? My hobby projects don't reflect my professional standards for coding, if they did they would no longer be hobby projects :P
- add-sub-mul-div 2y ago
  Same with me, I have active projects on github but the repos are private and bespoke, very specific to my environment. It's not performative activity to make my profile look good, I actually use the stuff.
  - mariusor 2y ago
    And are you sure your use cases don't match others', or are you not willing to share your work for free with them? Why would it be performative to make it public?
    - Nevermark 2y ago
      Their point is they don’t think their project is suitable to be public, so making it so would be performative.
      - mariusor 2y ago
        I got that, but my question was "why?" on both accounts.
        trimethylpurine 2y ago
        I can think of a lot of answers. 1. You don't care what others think. 2. GitHub is trying to be social media. 3. Lots of code is useless because it serves as some specific compatibly for an ad hoc process that someone a long time ago automated wrong. 4. Publishing code to GitHub requires effort in making it look readable to someone who isn't doing what you're doing. 5. If you don't do #4, you'll clutter up search results for others, which is literally a disservice to open source. Also, public repos are for getting lots of people to work together for the good of the project's utility. Making them public for others' plaudits is literally the worst thing to happen to open source development. Save the vanity for Facebook. We're trying to solve problems here.
        mariusor 2y ago
        > Save the vanity for Facebook. We're trying to solve problems here. Are you sure that's what you want to say to me as a closing comment? That's a terrible conclusion, and it paints you in a very unflattering light.
        trimethylpurine 2y ago
        How so? Are you maybe adding some specific interpretation to my statement that would make it about you? Try reading it like this: We can save the vanity for Facebook... Or like this: I'd save the vanity for Facebook... Or: Job seekers should save the vanity for Facebook... I'm guessing you filled in the blank like this: Mariusor, you need to save the vanity for Facebook... Always assume the best intentions. Hard to do in text. Let me know if I'm missing your meaning.

gambiting 2y ago

I've been a C++ dev for more than a decade and every single project I've ever worked on has been confidential and closed source, there is nothing for me to put on GitHub, other than personal stuff but then why would I ever do that? My hobby projects don't reflect my professional standards for coding, if they did they would no longer be hobby projects :P

add-sub-mul-div 2y ago
Same with me, I have active projects on github but the repos are private and bespoke, very specific to my environment. It's not performative activity to make my profile look good, I actually use the stuff.
- mariusor 2y ago
  And are you sure your use cases don't match others', or are you not willing to share your work for free with them? Why would it be performative to make it public?
  - Nevermark 2y ago
    Their point is they don’t think their project is suitable to be public, so making it so would be performative.
    - mariusor 2y ago
      I got that, but my question was "why?" on both accounts.
      - trimethylpurine 2y ago
        I can think of a lot of answers. 1. You don't care what others think. 2. GitHub is trying to be social media. 3. Lots of code is useless because it serves as some specific compatibly for an ad hoc process that someone a long time ago automated wrong. 4. Publishing code to GitHub requires effort in making it look readable to someone who isn't doing what you're doing. 5. If you don't do #4, you'll clutter up search results for others, which is literally a disservice to open source. Also, public repos are for getting lots of people to work together for the good of the project's utility. Making them public for others' plaudits is literally the worst thing to happen to open source development. Save the vanity for Facebook. We're trying to solve problems here.
        mariusor 2y ago
        > Save the vanity for Facebook. We're trying to solve problems here. Are you sure that's what you want to say to me as a closing comment? That's a terrible conclusion, and it paints you in a very unflattering light.
        trimethylpurine 2y ago
        How so? Are you maybe adding some specific interpretation to my statement that would make it about you? Try reading it like this: We can save the vanity for Facebook... Or like this: I'd save the vanity for Facebook... Or: Job seekers should save the vanity for Facebook... I'm guessing you filled in the blank like this: Mariusor, you need to save the vanity for Facebook... Always assume the best intentions. Hard to do in text. Let me know if I'm missing your meaning.