Skip to main content

How would you analyze Macbeth's statement, "I am settled and bend up / Each corporal agent to this terrible feat" (1.7.92-93)?

This statement follows a difficult argument between Macbeth and Lady Macbeth. Lady Macbeth becomes very angry with her husband when Macbeth says he does not want to move forward with their plan to kill Duncan (1.7.34). Lady Macbeth proceeds to try all manner of insults and manipulation to coerce Macbeth to recommit to their plan, including wounding his ego by insulting his masculinity and implying he is disloyal to her. She calls Macbeth a "coward" and claims he lacks courage. Lady Macbeth also says she would kill her own baby if she had promised him that she would do so. Once Lady Macbeth convinces Macbeth that no one will doubt their feigned grief when Duncan is discovered dead and that they can actually get away with this murder, Macbeth says, "I am settled and bend up / Each corporal agent to this terrible feat" (1.7.92-93). In other words, Lady Macbeth has convinced Macbeth to be in favor of their plan. After much indecision, Macbeth is no longer on the fence. He claims that all his actions will now be focused on murdering Duncan. Once Lady Macbeth has successfully convinced Macbeth, there is no going back; he will remain on this murderous path until the play's end.

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