skip to main content
research-article

The Tower of Babel did not fail

Published:17 October 2010Publication History
Skip Abstract Section

Abstract

Fred Brooks' retelling of the biblical story of the Tower of Babel offers many insights into what makes building software difficult. The difficulty, according to common interpretations, comes from the communication and organizational problems in software development. But the story contains one more important lesson that people tend to miss: one cannot accomplish impossible goals, which programmers are often asked to do. Software engineering, as a discipline, can overcome poor communication; but as long as we attempt to live up to impossible expectations, we will always fail.

References

  1. }}--, Once And Only Once. Available at: http://c2.com/cgi/\\wiki?OnceAndOnlyOnce.Google ScholarGoogle Scholar
  2. }}--, What is 80/20 rule? Available at: http://www.80-20pre\\sentationrule.com/whatisrule.html.Google ScholarGoogle Scholar
  3. }}Kent Beck. Extreme Programming Explained: Embrace Change, Addison Wesley, 2000. Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. }}T. Berners-Lee. The World Wide Web: A very short personal story. Available at: http://www.w3.org/People/Berners-Lee/ShortHistory.html.Google ScholarGoogle Scholar
  5. }}Fred P. Brooks. The Computer Scientist as a Toolsmith II, Communications of the ACM, March 1996. Google ScholarGoogle ScholarDigital LibraryDigital Library
  6. }}Fred P. Brooks. The Mythical Man-Month, Anniversary Edition, Addison Wesley, 1995. Google ScholarGoogle ScholarDigital LibraryDigital Library
  7. }}Fred P. Brooks. Three Great Challenges for Half-Century-Old Computer Science, Journal of the ACM. January 2003. Google ScholarGoogle ScholarDigital LibraryDigital Library
  8. }}Fred P. Brooks. The Design of Design: Essays from a Computer Scientist, Addison Wesley, 2010. Google ScholarGoogle ScholarDigital LibraryDigital Library
  9. }}Bush, V. As We May Think. The Atlantic Monthly, July 1945.Google ScholarGoogle Scholar
  10. }}Buxton, J. N. and B. Randell, eds. Software Engineering Techniques, April 1970, p. 21. Report on a conference sponsored by the NATO Science Committee, Rome, Italy, 27-31 October 1969.Google ScholarGoogle Scholar
  11. }}Cockburn A. and L. Williams. The Costs and Benefits of Pair Programming, Proceedings of eXtreme Programming and Flexible Processes in Software Engineering, XP2000.Google ScholarGoogle Scholar
  12. }}Connell, C. Software Engineering ` Computer Science, Dr. Dobb's High Performance Computing, June 04, 2009. Available at: http://www.drdobbs.com/hpc-high-performance-computing/217701907.Google ScholarGoogle Scholar
  13. }}Cusumano, M.A. Factory Concepts and Practices in Software Development: An {sic} Historical Overview. Working Paper #3095--89 BPS. Sloan School of Management, MIT, 1989.Google ScholarGoogle Scholar
  14. }}DeMarco, T. Software Engineering: An Idea Whose Time Has Come and Gone? IEEE Software, July/August 2009. Google ScholarGoogle ScholarDigital LibraryDigital Library
  15. }}Evans, E. Domain Driven Design: Tackling Complexity in the Heart of Software, Addison Wesley, 2004. Google ScholarGoogle ScholarDigital LibraryDigital Library
  16. }}Gamma, E., R. Helm, R. Johnson, and J. Vlissides. Design Patterns: Elements of Reusable Object-Oriented Software, Addison Wesley, 1994.Google ScholarGoogle ScholarDigital LibraryDigital Library
  17. }}George, A. R. The Tower of Babel: Archaeology, History and Cuneiform Texts Archiv fur Orientforschung, 51 (2005/2006). pp. 75--95. Available at: https://eprints.soas.ac.uk/3858/.Google ScholarGoogle Scholar
  18. }}Greenfield, J., K. Short, S. Cook, and S. Kent. Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools. Wiley, 2004. Google ScholarGoogle ScholarDigital LibraryDigital Library
  19. }}Herbsleb, J. Beyond Computer Science, Proceedings of the 2005 (27th) International Conference on Software Engineering. Google ScholarGoogle ScholarDigital LibraryDigital Library
  20. }}Jackson, M. Problem Analysis Using Small Problem Frames, South African Computer Journal 22; Special Issue on WOFACS'98, pp47--60, 1999.Google ScholarGoogle Scholar
  21. }}Knuth, D. E. Computer programming as an art. Communications of the ACM. Volume 17, Issue 12 (December 1974). Google ScholarGoogle ScholarDigital LibraryDigital Library
  22. }}Knuth, D. E. Literate Programming. The Computer Journal. Volume 27(2), pp 97--111, 1984. Google ScholarGoogle ScholarDigital LibraryDigital Library
  23. }}Lamb, D. A. and K. A. Schneider. Formalization of information hiding design methods, CASCON '92: Proceedings of the 1992 conference of the Centre for Advanced Studies on Collaborative research. Google ScholarGoogle ScholarDigital LibraryDigital Library
  24. }}Mahoney, M. Software Evolution and the Moving Picture Metaphor, Proceedings of the Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA 2009). Google ScholarGoogle ScholarDigital LibraryDigital Library
  25. }}McCullough, D. The Path Between the Seas: The Creation of the Panama Canal, 1870--1914. Simon & Schuster, First Edition, 1978.Google ScholarGoogle Scholar
  26. }}Mitchell, C. Guest View: The half-agile path leads nowhere. SD Times, March 15, 2010. Available at: http://www.sdtimes.com/GUEST VIEW THE HALF AGILE PATH LEADS NOWHERE/By CYNDI MITCHELL/About AGILE/34197.Google ScholarGoogle Scholar
  27. }}Naur, P. Programming as Theory Building, North Holland Publishing Company, Micropocessing and Microprogramming 15 (1985) 253--261.Google ScholarGoogle ScholarCross RefCross Ref
  28. }}Parnas, D. L. On the Criteria To Be Used in Decomposing Systems Into Modules, Communications of the ACM, Dec. 1972, Vol. 15, No. 12. Google ScholarGoogle ScholarDigital LibraryDigital Library
  29. }}Parnas, D. L. Software Aging, Invited Talk, International Conference on Software Engineering, 1994. Google ScholarGoogle ScholarDigital LibraryDigital Library
  30. }}Parnas, D. L. Software Engineering: An Unconsummated Marriage, Communications of the ACM, Sept. 1997, Vol. 40, No. 9. Google ScholarGoogle ScholarDigital LibraryDigital Library
  31. }}The Standish Group, CHAOS Summary 2004. Available at: http://www.softwaremag.com/L.cfm?doc=newsletter/2004-01-15/Standis.Google ScholarGoogle Scholar
  32. }}The Standish Group, CHAOS Summary 2009. Available at: http://www1.standishgroup.com/newsroom/chaos_2009.php.Google ScholarGoogle Scholar
  33. }}Waldo, J., G. Wyant, A. Wollrath and S. Kendall. A Note on Distributed Computing, Sun Microsystems Technical Report SMLI TR-94-29, November 1994. Google ScholarGoogle ScholarDigital LibraryDigital Library

Index Terms

  1. The Tower of Babel did not fail

        Recommendations

        Comments

        Login options

        Check if you have access through your login credentials or your institution to get full access on this article.

        Sign in

        Full Access

        • Article Metrics

          • Downloads (Last 12 months)3
          • Downloads (Last 6 weeks)1

          Other Metrics

        PDF Format

        View or Download as a PDF file.

        PDF

        eReader

        View online with eReader.

        eReader
        About Cookies On This Site

        We use cookies to ensure that we give you the best experience on our website.

        Learn more

        Got it!