The Mythical Man-Month: Essays on Software Engineering Literary Elements

The Mythical Man-Month: Essays on Software Engineering Literary Elements

Genre

Nonfiction, Business Essay Series

Setting and Context

United States, mid to late 20th Century, in a software development company

Narrator and Point of View

The book is written from a third person limited omniscient perspective.

Tone and Mood

The overall tone of the book is grim. The author is identifying and describing a serious problem.

Protagonist and Antagonist

The protagonists are the software developers. The primary antagonist is time, or to a lesser extent the supervisors of the people doing the work

Major Conflict

The problem, according to the book, is that management tends to underestimate the difficulty of scoping software development projects. They allocate too few resources in terms of time and personnel, they insist on hard deadlines and refuse to reduce the difficulty or complexity of the project, they refuse to compromise or to prioritize features or activities, and when the project inevitably falls behind schedule they attempt to get back on track by adding more people to the task. This doesn't work because of unclear requirements, poor communication, and the fact that software development workers aren't fungible.

Climax

There is no climax to the book because there is no narrative arc. The book is a series of collected essays on the subject of software development.

Foreshadowing

When management insists on a hard deadline, the reader knows the project wil be late.

Understatement

The author understates the naievete of a project team lead who, having presumably been through management training before or else who has hopefully been a member of a similar team in the past, still believes that the people doing the work are fungible, easily replaceable, and not in need of rest after they burn out.

Allusions

There are frequent allusions to the Christian Bible. The story of the Tower of Babel figures prominently.

Imagery

The image of the tar pit is used to describe a situation that consumes everything that touches it.

Paradox

A complex software project requires more effort than expected to complete it, but adding additional people increases the complexity of what has to be done, and makes the project even bigger and more complex, increasing the number of person-hours required to complete it.

Parallelism

Parallelism does not occur in this book, although allegory is present in the references to the tar pit, the tower of Babel, a surgical team, and a "silver bullet" representing an item that can remove a major obstacle to progress.

Metonymy and Synecdoche

"As the child delights in his mud pie, so the adult enjoys building things, especially things of his own making." The child and the adult are representative of humanity, or at least male humanity, as a whole. Female pronouns do not appear in this book except when quoting a female author such as Dorothy Sayers.

Personification

The software developer personifies the creative effort. Notwithstanding the fact that the first computer programmer, Ada Lovelace, was female (along with the majority of the first NASA programmers), the author chooses to depict computer programmers and software developers as uniformly male. He refers to workers as "men" throughout the book, not just in the title, and every hypothesized role in software development with significant responsibility is described as belonging to a male person.

Update this section!

You can help us out by revising, improving and updating this section.

Update this section

After you claim a section you’ll have 24 hours to send in a draft. An editor will review the submission and either publish your submission or provide feedback.

Cite this page