Despite a great deal of social upheaval and a number of serious political and economic issues, the United States did not descend into civil war or division after the American Revolution. When we look at other revolutions around the world, including the French, we can see how significant this is. While many historians credit the stability imposed by the counter-revolution that was the U.S. Constitution, it is also true that the Articles of Confederation, as a limited form of government, provided perhaps the greatest degree of national unity that was conceivable in the immediate aftermath of independence. It established a framework for more unified government even as it proved inadequate to deal with the challenges the nation faced in the so-called "critical period." The government under the Articles was successful in providing for western expansion, a crucial issue at the time. The Land Ordinance of 1785 provided for the parceling of land in the Northwest Territory, enabling the orderly sale of federal lands in the region. The Northwest Ordinance, passed two years later (ironically while the Constitutional Convention was underway in Philadelphia) created a process by which territorial, and eventually state, governments could be established. So the Articles, while ultimately inadequate, were not a total failure.
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