In humans, the respiratory system facilitates the intake of oxygen and removal of carbon dioxide in the body. The lungs, heart, blood vessels, and blood cells are all important figures in respiration. When we inhale, oxygen-rich air fills our lungs and the hundreds of thousands of tiny pockets called alveoli. Each alveolus is surrounded by a membrane full of capillaries. Oxygen moves across this membrane and into our blood, where it attaches to red blood cells. These red blood cells are circulated out of the lungs and around the body, where it nourishes all of our bodily tissues by "dropping off" some of that oxygen. In place of the oxygen, gaseous bodily waste like carbon dioxide can attach and return to the lungs. When these red blood cells return to the lungs, they drop off the carbon dioxide and pick up some fresh oxygen to carry throughout the body! All of this occurs in a continuous cycle.
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