Marbury v. Madison was significant because with its decision in the case, the Supreme Court established the principle of judicial review. The case stemmed from newly-elected President Thomas Jefferson's refusal to allow his Secretary of State James Madison to deliver commissions for a number of lower-level judicial appointments made by outgoing President John Adams. One of the appointees, William Marbury, challenged Jefferson, claiming that the Judiciary Act empowered (required, even) the Supreme Court to issue a legal writ called a mandamus that would force the President and his Secretary to deliver up the commissions. The Supreme Court, headed by Jefferson's political adversary John Marshall, ruled that this part of the Judiciary Act was in fact unconstitutional. The case was very complex, and not in and of itself all that consequential, but the precedent established by Marshall--that the Court might rule a law passed by Congress unconstitutional--was a very significant one. Though the Court would not exercise judicial review for several decades, the principle of judicial review would over time become a pillar of the system of checks and balances in the U.S. Constitution. It was also one of several landmark decisions issued by the Court under Marshall, whose vision of a robust federal government would prove very influential.
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 ...
Comments
Post a Comment