P waves and S waves are both types of seismic waves. A P wave (primary wave) is a compressional wave that shakes the ground back and forth in the same direction and in the opposite direction. P waves have the highest velocity and so are the first waves from an earthquake to arrive at a seismograph. S waves are secondary waves and are a type of elastic wave. An S wave shakes the ground back and forth perpendicular to the direction the wave is moving. S waves are more destructive than P waves because the lateral movement of the wave produces a rolling effect along the surface, causing damage to structures. The time difference between the P wave and S wave at the seismograph is used to determine how far away the epicenter is located. Using three seismograph locations, the epicenter can be accurately determined.
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