Gravity is essential to a stream's ability to erode and deposit materials. In fact, you can start by saying quite literally that streams would not exist without gravity. Gravity is the reason water falls from the sky, and, once it has fallen, gravity pulls water to the lowest elevation. Gravity creates streams. Gravity is the reason water continues to flow into streams, and the reason water flows along streams to rivers and lakes. Since it the motion of water along, over, and through things that causes them to erode, gravity is the force driving erosion. Gravity is erosion's engine. The process of depositing materials is known as sedimentation. Gravity is one of the forces shaping sedimentation. Other factors also apply, like the viscosity of the liquid in which particles are suspended. In general, water's buoyancy pushes the particles up, in suspension, and gravity pulls them down, so they are deposited.
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