After three weeks at Auschwitz, Elie and his father are marched to the work camp at Buna. After a four hour walk they arrive at a camp which Elie describes as looking as though it had gone through an "epidemic," with not many people around. Elie and his father are installed in what was called the "orchestra block" because there were several musicians living there. One of the musicians, a Polish man named Juliek, explains to Elie that they work in a warehouse and that the work was not "difficult or dangerous." He does, however, warn Elie about the "kapo," named Idek, who sometimes had "bouts of madness." The work consists of counting "bolts, bulbs, and small electrical fittings." Elie is told to take his time at the work but to beware of the SS watching. He is able to work next to his father. There were also "Polish civilians" and a "few French women" in the warehouse. One time they were also required "to load diesel engines onto trains" while being supervised by the SS. Elie becomes friends with two brothers, Yossi and Tibi, and is also befriended by a French Jewish girl who comforts him after he is attacked and beaten by Idek. Amazingly, Elie meets the French girl years after the war and they talk about their experiences.
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