Skip to main content

Why might labor laws have produced hardship in some cases?

Labor laws are often thought of as a positive event for working people. However, it is possible for labor laws to cause hardship. For example, when unions were given the right to exist, it gave the workers more power. This often led to higher wages. However, for the business owners, it meant higher costs. Business owners might incur lower profits because of this. It is possible they might hire fewer workers. This could increase unemployment. Business owners might pass the higher costs to the consumers who then would pay higher prices for the products they bought.


Another side effect of labor laws is that it removes some flexibility. Companies must follow the procedures outlined in the union contract. Failure to follow the established procedures could lead to charges of discrimination or favoritism. This prevents any negotiation with an individual worker. As a result, a company isn’t able to reward a worker beyond what is stated in the contract. This could lead to the loss of good workers who might go elsewhere where they could negotiate their own deals.


If an employer fires a worker, the employer may be in a difficult position if another company contacts them about hiring that worker. There are laws that protect the confidentiality of the worker. There also are laws that state that an employer must warn a future employer if a person was fired because he or she was acting dangerously. A company has to walk a very fine line in these situations.


It is possible for labor laws to cause hardships.

Comments

Popular posts from this blog

Is there a word/phrase for "unperformant"?

As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...

Is 'efficate' a word in English?

I routinely hear the word "efficate" being used. For example, "The most powerful way to efficate a change in the system is to participate." I do not find entries for this word in common English dictionaries, but I do not have an unabridged dictionary. I have checked the OED (I'm not sure if it is considered unabridged), and it has no entry for "efficate". It does have an entry for "efficiate", which is used in the same way. Wordnik has an entry for "efficate" with over 1800 hits, thus providing some evidence for the frequency of use. I personally like the word and find the meaning very clear and obvious when others use it. If it's not currently an "officially documented" word, perhaps its continued use will result in it being better documented.