4 ms·
Boycotts/strikes* only work if most or nearly all people participate, because you'll only participate if you're pretty sure nearly everyone else is too. While i
by crazygringo 3y ago
Boycotts/strikes* only work if most or nearly all people participate, because you'll only participate if you're pretty sure nearly everyone else is too. While if this blogpost merely gets 0.1% of developers to strike... Apple couldn't care less.
I think this developer strike is a great idea, but launching it as a single person's call to action (Jeff Johnson's) is not generally going to be effective in changing behavior.
What an organizer needs to do is to first personally contact somewhere between 50-200 other major, known, respected developers and get them to co-sign a joint letter which then gets published, so everyone can see this is a serious strike by people who know what they're doing -- not just one person's wish. It needs to get covered in all the major tech publications, so both Apple and all developers see it as well.
And then the letter needes to not lay out a list of all of the complaints, but rather the specific, verifiable actions Apple needs to take in order to end the strike, so this isn't some open-ended thing. And they need to be realistic actions as well, not wishful thinking -- signs of progress with dates and milestones, not fix-all-the-things-immediately.
If you're going to do a strike, you need to actually organize it. Writing a blog post that merely "encourage[s] all Apple developers to join me" is not the same as organizing. And generally speaking, writing a blog post claiming that you're striking isn't going to get anybody else to magically organize it for you.
* As the author indicates lower in the article, it's more of a strike than a boycott since it's stopping providing free labor rather than stopping purchases, so I'll refer to it as a strike
- jshier 3y agoFundamentally, such a strike assumes Apple cares about the free reports they get from their developers. I'm not sure that's true. And even if it is, it's not like they don't have enough other reports or features to work on, so the loss of all outside bug reporting probably wouldn't affect them at all.
- jfim 3y agoThere might even be a middle manager that gets to say "external bug reports are 30% down YoY, our quality efforts worked out."
- lapcat 3y agoI'm already fairly well-known in the Apple developer community and received a lot of positive feedback on social media before posting the announcement, but I do think you're overestimating the amount of effort that I and other developers are willing to put into getting Feedback Assistant improved. This is not a fight for higher income or something of that obvious importance. The beauty of the strike is that steps 1-3 at the beginning are low effort from everyone, which allows everyone to easily join if they choose. As I said at the end of the article, one of the goals of the strike is to prove to ourselves that we don't really need Feedback Assistant, we've got little to lose, it's not essential to us that we participate in the bug reporting system, and we can just walk away. The strike is not a win-at-all-costs, fight-to-the-death scenario. Feedback Assistant, no matter how unrelentingly terrible and annoying, is or at least should be rather low on our list of professional priorities. I think this attitude gives us leverage over Apple. We're only volunteers walking away from a crappy volunteering "opportunity", whereas Apple relies on our free labor for its commercial products and would have to actually hire additional staff and pay them in order to replace our QA work.
- saagarjha 3y agoMight be worth having a public list of people who've "signed" your boycott, though.
- lapcat 3y agoI've considered that, but I have some concerns about the idea. I'm worried about personally getting overwhelmed by emails and messages on social media. The more successful the boycott, the more I become swamped. :-) Also, I think many developers have a fear of reprisal, whether that's empirically justified or not. My understanding is that there's now actually some degree of anonymity in Feedback Assistant, after changes were made in recent years for GDPR compliance? In any case, putting your name in public is a bigger step than simply boycotting, and I'm aiming for maximum participation. I've put my own name on this, and some cranks have even speculated that I might get kicked out of the developer program for it, which I doubt, because it would make me a martyr and kill my popular software — not to mention that dropping several 0days on Apple didn't get me kicked out — but I suppose that's always a possibility. In general, I don't think that petitions are particularly useful. I'm more in favor of action (though in this specific case, the boycott is technically inaction).
- ncallaway 3y ago> because you'll only participate if you're pretty sure nearly everyone else is too. Definitely true for traditional paid labor, but this isn’t that. Nobody is leaving their paycheck behind if they stop using Feedback Assistant. Since the costs to participating in this strike are very low (for most people, participating in the strike is probably a lower cost than not participating in it), I could see a path to building up to an impactful strike over time, in a way that’s not possible in a traditional labor dispute.
- schappim 3y agoSure Apple could be indifferent to a small percentage of people boycotting their process, but the Public Relations (PR) and Comms group is extremely averse to negative commentary. I'd imagine there are some emails flying around right now...