[QUOTE=Voyager]
And if you are in favor of the market, you should be in favor of unions, since they are part of the market also. When I worked for Bell Labs I was not in a union, but I got lots of benefits fought for by the people who were.
[/QUOTE]
I’m not opposed to unions, no. Not sure why you think I am. I AM opposed to union monopolies backed up by government coercion, but that’s something different. Certainly collective bargaining is part of the market (in this case, the labor market).
The productivity increases aren’t due to labor, though. Thus, IMHO labor wouldn’t reap the majority of the rewards from that increase (which is what’s actually happened…they aren’t, by and large).
As to ‘no one pays anyone no one buys anything’ type arguments, I believe they are attempts to appeal to emotion and also to take things over the top. We don’t pay people in order to buy stuff, we pay them as an exchange of money and benefits for labor given, a simple transaction. If my company is more productive due to labor, then I HAVE to pay them more to keep them, or they will take their labor elsewhere and benefit someone else. However, if my companies productivity gains are because of capital I invested in infrastructure or automation, then why SHOULD I pay labor consummate with my gains?? I’m not saying that labor should get nothing (because nothing is ever black and white, and no gains are every from one single factor or innovation, but from a range of them, including labor), but you seem to be saying that if my company increases their profits that I should automatically pass those along to labor, even if labor was a minor factor in those gains…just because those people would then buy stuff. To me, that’s not how it works.
Well, the second half of this sentence is a strawman…I never said nor think that because people get a ‘cellphone’ that they shouldn’t or wouldn’t mind not getting a raise. That has nothing to do with my point.
As for the '50’s, while automation was coming into the work force, labor was still a major factor for why and how businesses expanded, thus why labor got a larger share of the gains from companies profits. Remember that during that time period, skilled and semi-skilled labor was still vital in manufacturing in the US. That gave labor a large advantage when it came to leverage against companies…if companies who were profiting from labors increased production then they had to pay some of those gains back, or their labor force responsible would take their labor somewhere else, and allow them to profit instead.
To me (in my non-economics major ignorance), the turning point was when labor attempted to over-leverage that by using the government and the public to press through their increasing demands. The backlash is what we have today. Many of the things that companies did in the past that required large skilled or semi-skilled (or unskilled) labor forces were broken down and automated. Processes that used to take many people to over see are done by expert systems and automated processes. Corporate bloat was trimmed down by new streamlined procedures and processes that allowed for fewer people to oversee and manage. All the while, productivity increased by a large factor. That’s how the US is able to manufacture at higher levels today with a fraction of the work force. All of this, however, lessened the dependence of industry on labor, however, since you needed far fewer people, and those people were less necessary, I guess.
Since you used an anecdote taken from your own experience, let me share mine. When I started off as a network engineer, the job was extremely difficult, and it took people of fairly exceptional skill to do it. Every network devices…routers, switches, hubs, firewalls, etc…had a different, extremely esoteric command line interface you needed to master to configure them. The IP addressing scheme itself took some level of skill with binary and understanding of subnetting to manipulate, and there were no schools or training for this by and large. You learned the old fashioned way. I remember when IP first came out, and we were all trying to figure out how to address things on the internet (this was before RFC-1918 private network addressing) or even in large corporate networks. Network engineers, rightfully, commanded large salaries and we were always in demand. My personal salary shot up continuously…ever time I changed jobs I got at least a 10% bump, often more, and I changed jobs extremely frequently through the 90’s. This was the norm in my own circle of peers.
Today? Well, I won’t say that network engineers are a dime a dozen, since we aren’t (and I still make pretty good money), but today we don’t command the same level of demand we once did. Why? Well, because of expert systems of course. Today, to configure a router/switch/firewall/VM farm/SAN/server system/etc you need to know the basics, to be sure, but it’s all a GUI driven process. IP Addressing? There are tools that will subnet an address space to any mask you like in literally seconds (I have two apps on my iPad and iPhone to do this, and you can simply Google and use a web browser to do one now). If I need to know how a command works or the syntax, I can use Google to look it up quickly. Someone can do what I do with a fraction of the knowledge about infrastructure and architecture that I have (and it will probably be some damned kid making a fraction of what I make doing it too :p).
So, is this right? Shouldn’t network engineers just get to continue to make more and more? I mean, the companies are making more and more. Shouldn’t we also make more? My answer remains the same as above…should we make more? Certainly, if we contribute to the overall success of the company. Should we make more consummate to the companies gains? Nope…why should we? The breakthrough in why we engineers are more productive isn’t us, it’s in the systems we have today, in the tools we use. As for the people who created those, I’d guess they ARE making more or have made more, by and large.