Elie and his father endure several "selections" during the course of their ordeal in Nazi concentration camps during World War I. A selection made the difference between life and death. In the initial selection at Birkenau they are advised to lie about their ages in order to avoid being pointed to the right (sometimes the left was death and sometimes the right) and certain death by the infamous Dr. Mengele, who presided over many of the selections in the camps affiliated with Auschwitz. Later, before they board a train to Buchenwald, the weak, those who would be killed, were pointed to the left and the stronger men to the right. During this selection, when he sees his father has been marked for death, Elie risks his life to bring him back to the right. Unfortunately, Elie's father dies at Buchenwald. How many survived the various selections is unclear. At the end of the war the total number of Jews killed was estimated at over six million, and some think the number much higher. One thing for sure is that when American troops liberated Buchenwald in the spring of 1945 there were 20,000 prisoners still alive, among them Elie Wiesel. These prisoners would have all survived at least one selection, and for most many more.
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