The Mythical Man-Month

Essays on Software Engineering

Paperback, 322 psl.

English kalba

Publikuota 1995 m. lapkričio 7 d., Addison-Wesley Professional.

ISBN:
978-0-201-83595-3
Copied ISBN!

Žiūrėti „OpenLibrary“

5 žvaigždutės (2 atsiliepimai)

Classic text on the human side of software engineering, containing essays on the management of software teams, projections about how computer languages and tools will evolve, and philosophical speculation. Unlike most other books about computing, Brooks' work has been remarkably enduring, remaining in print for at least four decades. The book is most famous for its statement of Brooks' Law: "adding manpower to a late software project makes it later".

8 leidimai

apžvelgė autoriaus Frederick P. Brooks knygą The Mythical Man-Month

The Mythical Man Month Review

4 žvaigždutės

I find that programmers seem better at coordinating work and communicating about work compared to other fields that I have experience with. The work is organized in a much more humane way than the email inbox driven hyper-active hive-mind model of other office workers so vividly described in Cal Newport’s in “A World Without Email”. In fact, programmers seem to already be living in that future utopia of an emailless world. How did it get to be this way? I think this book may have played a major role.

Despite being only a few years removed from computer programs consisting of stacks of cards, high level languages being a new thing compared to assembly language, and changesets being distributed via microfilm, this book, originally published in 1975, outlines a way of developing software that resonates today:

In “The Surgical Team” Brooks outlines the roles required in a software development shop: …

Review of 'The Mythical Man-Month' on 'LibraryThing'

5 žvaigždutės

This book was written in the sixties, yet, I find its recommendations and requirements for software development are just as helpful, humorous and educational in the 21st century. I still don't understand how they got any work done back then with manually teletypes, printed requirements documents being updated everyday and the like, but they still had the exact same problems we do now. returnreturnThe two things I took away most, "the more people you add to a late project, the later the project is." Along with the title of the mythical man month, is the idea "nine women can't make a baby in a month." The other point, was that whatever your estimate is for development time, you need to consider at least twice as much for validation. This is counter intuitive, you develop it once, you test it once, and that test takes less time than writing code did, …

Temos

  • Software engineering