Those Pilgrims who wrote about their experiences at Plymouth described the area in different ways. In his History of Plymouth Plantation, the most famous account of the settlement, William Bradford, the governor of Plymouth, described the region alternately as a "hideous and desolate wilderness, full of wild beasts and wild men." Bradford's purpose in writing the History was to illustrate the workings of God in providing for his band of Separatists in such a hostile environment. In an often-cited passage, Bradford describes, for example, a Patuxent village, deserted due to a smallpox epidemic that preceded the Pilgrims, as being cleared out by God for their benefit. Another famous Pilgrim leader, Edward Winslow, described the area as teeming with natural resources, including fish, shellfish, berries, and good land for growing Indian corn. Winslow concluded that "men might live as contented here as in any part of the world." Winslow, who developed a friendship of sorts with the local Wampanoag leader Massasoit, described the inhabitants of the area as "people without any religion, or knowledge of any God," yet "very trusty...quick-witted, and just." Winslow assured a correspondent that Pilgrims could "walk as peaceably and safely in the wood...as in the highways in England." The Pilgrims, in short, believed that the world they had come to inhabit was provided for them by God.
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