The information that can be determined by observing the spacing of contour lines on a topographic map is relative steepness. It's relative steepness because without knowing the map's relief or the map's contour interval, all that a user can do is see that certain areas are steeper than others. Contour lines that are closely spaced indicate a steeper section than contour lines that are widely spaced. In order to know exactly how steep a particular slope is, the map user will need to know the contour interval. The contour interval is the change in elevation from one contour line to the next contour line. Once the elevation change is known, the user would need to know what the map's scale is. By knowing the contour interval and the map's scale, a person can then calculate the actual steepness of a slope.
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