There are some updates to this page that haven't been applied yet because you've entered some data into a form. You can refresh this page to receive new updates.
American citizens often complain about how high CEO salaries are. The SEC attempted to mitigate this, and required CEO salaries to be publicly disclosed. As a result, they increased approximately three-fold between 1976 and 1993, going from 36 times the average worker pay to 131 times the average worker pay. "It encouraged other CEOs to demand higher pay, since now they had hard data telling them they were underpaid."[1]
This looks to me to be a classic example of the correlation/causation problem. CEO salaries were heading up, a policy changed, and CEO salaries continued to head up... Therefore the policy must have raised salaries! This is not at all clear. Maybe CEOs demanded higher pay, but average workers demanded lower pay, and the net effect was in fact to lower pay. However, other forces were causing pay to go up anyway, so on net pay went up, even though the effect of this policy was negative.
Girl Talk has a unique ability to making incredibly catchy mashups. He samples songs that already have a wide audience. Chances are you already like many songs featured on Girl Talk's albums. He provides a fresh take on these songs, in a style that is reminiscent of improvised jazz, and does so seamlessly. It's difficult not to tap your foot to the beat. Each sample seems to hit a sweet spot in terms of the listener's attention span. As soon as you're getting comfortable with the current beat he switches it up.
As a case study, "Oh No" on the album All Day (released today), begins by mixing "War Pigs" by Black Sabbath and "Move Bitch" by Ludacris. There are no obvious tempo adjustments and it sounds as though each song was originally written with the other in mind. Even though it's not common for the audiences of these two artists to overlap, Girl Talk makes them more accessible.
Yeah, I guess I can see the appeal, objectively. But I don't really like many of the songs that he mixes in the first place, so it's hard for me to like the mashups holistically.
By definition, writing new code means you are creating new functionality. Re-writing existing code doesn't introduce new functionality, but improves that which already exists. It is often frustrating to redo work you or somebody else has already done.
Code that is selected for rewrite is often flawed in some way (there's no point in re-writing good code), and requires reading it to understand it. Hence, rewriting often involves reading bad code.
I wouldn't say that rewriting code is necessarily less enjoyable than writing new code. It's similarly exhilarating to make an existing function that is well-written an order of magnitude faster, shorter or more efficient.
I agree. I love to do a great code refactor that improves one or several dimensions of code quality by a relevant factor. It's just awesome, and when you are refactoring your own code it means you are improving, which is always good.
