The Supreme Court's decision in Dred Scott v. Sandford greatly enflamed sectional tensions between the North and the South. By declaring that Dred Scott was not entitled to his freedom, even though he had lived in Wisconsin territory for a time, the Court basically invalidated the Missouri Compromise, which declared territories north of the 36'30 line closed to slavery. This decision thus outraged many Northerners, who were convinced that a "slave power" conspired to spread the institution throughout the nation despite the opposition of the North. (A majority of the Supreme Court, including Chief Justice Roger Taney, was pro-slavery.) It even threatened the doctrine of "popular sovereignty" proposed by Northern Democrats like Stephen Douglas as a solution to the issue of the expansion of slavery. Southerners no longer saw this as a valid political position, and rejected Douglas when he attempted to make it part of the Democratic Party platform in the presidential election of 1860. Most importantly, it greatly added to the popularity of the Republican Party in northern states. The Republicans were devoted to stopping the spread of slavery, and when their candidate Abraham Lincoln won the presidency in 1860, largely because of the split in the Democratic Party mentioned above, the states of the Deep South, led by South Carolina, seceded from the Union. So the decision exacerbated tensions between North and South and made compromise over the issue of slavery far less likely.
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