> The author makes a valid point, however the pushback against using OSS as an important hiring signal, is that most people are not privileged with enough spare time to work on OSS outside of their day job.

Like most people I know, I use open source software in my day-to-day job even though I work in a company who provides proprietary software and services.

That means that when I do encounter errors or bugs in those open source components and libraries I can make the choice to either write workarounds locally in my code, or I can choose to submit patches back upstream.

That’s not a matter of privilege. That’s a matter of choice.

I also think it’s reflective of a developer’s attitude: does he prefer things done “properly”, or will he just hack together something which works? Will he share his solutions or not?