Cassius, as Julius Caesar describes him, has a “lean and hungry look,” indicating he is eager to cause trouble and manipulate others to do what he might not be brave enough to do. Cassius warns Brutus that Caesar is becoming very popular in the eyes of the Romans. What the army and the Senate fear most is that the Republic will be replaced with a monarchy, which the Romans had ended in about 509 BCE, almost five hundred years before the events in this play occur (55 BCE). Cassius feeds on this fear to overthrow the popular general Julius Caesar. He manipulates Brutus and others into forming a conspiracy to murder Caesar. They are successful in this act, but misjudge how much the Roman people fear returning to monarchy. He thought he knew the heart of the Romans more than he actually did. Cassius remains involved in the conspiracy, but allows Brutus to take the brunt of the anger. His character remains the same throughout the play, but his confidence of his place in the new Rome he created changes. Cassius commits suicide, though even in this he manipulates his servant to do the actual deed. Throughout the play, Cassius convinces others to do what he wants done but cannot do himself. The development of his character is only in the realization of his failure, which he finally has to admit was his own fault. He cannot throw this off on someone else.
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