Skip to main content

What is the importance of plotting in Act III, Scene 1 of Macbeth?

The word "plotting" refers to an act in which the perpetrator(s) secretly plan to commit an evil deed. In this sense, then, plotting, by its very nature, seeks a malicious outcome, meaning those who indulge in the act do not wish to do any good and are, consequentially, evil.


Plotting in Act III, Scene 1 is important because it reveals the extent of Macbeth's perfidy. The scene illustrates that he has reached such a state of ruthless and cold-blooded malice, that he has lost all rectitude. There are no boundaries to his pervasive perversion, so much so that he plots the murder of his confidante and friend Banquo and Banquo's son, Fleance.


It is clear from the beginning of the scene that Macbeth has already started plotting Banquo's assassination. Macbeth, who earlier somewhat reluctantly acquiesced to his wife's insistence on killing king Duncan, has now become a master in the art of murder. His conversation with Banquo most pertinently illustrates his sly and wicked intent. He seeks as much information about Banquo's journey as possible so he may perfectly plan the assassination.


When Macbeth meets the assassins, he blatantly lies to them about Banquo's role in their misery and strife, giving them a reason to kill the general. He absolves himself from all blame. Furthermore, he challenges their courage and their will to destroy those who had supposedly done them harm—in this instance, Banquo. They are easily convinced and swear revenge. Macbeth, just to make sure, reminds them that Fleance should also be killed.


Macbeth's cold-blooded statement at the end of the scene most potently indicates the depth and magnitude of his evil:



It is concluded. Banquo, thy soul's flight,
If it find heaven, must find it out to-night.



The once-honorable and -admired general has truly lost his way—the fair has become absolutely foul.

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

What warning does Chuchundra issue to Rikki?

Chuchundra, the sniveling, fearful muskrat who creeps around walls because he is too terrified to go into the center of a room, meets Rikki in the middle of the night. He insults Rikki by begging him not to kill him. He then insults him by suggesting that Nag might mistake Chuchundra for Rikki. He says, "Those who kill snakes get killed by snakes."  He issues this warning to Rikki not to help keep Rikki safe but as a way of explaining why Rikki's presence gives him, Chuchundra, more reason to fear.  Chuchundra starts to tell Rikki what Chua the rat told him--but breaks it off when he realizes he might be overheard by Nag. He says, "Nag is everywhere, Rikki-Tikki." Rikki threatens to bite Chuchundra to get him to talk. Even then, Chuchundra won't overtly reveal any information. But he does say, "Can't you hear, Rikki-Tikki?" This is enough of a clue for the clever mongoose. He listens carefully and can just make out the "faintest scratch-s...