Skip to main content

What are the disadvantages of judge made law, relative to statute law?

There are at least two main disadvantages of judge-made law relative to statute law.  One disadvantage has to do with the legitimacy of such law while the other has more to do with pragmatic issues.


In pragmatic terms, law made by judges will not be able to touch on as many issues at as many times as statute law can.  Judges can only make law when cases come before them.  They cannot go out and change laws simply because they want to.  In addition, they cannot rewrite laws based on whatever they feel is best at a given time.  Instead, they can only rule on specific issues raised in their cases.  For example, let us look at “Obamacare.”  Judges could strike down certain portions of the law if they wanted, but they only if plaintiffs brought cases that touch on those portions of the law.  In addition, judges would not be able to replace the law with something they liked better.  They would only be able to invalidate the law as it currently stands.


In terms of legitimacy, the disadvantage of judge-made law is that it will not seem as legitimate and democratic to many people.  Many judges are not elected.  Even those who are do not interact with other judges to debate and to make laws through consensus.  This is in contrast to the legislative branch.  In this branch, all lawmakers are democratically elected and will therefore seem legitimate to the people.  In the legislature, lawmakers get together and discuss and debate ideas.  From these interactions come laws.  This process is much more likely to make people feel satisfied with the laws.  They will respect the laws more because those laws have been created by elected officials who have been able to discuss and debate them.  They will not feel that way as much about laws that have been made by, at most, a handful of judges who are often not elected.


For these reasons, laws made by judges are generally at a disadvantage compared to statute laws.

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 ...

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...

What warning does Chuchundra issue to Rikki?

Chuchundra, the sniveling, fearful muskrat who creeps around walls because he is too terrified to go into the center of a room, meets Rikki in the middle of the night. He insults Rikki by begging him not to kill him. He then insults him by suggesting that Nag might mistake Chuchundra for Rikki. He says, "Those who kill snakes get killed by snakes."  He issues this warning to Rikki not to help keep Rikki safe but as a way of explaining why Rikki's presence gives him, Chuchundra, more reason to fear.  Chuchundra starts to tell Rikki what Chua the rat told him--but breaks it off when he realizes he might be overheard by Nag. He says, "Nag is everywhere, Rikki-Tikki." Rikki threatens to bite Chuchundra to get him to talk. Even then, Chuchundra won't overtly reveal any information. But he does say, "Can't you hear, Rikki-Tikki?" This is enough of a clue for the clever mongoose. He listens carefully and can just make out the "faintest scratch-s...