In writing the history of Plymouth Plantation, William Bradford gave God the credit for pretty much everything he and the other Separatists experienced in their journey on the Mayflower in 1620 and the first difficult winter they spent in Massachusetts. In the spring of 1621, a Pemaquid named Samoset approached the English colony and spoke to them in broken English of a Wampanoag sachem, Massasoit. Shortly thereafter, Massasoit came to the colony with Squanto, a Patuxet who spoke English well. After negotiating a six-point agreement, Massosoit left, but Squanto stayed behind with the colonists and helped them. He was a translator and advised them on the best places to plant, hunt, fish, and trade, and how to navigate the local geography. Bradford describes Squanto as " a special instrument sent of God for their good beyond their expectation." Bradford gives the credit to God for sending Squanto to the colony.
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