There are several reasons why Bob Ewell isn't worthy of receiving compassion in the novel To Kill a Mockingbird. Throughout the novel, Bob Ewell is the most despicable citizen in Maycomb and is responsible for Tom Robinson's wrongful conviction after accusing him of assaulting and raping his daughter. During the trial, Atticus reveals that Bob Ewell is the one who beat his daughter, and Bob vows to avenge Atticus. Bob publicly spits in Atticus' face, proceeds to harass Tom's wife, Helen, and attempts to break into Judge Taylor's home. In Chapter 28, Bob does the unspeakable and attempts to murder Jem and Scout while they are walking home from Maycomb's Halloween festival. Fortunately, Boo Radley saves the children by wrestling Bob Ewell off of them and killing him with Bob's own knife during the struggle. Bob's unapologetic, vengeful attitude, coupled with his attempt to murder two innocent children are the reasons he isn't worthy of receiving compassion. Bob was not satisfied winning the case which resulted in Tom's death, and chose to harm those who opposed him during the trial. Attacking two unarmed innocent children is the epitome of immorality. Bob Ewell was malicious, depraved, and evil throughout the entire novel and deserved to die after attacking Jem and Scout.
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