my guess is the software equivalent is the architect role - basically someone high level that doesn’t code much but does design the overall way that systems interact (or, to put it redundantly, designs the architecture of the full system)

however i don’t know if this term is en vogue as much anymore except for very large scale businesses (i would bet money that banks employ architects, for example)

When I read the post I was initially focused on google search but man….if gmail were to die, the pile-on effects would be seriously catastrophic and it would take a very long time for things to stabilize again. It’s not just personal emails that are handled by gmail - their corporate offerings are used by a ton of companies, and there are plenty of school districts as well that rely on it for their email (and thus associated logins). If you’ve ever worked near education, you know what a cluster that would be as all the IT departments scrambled to figure out who would be responsible for a migration.

I don’t really see it happening, but it’s very scary to think about what would happen if gmail were to fall.

Hadn’t heard of this one, but it looks great! There’s definitely something to be said about the opportunity opening here for a continued evolution of how we want social media itself structured.

Lemmy is pretty reddit-esque and mastodon very twitter-like, squabbles looks to be trying a mix of the two, so I hope creative people continue to evolve how our conversations are structured going forward (in addition to the advantages the fediverse is already delivering on)

so…proof that a hot dog isn’t a sandwich but now….it’s a TACO??!?!?

This is the best solution I’ve come up with, but it’s going to result in a lot of duplicate posts (and the comments will still be fragmented). I’m following several technology communities and a lot of the posts are posted to each of these communities individually. This has always been my concern with federation (along with server health/durability)

It’s not the worst result, but I don’t know how well it will be received by more mainstream users. You also then have to solve discoverability of these “groups/metas”, and THAT has to be hosted on a federated instance so you could still end up with users confused on whether they should follow beehaws tech group or someone else’s….and round and round we go lol

(Just to be clear - I’m not against federation, it’s just such a starkly different model than the normal web that we really have to adjust our mindset and find truly novel solutions or adjust our expectations)