Second-system effect
From HandWiki
Short description: Project management phenomenon
The second-system effect or second-system syndrome is the tendency of small, elegant, and successful systems to be succeeded by over-engineered, bloated systems, due to inflated expectations and overconfidence.[1]
The phrase was first used by Fred Brooks in his book The Mythical Man-Month, first published in 1975. It described the jump from a set of simple operating systems on the IBM 700/7000 series to OS/360 on the 360 series, which happened in 1964.[2]
See also
- Anti-pattern
- Feature creep
- Inner-platform effect
- Osborne effect
- Sophomore slump
- Unix philosophy
- Examples in information technology: IPv6 deployment, Taligent, Workplace OS, Copland, Rhapsody
References
- ↑ Raymond, Eric. "Second-system effect". The Jargon File. http://catb.org/jargon/html/S/second-system-effect.html.
- ↑ Brooks Jr., Frederick P. (1975). "The Second-System Effect". The Mythical Man-Month: essays on software engineering. Addison Wesley Longman. pp. 53–58. ISBN 0-201-00650-2. https://archive.org/details/mythicalmanmonth00broo/page/53.
External links
- Spolsky, Joel (April 6, 2000). "Things You Should Never Do, Part I". https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/.
- Turoff, Adam (August 21, 2007). "Notes on Haskell". https://notes-on-haskell.blogspot.com/2007/08/rewriting-software.html.
- Gunton, Neil (July 20, 2008). "Rewrites Considered Harmful?". https://www.neilgunton.com/doc/?o=1mr&doc_id=8583.
- Chad Fowler. "The Big Rewrite". http://chadfowler.com/2006/12/27/the-big-rewrite.html.
 |  |
