Comment by impropsters
5 years ago
Sometimes it feels like software development has devolved into a sea of posturing and marketing oneself. It's faintly depressing to see reminders of that trend which are as stark as this.
It's a fitting allegory, though. This contest has used free T-shirts to solicit open-source contributions in the same way that the industry has used high salaries to solicit creative and impactful contributions.
Now imagine that you're trying to fill a position, and these pull requests are analogous to candidate interviews. You might start to have some sympathy for people who believe that we need some sort of professional certification for the trade.
It's unfortunate considering the democratizing promise of low-cost computing, but how else can you effectively deal with this "market for lemons" caused by large swaths of people acting in blatant bad faith?
When seeming is taken for being, being becomes seeming. \
When nothing is taken for something, something becomes nothing.
> Sometimes it feels like software development has devolved into a sea of posturing and marketing oneself.
I've been saying it for a long time, but the reason that this and other problems (like high developer burnout) seem like especially bad problems that the world of "software development" is facing is primarily because they're especially bad in the GitHub culture (and as a consequence of that culture), and the developers who are experiencing the worst of it are part of that community. Ditch the 'Hub, its userbase, and what is considered "best practice" there, and then many of these problems get dialed back a lot.
Much like follower counts on other social media sites, GitHub's contribution graph and profile timeline should have never been public. They should have been neat features of your personal dashboard that you alone are able to see when you're signed in—providing some form of encouragement à la the Seinfeld hack and to help you manage your work—but not for others' eyes. The gamification of "social" leads to degenerative behavioral patterns.
> Ditch the 'Hub, its userbase, and what is considered "best practice" there, and then many of these problems get dialed back a lot.
This sounds like "Without GitHub you will get less spam", which is probably true, but I think the reason is not "github is bad", it's: Less people will find your project.
Maybe that's a worthwhile trade-off, but it's very different from "all will be better without Github"
Less people finding your project could be an improvement if the people you loose are the onse that just create the kind of spam contributions mentioned in the article. You don't need GitHib for useful software to become popular, it is just one channel. And you definitely don't need the gamified bullshit like total stars on your profile.
1 reply →
> Less people will find your project
That is false. Firstly, even if your project is not hosted on github, clones of it will appear on github anyway.
Secondly, planting yourself in the middle of a vast ocean of garbage is not a good strategy for being found. You might be thinking of the Github of twelve years ago.
> Maybe that's a worthwhile trade-off, but it's very different from "all will be better without Github"
Making up quotes is not cool; those aren't my words, and that's not my position, so I'm not going to be gulled into defending it or kept from calling attention to what amounts to a sleight of hand here, even if it wasn't intentional.
(And this really chafes, because after I wrote what I meant, I even revised it to pre-empt[1] getting sucked into a discussion where someone responds to the wrong reading—specifically trying to avoid things like this. But when people don't even respect the constraint of sticking to others' actual words and instead conjure up other words that make for a more convenient world[2] to operate in, then there's almost nothing that can be done.)
> This sounds like "Without GitHub you will get less spam"
Well, it shouldn't; that's reductive.
If the bad stuff that arises from GitHub, its culture, and its practices were proportionate to its size, that would be one thing. (But also not itself a good reason not to consider ditching it—just like it's not obviously true that it would be a good idea to use Windows because the risk of malware is rational given its size as a target.) What's bad about GitHub, though, might in fact be disproportionate to its size—and in some cases, especially with respect to the practices that get promoted in that world, are things that are bad irrespective of GitHub's size.
1. https://pchiusano.github.io/2014-10-11/defensive-writing.htm...
2. https://wiki.lesswrong.com/wiki/Least_convenient_possible_wo...
2 replies →
The effect of those things on github are minuscule comparing to that of medium and twitter. I never even looked at anyone else's github profile. Most of the time it's medium and twitter that take me to their projects and I only evaluate the project with the context of who they are on twitter or what they've written on medium.
I've seen quite a few people market themselves by saying how many stars they have on github, and some even started putting something like "If you find this useful, please star it" in their documentation. It's not quite "like, share & subscribe" yet, but it's on the way. Any public metric will be optimized for, I guess.
2 replies →
> Most of the time it's medium and twitter that take me to their projects and I only evaluate the project with the context of who they are on twitter or what they've written on medium.
Please revisit my original comment. When I wrote it, I put some effort into qualifying things to make it clear that I'm not talking about just what happens on GitHub on the site. I referred to its culture. The things you just described are part of that culture, and very notable elements of it.
5 replies →
I’d argue getting a shirt for some PRs is better than the status quo, where you get nothing for a PR.
Which just goes to show how bad the status quo is.
> where you get nothing for a PR
You already got payment up front: software that the author(s) have made available to you for free.
You get payment by the author spending time to review your changes.
You also get payment afterward: free maintenance for your pet feature. (Not guaranteed of course but generally the case.)
“But we obtain the puzzling result that, when rewarded, volunteers work less. These findings are in line with a large literature in social psychology emphasizing that external rewards can undermine the intrinsic motivation for an activity.”
Be very careful assuming that a payment motivates open source developers. If you offered to help me do something for an hour for whatever internal motivation you might have, and afterwards I offer you $5 for your time, you would likely be demotivated.
If you offered to help me do something for an hour for whatever internal motivation you might have, and afterwards I offer you $5 for your time, you would likely be demotivated.
On the other hand if you offered to buy them a beer or a coffee it would probably be very motivating. I'm not sure why this is. Maybe cash just feels lazy and impersonal, so the amount being offered has to be big enough to counter that feeling.
3 replies →
That quote might be misleading:
"Volunteer work is an increasingly large, yet ill-understood sector of the economy. We show that monetary rewards undermine the intrinsic motivation of volunteers."
-- https://ideas.repec.org/p/zur/iewwpx/007.html
The earlier sentence make it clear they are talking about monetary rewards specifically, not any kind of reward. A t-shirt might notionally have a $ value, but it is not a monetary reward. Plus, the nature of a branded t-shirt has an obvious team-participation / prestige value.
If rewards demotivate people, we should also avoid positive recognition, or praise, which is a form of reward; of course this is unintuitive, so I assume monetary rewards are a special case.
1 reply →
I actually would be very motivated. From the perspective of a contributor the worst thing that can happen is that their patch gets rejected or ignored. If you get paid for something it means someone actually wants your contribution. It's less likely to be ignored or rejected outright.
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.511....
here is the work that you cited if i am not wrong.
That's missing the point a bit.
Good PRs are valuable, but require lots of work. Spam is not valuable, but it also does not require basically any work.
Hacktoberfest equally rewards both good PRs and spam equally. With those incentives, what are people logically going to produce?
On the other hand, what kind of people are going to logically participate in an event where the reward is a Hacktober branded T-shirt? What are their likely motivations?
1 reply →
I submitted very few PRs to open source projects. I usually submit bug reports.
In both cases I get that what I care about gets into the project. It's enough for me.
My pet theory is that 'marketing oneself' trend is a sign of oversaturation (and forthcoming commoditisation).
This happen a few years back in UI design when designers started to put more work into presentation of projects than projects themselves.
> When seeming is taken for being, being becomes seeming
This quote can be applied to organizations on the wane.
> devolved into a sea of posturing and marketing oneself
Don't think it's devolved at all this has been the norm from the 80's onwards (perhaps earlier).
Look at how fractured open source is today and the sort of egos that come with it everywhere you look. While the points made in this article are valid, it's great that someone is incentivising people to interact with various projects rather than do their own thing rather than climb blindly up the same treacherous mountains others have done long ago.
Hey, also why not rewrite it in rust :)
Being a contrarian is easy, fixing these well acknowledged problems is hard.