It is true that manufacturing reduced the time spent making clothing, but a) a lot that time weren't really career jobs, but women spending their time spinning and selling the results for a small amount to supplement what the household could not grow, and b) people willingly decamped for cities to work in the factories. (You can still see some of this process in China, with the migrant workers; they could continue subsistence farming, but they choose not to.) People materially got richer, as they moved up from subsistence farming. I think I spend a few hours a year to get the money to buy clothes, which I think is a good deal. (I spend longer looking for clothes I want, which I hate doing, but is quite the luxury historically.)
Many women did this as their full time job. Spinsters became a viable option for women without a family or land to be self sufficient. Most women used to multi task a drop spindle as they went about their day. A spinning wheel was a massive improvement per hour but the lack of portability made it an independent job. As specialists could now make way more thread which enabled the transport of large quantities of relatively high value goods to one location for economies of scale. Which could then benefit from a positive feedback loop.
> manufacturing reduced the time spent making clothing
Anyway, my point was factories came late in the process. Automation of thread making occurred at several stages before there was enough supply excess supply for any kind of scale. Without that factories could only really automate less than 5% of the total labor for making clothing.
So sure, eventually automation came for those home spinners, but that happened after the natural benefits from economies of scale alongside huge shifts in the land devoted to cotton etc. This ties into all kinds of economic activity, southern plantations depended on a relative increase in the value and demand of cotton far above its historic level etc.
That assumes that the union never unfairly exploits the company. I think historical evidence shows that unions sometimes do exploit the company (and that union leaders sometimes exploit the members). Humans exploiting other humans is a flaw of all of us, not just corporate management.
Yeah, I'm not sure Id Software, backed by their billion dollar parent company ZeniMax Media, who in turn is backed by their parent company Microsoft, has to live in fear of being exploited by the 165 employees who just signed onto a union.
You're trying to minimize the power of the union by quoting dollar amounts, when the whole point of the union is to have power, and the whole point of unionization is to defeat superior dollar amounts by capturing the organizational memory that money cannot buy.
You cannot replace your entire gamedev team at once without destroying what makes your company, your company. You cannot respond to your entire gamedev team refusing to work other than by replacing them or by getting them to stop striking, either by aggressively union-busting or by negotiating with the union. That is the reason unions work at all.
It's not just about dollar amounts, it's about security and consequences. If a developer finds out that he got laid off his life is completely upended. If the CEO of microsoft finds out that the subsidiary of a subsidiary goes under, his life doesn't change. One of those two people is in a position of power so much greater than the other that they have absolutely nothing to fear from having to treat a small number of twice removed employees a little more fairly.
The whole point of the union is to have any power at all and to try to improve their working conditions, not to overpower the giants who rule over them. No one joins a union because they want to put themselves out of a job.
>You cannot respond to your entire gamedev team refusing to work other than by replacing them or by getting them to stop striking.
Funny thing. Pay people fairly and don't abuse them, and they don't strike. If they are striking, I have a lot more suspicion towards management than the workers.
That is as true as saying "work hard and produce good value and you wont get fired, if you are fired I have a lot more suspicion on the worker than the manager".
Sure most of the time people are fired for good reasons and most of the time people strike for good reasons, but not always.
Why would they be terrified of a handful of employees just for having the ability to influence the company? The point of a union is to improve working conditions and job security, not to murder your bosses and kill off the company. Funny thing about workers is that they like having jobs, especially ones where they have any influence at all. If a company is fearful that treating workers a little more fairly will sink them, the company deserves to go under.
What you say is true but it does not represent the spirit of what has happened historically. Historically the means of production exploit labor vastly more frequently and with greater degrees of extremity than the inverse.
This comment puts it in perspective:
>Yeah, I'm not sure Id Software, backed by their billion dollar parent company ZeniMax Media, who in turn is backed by their parent company Microsoft, has to live in fear of being exploited by the 165 employees who just signed onto a union.
Your comment is inane in the context of the reality of the situation.
The Union is a business too - and it's product is the labor of it's members.
Always follow the money - there's no free lunch. The Union negotiates incremental raises not because it is righteous and just - no, it negotiates incremental raises because the Union wants more revenue.
Sometimes the goals of a Union and it's members align - but often they do not.
Unions get a lot of free positive PR, but in modern times there seems to be more examples of bad-acting Unions than good-acting Unions. Unions have been responsible for businesses failing and massive job-loss, are the source of countless frivolous lawsuits, and in many ways suppress wages by standardizing across organizations and industries instead of allowing natural market-forces to act. Unions have been responsible for stunting the development of a generation of kids during COVID, keeping our ports non-automated and inefficient, driving product cost increases due to bloated staffing requirements, driving jobs overseas, and in some cases preventing people from gaining employment that don't want to be part of a Union.
Unions used to serve a great purpose. We used to have 12-16+ hour workdays, no days off, etc. None of that is true anymore - the great battles have been fought and won, and nobody is going back. The Unions have to find a reason to exist, so propaganda.
Software Engineers are the very last class of workers that need Unions. On average a SE earns a very healthy income and has a very comfortable working environment.
If you believe a Union will substantively benefit your quality of life - you really should just find a new job. As fanciful is it might be, a Union isn't going to 180 your job and make everything great - and now they get a cut of the wages too.
> We used to have 12-16+ hour workdays, no days off, etc. None of that is true anymore - the great battles have been fought and won, and nobody is going back.
The 8 hour workday is not guaranteed to office workers anymore.
Heh, that reminds me of the BASIC games I used to write as a kid. I didn't know that variables could be more than one letter, so S would be score, but then if I needed speed and S was taken, I'd just use T. After a while I'd hit a bug that was difficult to reason about, or leave the codebase for a while and not have any clue what the variables meant. So I'd abandon it and start with the fresh, new idea.
I have a feeling she would have said that 10, 20, 30, and 40 years ago, too.
But she's probably not wrong. Over the course of her life, the US has gone from mostly farm communities which for good or bad have long-standing social networks, to mostly atomized people in cities. We've also gotten incredibly richer as a society, but we don't know each other. If you don't know each other, who can you rely on? I assume that something similar applies to Italy.
Blaming academia is misguided, and "drive change" has never been in their job description until Progressivism took hold. The problem is each one of us: we want to numb out more than we want to do something hard. The problem is also philosophical/religious: we have collectively decided that virtue is following our animal desires (what makes you happy), which is the opposite of historical virtue. I think this can be traced back to the prevailing nominalist utilitarian view: matter is just what we make of it, and since there is nothing higher than matter, the only ethic is greatest happiness. So now, as a society, we do not really have any way to articulate the problem we intuitively feel, because the problem is that our underlying philosophy does not work, but we have even forgotten (societally) the other philosophy that has historically worked, so we cannot easily get back. I think this accounts for the interest in Stocism and traditional Christianity (especially Eastern Orthodoxy), since both unequivocally say that being enslaved to your passions (animal desires) is not the good life.
We've also been rebelling against traditional values for over fifty years and even celebrating it in song and movies. We've adopted a utilitarian ethic in lieu of the traditional values we've rebelled against. I think those are more salient probable causes than over-crowding, especially since the reasoning given for over-crowding as a reason uses a utilitarian ethic (people are only good because they can afford do be). A large part of virtue is doing the good thing regardless of hard times or good times.
Well, if your calculator has a loose wire that sometimes flips a random bit somewhere, you might find that a slide rule that is consistently correct has a certain value.
> If something "seems right/passed review/fell apart" then that's the reviewer's fault right?
No, it's the author's fault. The point of a code review is not to ensure correctness, it is to improve code quality (correctness, maintainability, style consistency, reuse of existing functions, knowledge transfer, etc).
I mean, that's just not true when you're talking about varying levels of experience. Review is _very_ important with juniors, obviously. If you as sr eng let a junior put code in the codebase that messes up later, you share that blame for sure.
In the late '90s, when CPUs were seeing the advances of GPUs are now seeing, there wasn't much of a market for two/three-year old CPUs. (According to a graph I had Gemini create, the Pentium had 100 MFLOPS and the Pentium 4 had 3000 MFLOPS.) I bought motherboards that supported upgrading, but never bothered, because what's the point of going from 400 MHz to 450 MHz, when the new ones are 600 or 800 MHz?
I don't think nVidia will have any problem there. If anything, hobbyists being able to use 2025 cards would increase their market by discovering new uses.
reply