[citation][nom]rds1220[/nom]I am not saying to be a puss and let people walk all over you but being an arrogant asshole is not right either. If you think that is the way to handle things in the business world than you have no exprience in the real world or you have a very sadistic boss. If I treated people like that I would hae no workers and no compters to fix.[/citation]
If you don't have enough of a spine to stop problems like these while they're being created, then you're gong to end up with a compilation of utter junk. It's called quality control, and bad things happen when you don't enforce it. Don't blame your own failures on another person's perfectly fine work, and your boss will have no reason to be 'sadistic'.
More about the article, though... goddamn, Linus; stick it to 'em. When someone else completely botches a piece of code and then shovels it off on someone else's work, it would be unacceptable NOT to do exactly what he did. Nice to see someone who still stands for doing it right the first time, and not patching the patches that were supposed to fix the originally broken code.