Yes. At the beginning of the novel, Amir sits idly by and witnesses Hassan get raped, then plants money and a watch underneath Hassan's bed to make it look like Hassan stole from him. Amir's actions force Ali and Hassan to leave their home which ends Baba's long friendship with Ali. Throughout his life, Amir is plagued with guilt for his actions until he gets a call from Rahim Khan telling him that there is a way to be good again. When Amir travels to Pakistan to speak with Rahim Khan, Rahim tells him about Hassan's son, Sohrab. Amir accepts the challenge to find Sohrab in Afghanistan and give him a new home with two Christian missionaries living in Pakistan. Amir atones for his past wrongs by facing off against Assef one on one in order to leave Afganistan with Sohrab. Amir almost dies during the fight, but is fortunately saved by Sohrab, who uses his slingshot to knock out Assef's eye. After Amir recovers from his severe injuries, he attempts to adopt Sohrab only to find out how difficult the immigration adoption policy is. After Amir tells Sohrab that he will have to put him in an orphanage for a little while, Sohrab attempts to kill himself. Amir saves Sohrab's life and eventually takes him to America where Sohrab is safe. Amir atones for his wrongs by risking his life and saving Sohrab's life several times in the process of bringing him to America. Amir's sacrifice gives Sohrab a chance to experience a happy life in America.
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