Skip to main content

Macbeth is a tragedy, a drama about a high-ranking individual who has many noble qualities, but who suffers from a tragic flaw. Because of this...

It is true that Macbeth is manipulated, most notably by his own wife and the Weird Sisters, but if he did not already possess the flaws that compel him to make unscrupulous choices then his story would not have ended in his own destruction.  He, ultimately, is responsible for his own tragic ened.


Macbeth admits that he suffers from a "Vaulting ambition" but believes that it is not enough to convince him to murder Duncan (1.7.27).  However, when his wife wounds his pride, insisting that "When [he] durst [commit the murder], then [he was] a man" (1.7.56).  In other words, unless he is willing to murder Duncan, then he is not really a man in her eyes.  She calls him a "coward" and "green and pale," painfully wounding his ego again and again (1.7.47, 41).  She knows just what buttons to push.  It is only after she insults his pride that Macbeth is willing to move forward with their plan.  If he were less prideful, she would not be able to manipulate him in this way.  


Further, the Weird Sisters, as early as Act 1, scene 1, admit that they are going to attempt to deceive Macbeth.  They chant, "Fair is foul, and foul is fair," meaning that they are going to make good things seem bad and bad things seem good (1.1.12).  Therefore, when they tell Macbeth that he is going to be king, it sounds really good but it will, in actuality, be quite bad for him.  It compels him to consider how to make it happen when his ambition takes hold of him.  Were he less ambitious, less easily manipulated, or even more loyal, he would not have taken the path to his own demise.  

Comments

Popular posts from this blog

Is there a word/phrase for "unperformant"?

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 ...

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...