Unlike in other plays (Macbeth, in particular), Shakespeare leaves no doubt that fate is at work in Romeo and Juliet. In the Prologue, the chorus tells the audience that by the end of the play, a pair of "star-cross'd lovers" will take their own lives, their love doomed to disaster. So in a way, every event in Romeo and Juliet leads to this conclusion, and we impose this interpretation on the course of the play. But even without this statement in the prologue, we can still point to several key events in the play to show how fate brings about the demise of the two young lovers. First, Capulet restrains Tybalt from attacking and possibly killing Romeo at the masque, a decision that makes it possible for Romeo to meet Juliet. Then, after Romeo and Juliet are married, Romeo kills Tybalt in the streets, an act that ends in his banishment. Perhaps most poignantly, Friar John fails due to plague to reach Mantua with a letter from Friar Laurence explaining that Juliet's "death" is a ruse, but Balthasar, who believes Juliet dead, does. So from the time Romeo and Juliet first meet, it seems that one thing after another goes wrong. Shakespeare makes it clear from the beginning of the play that this will happen, a dramatic decision that makes this play all the more tragic.
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