Many different factors can be said to have driven the development of self-government in the American colonies. The first is their relative isolation from England. News, instructions for royal governors, and other information crucial to the exercise of state power took months to reach the colonies from Britain, and this made it difficult for England to enforce its own policies. In the absence of these policies, governors and colonial assemblies exercised considerable autonomy in making decisions. Another reason that the colonies developed a tradition of self-government was the that the British saw it as inefficient and costly to enforce laws, especially the Navigation Acts, which were intended to regulate trade. Smuggling, the printing of paper money, and other practices ostensibly banned, or at least frowned upon, by England were routinely practiced. The colonies also had a much larger voting population than Great Britain, because a higher percentage of people owned property, and met the qualification for voting. Thus colonists expected that their will would be reflected in the laws, and they thought that local representatives were better positioned to make such laws than a faraway Parliament. Some scholars point to other factors, like the emergence of the Great Awakening and the Enlightenment, which caused American colonists of a variety of social classes to question British rule.
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