Indeed, sports and entertainment unions probably aren't a good comparison for tech. Other professions like accounting, medicine, law, and engineering might have better examples of cost/benefit, though it's hard to think of another professional industry with the ridiculous level of functional duplication (a million frameworks for everything) in tech.

There's definitely challenges in not turning it into a protectionist thing, but done well I don't think it's a bad thing.

Mentorship programs that bypass the degree requirement are less common, but I made it through without a degree. I would love to see more of them, and more companies willing to help with work-study, but the challenges of that approach are real and may not have an easy solution.

> First, the film unions provide useful benefits (like reasonably-priced health insurance), so most professional actors want to be part of the union. Second, union members are prohibited from working on non-union productions. Additionally, most well-known actors are union members. This gives a strong incentive for a production to be a union production. Third, union productions are prohibited from hiring more than a token number of non-union actors (unless they pay a fine to the union). This gives a strong incentive for productions to only use union talent (which also gives actors another reason to want to be a union member).

Note that by observing important differences between the film and software industries, I'm not arguing that unions couldn't work for the software industry. I suspect this is why I've been downvoted.

I get your point, but I was just using SAG to give a concrete example. The rules are broadly similar for the other film industry unions as well, with similar effects (and other roles have "industry-famous" if not "mom and dad famous" talent).

I suspect you'd get similar dynamics if, for example, a large cohort of the staff/principle engineers plus a bunch of senior engineers in the valley joined the SWE Local 16384. It's probably not necessary that your mom and dad have heard of them.

To be quite clear (and likely this was your point, in which case I agree), if the film/tv unions excluded actors, the effect would be pretty comparable. My friends and family aren't going to see a film because Joe The Sound Guy worked on it just like they aren't going to buy an app just because Collin The SRE worked on it (no matter how famous Joe and Collin are in their respective industries).

Twitter is full of them.

> Twitter is full of them.

Name one.

In general, I try to avoid Twitter though because the software community there is very self-congratulatory and a bit toxic elitist. Not to mention if you aren't a front-end dev good luck being treated like you are a real engineer.

Is this a typo? I was under the impression that frontend devs were near the bottom of the dev pecking order. At least that's been my experience wherever I've worked and in things I've read.

FWIW, frontend is a suite of hard problems which are distinct from the problems we face on the backend but no less challenging. Frontend development today certainly seems a lot less rigorous than backend development in the sense that there seem to be fewer best-practices and more of an embrace of a certain "cowboy/ninja/move-fast-and-break-things" chaotic ethic (engineers from other disciplines would balk at the characterization of backend engineering as 'rigorous', but I think it's fair to say that we devote more rigor to it than frontend development). I think this is largely due to our industry deciding that frontend was a low-skill position and thus putting most of our most junior engineers there to sort it out, and then we on the backend mock them for churning out new frameworks and tools in a desperate effort to bring some order to the chaos.

My personal guess is it's because front-end people can demo things easier.

I think amongst larger dev circles, it's probably generally true that front-end are considered towards the bottom. I think some front-end developers, like Dan Abramov, show that that's a bit unfounded.