3 ms·
> I don't know whether something like that would work in the software industry, but it seems at least plausible to me that it could benefit everyone who is curr
by throwaway894345 6y ago
> I don't know whether something like that would work in the software industry, but it seems at least plausible to me that it could benefit everyone who is currently employed in tech (at the expense of future potential tech employees).
I doubt it, if only because actors are hired in large part due to their celebrity. There are no celebrity SREs (at best they have some cache in the software/SRE community, but not in the general public).
- minimuffins 6y agoMost people in film and TV unions aren't actors.
- throwaway894345 6y agoI was responding to a particular comment that was talking about the mechanics of these entertainment unions with respect to actors specifically: > 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.
- labcomputer 6y ago> I was responding to a particular comment that was talking about the mechanics of these entertainment unions with respect to actors specifically: 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.
- throwaway894345 6y agoI guess I'm saying that the celebrity nature of actors is a confounding factor. It's not that these actors are merely celebrities among the film industry, but your mom and dad and friends actually have heard of them and their presence in a film is going to influence whether or not people turn out to see the film. You can get the most famous programmers together to build a product, and no one is going to buy that product on the basis of those programmers' celebrity unless some segment of the software industry is the target audience for that product. 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).
- bradleyjg 6y agoThe other unions are even harder to get into. At least occasionally a casting director will insist on a non-SAG actor. Many of the other unions are effectively impossible to get into except via their apprenticeship programs. Similar to the physician cartel ...
- nitrogen 6y agoSimilar to the physician cartel ... 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.
- ryanbrunner 6y agoHonestly, an apprenticeship model is probably fairly well suited for a lot of types of software development. In my mind it's superior to a CS degree or bootcamp in terms of teaching practical skills. There's definitely challenges in not turning it into a protectionist thing, but done well I don't think it's a bad thing.
- GauntletWizard 6y agoMentorship programs exist at most major companies, and new software engineers are not allowed to commit code willy-nilly - They pass code review, and less senior members of a team typically have more careful code review applied to their commits than more senior ones. 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.
- sitkack 6y ago> There are no celebrity SRE Twitter is full of them.
- throwaway894345 6y ago>> There are no celebrity SREs (at best they have some cache in the software/SRE community, but not in the general public). > Twitter is full of them. Name one.
- ar_lan 6y agoKelsey Hightower comes to mind. 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.
- throwaway894345 6y agoHightower's celebrity does not extend to the general public. I don't think he even has a wikipedia page, which is certainly the low water mark for celebrity.
- kelnos 6y ago> 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.
- throwaway894345 6y agoI think you're reading it wrong; the phrasing as I read it is consistent with your "frontend devs at the bottom of the pecking order" perception. The original quote says "good luck being treated like a real engineer" implying that frontend devs are treated so poorly they aren't even considered to be real engineers. 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.