Live data from Hacker News

The Few, the Tired, the Open Source Coders

wired.com

171–173 of 173 posts

Re: The Few, the Tired, the Open Source Coders

#171

Earlier quoted context omitted.

Which sounds like your signal is "cogently explain something interesting about their side project" and not simply "did something worthwhile for free".

Sure. I suppose that if you go deep enough, my signal is "will write good code here", which is suggested by "can write good code", which is suggested by "has written good code" and "wishes to write good code", which is suggested by..."did a side project" or "doesn't only write code when someone is standing there to pay them for it" or Everything in an interview process is an approximation and guess.

I agree that it makes business sense to shift risk to the potential employee.

My observation is that this biases the employment pool toward those who have extra money and time to work for no income.

Those who have to work two jobs, or spend their free time taking care of chronically ill family, or are otherwise prevented from being able to work for free, have less of a chance, even if they are otherwise well-qualified.

I have no suggestions for what to change, only my original comment that "passion" seems altogether too often a code phrase for something other than "loves to program."

Re: The Few, the Tired, the Open Source Coders

#172
post #19

Earlier quoted context omitted.

At every company I've worked I've lobbied for us to make donations to open source projects we depend on. Every single time it quietly dies in legal. There must be a better way.

OSS could use similar licensing as some SaaS where it's free for personal use or commercial use up to certain limits and then you have to pay. This would ensure developers can use it freely but at some time a company would have to either pay it or ditch it. However I see two issues with this model: - the community will shit on it like it's not real OSS - big companies will start banning the use of such licenses The o…

That is the AGPL (free)/Commercial(paid) dual license. Its pretty popular.

Re: The Few, the Tired, the Open Source Coders

#173

Earlier quoted context omitted.

>because they only solve the problem that the PR submitter needs solved right now. This is something that can lead to angry interactions between maintainers and pull request raisers. Never mind adding technical debt, pull requests can outright break uses cases they don't care about in order to implement the single use case they do care about. raiser: "Merge my PR. It fixes this issue." maintainer: "It fixes this sing…

A good test strategy would fix the problem. "Your PR fails all these tests, so can you make them all work before submitting the request?"

Definitely. You just need to keep an eye out for people removing failing tests because they think they are irrelevant :|
Post reply on HN