Notices by Anil (anildash@mastodon.cloud)

(I'm not trying to be obtuse, it's just that writing out the whole problem requires a lot of time, energy and effort because there's a lot of context-setting to do, and then you have to budget time for dealing with the wave of bullshit that follows anytime you level accurate criticisms at tech owned by silicon valley tycoons.)

replies are evenly split between “we’ve seen this pattern play out so many times!” and “wait, what’s wrong with it?”

I despair about how many talented people are using Substack when we know exactly where that whole mess is headed.

Hey, everyone who follows me who is hacking on somethigna round ActivityPub/fediverse — please reply here and share a link to your app/GitHub/Glitch! Would love to show off all the creativity that's happening right now. (And please boost so your friends can share their projects too.)

First, as background context, when I took over as CEO of Fog Creek (later Glitch), the company had long claimed to offer innovative benefits; in the context of the turn of the century, they likely *were* more generous in offering complete coverage of many kinds of care. But the state of the art in benefits in the tech industry advanced and having a bespoke benefits system made every common task harder, slower, more complicated and nonstandard.

This thread is from a larger-context conversation about why some tech workers choose to work for giants like Google; Justin details their experience in systemic failures with healthcare and benefits at a startup. Since I was CEO of that startup, it’s worth sharing the insights I got into how these systems fail, in hopes that other workers (and well-intentioned managers) can avoid replicating these problems and sparing people pain. https://twitter.com/modernserf/status/1610702219149557762

That’s the abstract description. In real terms, it meant that the lived experience of our workers was that their benefits were *worse* while we were putting in more time (and cost) to try to make them better. And if things are worse for you while a company says they’re trying to do better, most people don’t care if the cause is dishonesty or incompetence. It just sucks. It causes real pain.

In this particular case, while I knew there were gaps, I underestimated how a small (but quickly-growing) organization could mask these failures. This was often due to miscommunication, but to be sure there were people who actively obscured the ways the system was failing workers because they question the norms of tech industry benefits. This kind of risk will increase hugely in the industry as the tech execs become more pointedly anti-worker in the Musk Twitter era.

The answer can’t just be “go to big tech companies with world-class HR systems”, because those companies routinely harm vulnerable workers in other ways, and their leadership is being taken over by increasingly radicalized extremist execs. One way of improving things in other orgs may be if we can share insights into how to make things run better. I have a few lessons I’ve learned, and would encourage people to talk to those who’ve been affected by these failures, in order to learn more.

I wanted to share this story because I think many of us who care about the human impact of working in the tech industry intuitively know that the vulnerable get hurt by our systems. We hear the anecdotes from those we care about & we understand their stories. But few in positions of power can articulate _how_ they fail, even though there are (for now) managers & execs who genuinely do want to get it right. Many workers are going to have to reckon with similar concerns in the near term.

The most pertinent thing that amplified the challenge here is that our workforce got significantly more diverse *while* we were trying to improve these systems. What had primarily been a fairly homogenous old-school tech company over the prior 15 years was quickly a lot more inclusive, but that exposed all the weak points around key benefits like health care even more acutely. The most vulnerable bore the worst brunt. Small companies in particular have atrociously poor choices and little power.

For workers, a few bits of advice:
* Culture of leadership and the values of the organization _do_ matter, but always verify with the actual experience of the people working on the specific team you’ll be joining
* We often say “HR is not your friend” to workers who are having issues at work, and that’s valid, but it’s good to understand _why_ that is true in so many orgs.
* Even if an organization _is_ addressing problems, make your decisions about your career based on your current real needs.

A few lessons for managers:
* HR systems are optimized for convenience of management, meaning they shortchange marginalized workers _by default_
* HR culture is defined by people who _like_ those systems, and now often led by execs who resent their own workers, so resistance to improvements is often deep & pervasive
* One of the worst mistakes I’ve ever made as a leader was speaking to how we *wanted* a system to serve our workers without fiercely interrogating the risk of masked problems

I’m writing a little guide for organizations (companies, government agencies, non-profits) thinking about the fediverse. What do you want decision-makers at those institutions to know? Or what questions do you have?

Elves absolutely *fed up* right now at dealing with two-factor auth for the North Pole Jira instance.

If you’ve got friends who are still on Twitter, we’ve got a free way for you to make your own links page, now that Twitter is blocking linking to your own social media pages. You can even add your own domain name; it would be hard for Musk to block the entire internet. https://glitch.com/glitch-in-bio

mods asleep, post journalism

I love whatever metadata failure causes this to be the link preview for any time a TechCrunch story is shared. BREAKING NEWS ABOUT THE YAHOO FAMILY OF BRANDS.

Okay, so looks like the instance I'm on hasn't been handling misuse well and is going to get defederated from some other servers. Soooo, what instance do y'all think I should move to? And is there any history/experience of anyone with this size a network migrating instances that I could learn from?

Is there a service that will host a single Mastodon account for me (not an entire instance) but let me alias it to my own domain? I don't want to run an instance, but I would like to control my address/handle.