[Sparkyte]

I agree with this, but when working with a team I always feel motivated to see the progression made. Rarely do solo developers work well with others and rarely do collaborative developers work well by themselves. It really depends on the dynamic of the environment and the goal of the team.

[hinkley]

Which is a pretty pickle when you’re trying to hire devs. A candidate with a large GitHub repo may actually not be the team player you’re looking for.

[Rinzler89]

>a large GitHub repo

I feel like in SW, impact and quality should be a lot more valuable than quantity of repos/apps you write. A few lines of code that fix a Gnome/KDE/$BIG_FOSS_PROJECT bug would be a lot more valuable in my book, than say another one in the millionth pile of JS note taking apps, or a repo full of "Baby's first Rust app"

[hinkley]

I spent 1-3 hours every other Friday for six months writing a three line monkey patch to fix a (lack of) clipping bug in a drag and drop library that wasn't taking PRs because they were going to rewrite everything (and were 18 months into a 1 year rewrite and only half done).

I'm not going to name names but it rhymes with jQuery UI.

The best I could do was attach a code snipped to a bug report. I've gone back and forth about whether that should count as participation but for that case it's the most calendar time I've ever put into a line of code and you're goddamned right I want to count it.

[Rinzler89]

Based