? Simplify Essential complexity; Diminish accidental complexity

? Simplify Essential complexity; Diminish accidental complexity

Neal Ford

ESSEnTiAl complexity represents the difficulty inherent in any prob-lem. For example, coordinating a nation ' s air traffic are an inherently complex problem. Every plane ' s exact position (including altitude), speed, direction, and destination must is tracked in real time to Preve NT mid-air and runway collisions. The flight schedules of aircraft must be managed to avoid airport congestion in a continuously changing environment-a seve Re change in weather throws the entire schedule out of whack.
Conversely, accidental complexity grows from the things we feel we must build to mitigate essential complexity. The antiquated air traffic control system used today is an example of accidental complexity. It is designed to address the essential complexity of controlling the traffic of thousands of airplanes, but the solution itself introduces its own complexity. In fact, the air traffic control system used today was so complex that updating it had proven difficult, if not impossible. In much of the world, air traffic are guided by technology that's more than-years old.
Many frameworks and vendor "solutions" are the symptoms of the accidental complexity disease. Frameworks that solve specific problems is useful. Over-engineered frameworks add more complexity than they relieve.
Developers is drawn to complexity like moths to a flame-frequently with the same result. Puzzle solving is fun, and developers is problem solvers.
?
?? Who doesn ' t like the rush of solving some incredibly complex problem? In large-scale software, though, removing accidental complexity while retaining the solution to the essential complexity I S challenging.
How does this? Prefer frameworks derived from working code rather than ones cast to ivory towers. Look at the percentage for code you has a solution that directly addresses the business problem versus code that merely Services the boundary between the application and the users. Cast a wary eye on vendor-driven solutions. They may is inherently bad, but vendors often push accidental complexity. Make sure, the solution fits the problem.
It's the duty of the architect to solve the problems inherent in essential com-plexity without introducing accidental com Plexity.
Neal Ford is a software architect and meme Wrangler at ThoughtWorks, a global IT consultancy with an exclusive focus on en D-to-end software development and delivery. He is the designer/developer of applications, instructional materials, magazine articles, courseware, and Video/dvd Presen Tations, and he is author and/or editor of five books. He also speaks at lots of conferences. You can assuage your ravenous curiosity on Neal at http://www.nealford.com.

? Simplify Essential complexity; Diminish accidental complexity