Pressure, symbolized as P or p in physics, measures the amount of continuous perpendicular force applied to a surface. Pressure is calculated by dividing the amount of force (typically measured in newtons) by the surface area that the force is being applied to. The SI unit for pressure is the pascal, which is the equivalent of one newton of square force per one square meter of surface area. However, pressure is often measured in non-SI units when calculating liquid or atmospheric pressure. An example of a common non-SI unit of pressure is the bar, a unit equivalent to 100,000 pascals that is most often utilized to measure the Earth's atmospheric pressure. Pressure is also a unit of ideal gas law, varying linearly with absolute temperature and the amount of substance, and inversely with the volume of the gas.
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