The Missouri Compromise allowed Missouri to be admitted to the Union as a slave state. Naturally, you would not have liked this action if you were opposed to slavery. You might have found the practice of slavery morally reprehensible and would not have appreciated it being expanded into a new state. Politically speaking, the admission of Missouri as a slave state gave the South more power in Congress. Maine was admitted as a free state, which lessened the sting for the Northern states a little bit in this case. Another reason to dislike the compromise is that it set a precedent that Congress would cave to the pressure of the slave states in the future. After the Missouri Compromise, states would not be admitted unless a free and slave state could be admitted at the same time. A final reason to be against the Missouri Compromise is that it further divided the country on the issue of slavery.
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