Skip to main content

Book: The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)

The Mythical Man Month comes with a big reputation attached.

The books was originally written in 1975. The author (Frederick P. Brooks, Jr) is a prominent Computer Scientist and software engineer, who most notably managed the development of the IBM OS/360 operating system. To quote Wikipedia, “the book is widely regarded as a classic on the human elements of software engineering”.

Honestly this was, for me, a difficult one to read. It's a little bit like trying to read the Bible in some parts (which personally, I find tough going). But I would say it is well worth it. In reading this book, I can see that Brook's writing has had an influence on almost every other serious piece of literature on the management and practice of software engineering that I have ever encountered.

The book is entitled “Essays on Software Engineering” and that's what it serves up. The chapters of the book are arranged in some sort of order, but really they're fairly distinct. The first few chapters are introductory and the last few tie a conclusion together, however for the most part you could practically select a chapter such as “Hatching a Catastrophe” (deals with software project schedules and the black art of software estimation) and read it stand-alone comprehensibly.

So, all that's left really is to provide a couple of thoughts as to where the book shined, in my opinion. There were many more sections which I thought were enlightening, these are a random few which I noted:

Brooks is strong on specification and design up-front, in the same way that Joel Spolsky is. Chapter 6 “Passing The Word” goes into detail on specification.

On page 155, in the “Hatching a Catastrophe” chapter, Brooks says “A baseball manager recognizes a nonphysical talent, hustle, as an essential gift of great players and great teams. It is the characteristic of running faster than necessary, moving sooner than necessary, trying harder than necessary. It is essential for great programming teams, too. Hustle provides the cushion, the reserve capacity, that enables a team to cope with routine mishaps, to anticipate and forfend minor calamities. The calculated response, the measured effort, are the wet blankets that dampen hustle”...I love it!

In Chapter 1, “The Tar Pit”, there is a section on “The Joys of the Craft” and then one on “The Woes of the Craft”. I find these sections to put into words, my feelings regarding software development. I won't type the sections out (cause they're long!), but if you get the chance, read them. Anyone who's ever known the elation of writing even the tiniest program and watched it bring a machine to life in some way will be able to relate to these passages. The only other way that I could express the feeling is to say that it's something like this (Tom Hanks “creates fire”, in Castaway):


Finally, I think the following excerpt from near the end of the book captures the essence..."[the book] is only incidentally about software but primarily about how people in teams make things".

So that's it. In summary, a difficult read, but well worth the effort in my opinion.

Title: The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)
Author: Fredrick P. Brooks, Jr
Link: Amazon
Tags: Book, Fredrick P. Brooks, Project Management, Software Development, Software Engineering



Comments

Popular posts from this blog

HOW-TO: Apply a “baseless merge” in Team Foundation Server 2010 (and 2012)

Another purely technical post on TFS...
The scenario We wish to migrate code between branches that do not have a branch/merge relationship, in order to expedite urgent changes being made by a project team, without disrupting on-going BAU development work. Sample branch hierachy/strategy Imagine the following branching strategy in TFS (visible by connecting to TFS via Visual Studio 2010 or 2012):

Essentially you have a "DEV" branch, which has a "QA" branch, which in turn has a "PROD" branch. DEV is the branch that you would be using for BAU development. As a piece of development matures, you move it into QA, where it is tested by your internal QA team. There may be further changes made in DEV that are moved into the QA branch as the QA team pick up issues. Once the QA team are happy with a packaged of changes, they will move them into PROD, which is essentially the hand-over to the customer. The PROD branch represents the software that the customer has.

Mo…

HOW-TO: Add/edit a field in Team Foundation Server 2012 using Visual Studio 2012

It's been a while since I made a purely technical post...

So, today I wanted to make a change to a Microsoft Team Foundation Server 2012 (TFS2012) instance that I am working with to reflect "Actual" time spent on a task - mainly for reporting purposes, and because I have found in the past that making this minor process adjustment yields a relatively useful metric over the long-term.

I am using the Microsoft Scrum 2.1 Process Template (http://msdn.microsoft.com/en-us/library/vstudio/ff731587.aspx) for a project that I am working with. So that I don't forget how to do this (again!) I will blog-post the procedure I've used to add this field to the template as a screen-shot-based tutorial, as follows...
Before Assuming you are familiar with the Scrum Process Template (2.1-ish) - open a task and take a look at the "Details" section, as follows:


 This is where I want my "Actual" field to show up.
Get the Power Tools Download and install the latest v…

Eclipse/Android error: "Multiple dex files define [...]"

Wow, I am really going nuts blogging this-evening - 2nd post in less than an hour. 


Anyway this is a particularly nasty error that I keep running into with Eclipse/Android when starting the emulator after I have not run it for a little while. Since I run the risk of permanently forgetting the solution to the problem every time I walk away from my Android project (and thus having to spend a painful hour-or-so digging up the procedure again), I will blog it here, for my benefit, and for the benefit of anyone who may also suffer the same problem.


The gist is that when you start the emulator in debug mode (that is, you hit the button in the following image), you get the following error message come out on the console and a nasty popup telling you nothing more than there is an error with your program and you need to fix it:








[2012-04-06 23:20:57 - Dex Loader] Unable to execute dex: Multiple dex files define Lcom/google/gson/ExclusionStrategy;
[2012-04-06 23:20:57 - SimpleList] Conversion to Dal…