Romeo utters this line immediately after killing Tybalt in the first scene of Act Three. As his kinsman Benvolio urges him to flee, knowing that the Prince will possibly sentence him to death if he is captured, Romeo stands as if in a daze. He realizes the gravity of what he has done. He has cost his friend Mercutio his life by his ill-timed intervention in his fight with Tybalt, and he has doomed his recent marriage to Juliet. With this line, he is, essentially, cursing his bad luck. This is all the more powerful because the audience knows that Romeo and Juliet are doomed, and that the death of Tybalt has probably set in motion the events that will bring about their fate. As it turns out, Romeo has reason to decry his bad luck. The Prince does not sentence him to death, but to be banished to the nearby town of Mantua. The Friar's scheme to reunite the two lovers, and avoid Juliet's pending marriage to Paris, falls apart. The death of Tybalt at Romeo's hands is thus a major turning point in the play, which Romeo acknowledges, in a way, with this statement.
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