The Mythical Man Month is a classic book on software engineering by Fred Brooks. The book is often cited as being the only book you ever need to read on software engineering. If you're going to commission a large software project then the information within this book is invaluable.
Brooks developed his theories of software engineering while working at IBM. At the time it was common practice when planning software development projects to assume that a given job took a given amount of man-months to complete. For example a 12 man-month job could be completed in 12 months by one man, and therefore it could be completed in 6 months by two men and so on.
Following on from this belief it was generally considered that if a software project was running late the way to get it back on schedule was to add more manpower to job. Brooks' observation based on a wide range of projects that he managed at IBM was that in fact the opposite was true. This is summed up by Brooks's Law: Adding manpower to a late software project makes it later. The idea of a man-month, a unit of work that can be completed in one month by one man is a myth - and hence the title of the book.
Brooks's Law was arrived at empirically, via observation of projects he worked on, however the book goes on to explore the underlying reasons for the law. The central reason is that a programming task of any significant complexity cannot be perfectly partitioned into discrete tasks that can then be worked on and solved by individuals working in isolation. In other words beyond a certain number of workers on any task, the amount of communication and coordination required between the workers starts to increase exponentially.
A secondary reason for Brooks's Law is that as more workers are added to a software project the amount of time required to get workers up to speed on the state of the project also increases. This is because of the unique nature of individual software projects. Unlike many engineering projects which tend to follow variations on well trodden patterns and themes, the rate of development within the software industry means most projects involve new tools, technologies or design principles which will not be immediately familar to all developers.
A wide range of software development techniques have been developed over the years to try to counter the issues raised by The Mythical Man Month. You may hear phrases such as RAD, Waterfall, Agile etc when discussing software development projects. All of these techniques aim to minimise the risk associated with developing software in different ways. We may look at how some of these work in future posts.
We've recently been having a lot of fun exploring the power of Microsoft Cognitive Services for a project we are working on. Microsoft Cognitive Services are part of Microsoft's Cloud offering (also known as Azure). The services are split down
In 2016 Google made a pledge, to name and shame all website with unencrypted connections. They have now followed through. A few days ago Google began to show a "Not Secure" warning next to the the URL bar for all
Many clients come to us looking for a database application. But what is a database application exactly, and how does it differ from other applications? The main feature of a database application is that it is primarily concerned with creating, updating
Many web applications require some sort of reporting functionality. One of the most powerful frameworks for developing complex reports is Microsoft's SQL Server Reporting Service (SSRS). Webfuel web applications use SSRS to deliver complex reporting functionality for our clients. Developing