InfoQ

News

"Simple Ain't Easy"

Posted by Deborah Hartmann on Jun 01, 2006 02:03 PM

Community
Agile
Topics
Delivering Value ,
Agile Techniques
Tags
Simplicity
We human beings, so often capable of complex thought, paradoxically also long for something often called "simplicity".  A well known example of deep reflection on the subject is Thoreau's "Walden", published in 1854, a social critique of the Western World examining aspects of humanity that needed to be either renounced or praised.  But this tension is surely as old as man.

In recent decades, the idea has been explored in relation to many domains, including charity, time management, consumerism, and home design.  In concert with this movement, it surfaced in 2001 in the Agile Manifesto:
"Simplicity - the art of maximizing the amount of work not done - is essential"
But the term is somehow deceptive - surely simplicity should be, well, simple?

Brad Appleton has blogged at length on the subject, exploring "Myths and Misunderstandings about Simplicity", including these:
  • Simplicity = "easy to do/understand"
  • Simplicity = "simple to develop/deploy"
  • Simplicity = "good enough!"
  • Simplicity = "simplistic"
Appleton wants to open a dialogue on the subject: his posts on various Agile lists this week invited discourse, asking for people's impressions and commentary - comments can be entered here or on his blog. You will probably also find discussions going on in these newsgroups: ExtremeProgramming, AgileModeling, AgileManagement, ScrumDevelopment, LeanDevelopment or PragProg,

Appleton has pulled together much information, to make this blog entry an excellent resource for those thinking about how to apply simplicity as an Agile tool - he's finished his entry with links to 14 resources on simplicity in software and other types of design, and over 30 famous and pithy quotes on simplicity, including this one, by British mathematician Sir Eric Christopher Zeeman:
"Technical skill is mastery of complexity, while creativity is mastery of simplicity."
The Agile approach invites us to consider which of these is necessary at every moment: technical skill or creativity.  Each is valuable in its own right, and when well balanced against one another and focused on customer goals, both can contribute to the creation of extraordinary business value.

Ah, balance. Therein lies the Agile practitioner's challenge!

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.
True, True by Geoffrey Wiseman Posted Jun 2, 2006 9:18 AM
Simplicity is NOT easy by Jason Carreira Posted Jun 2, 2006 12:08 PM
Re: Simplicity is NOT easy by Floyd Marinescu Posted Jun 2, 2006 1:18 PM
  1. Back to top

    True, True

    Jun 2, 2006 9:18 AM by Geoffrey Wiseman

    This is true in so many human endeavours, from writing a short story, to making an email concise, to making a software system 'simple'. It's often worth the effort, but it certainly isn't easy.

  2. Back to top

    Simplicity is NOT easy

    Jun 2, 2006 12:08 PM by Jason Carreira

    Take the famous Blaise Pascal quote:

    I have made this letter longer, because I have not had the time to make it shorter.
    It takes EFFORT to keep things simple. It's easy to cut-n-paste your way to code-hell, it takes effort to identify opportunities for reuse and refactor out common code. At work a lot of what I do is to encapsulate the complexity of something we're trying to do so that the other team members can use what I've done to very simply solve similar problems over and over again. Take for example XFire. There's a lot going on under the covers, and even understanding it and configuring it is too complex to have to do more than once. But now that it's configured, people on my team can just annotate their classes with an @WebService annotation and the bean will be automatically registered as a web service. Don't let the term "simplicity" fool you. Simple != Easy.

  3. Back to top

    Re: Simplicity is NOT easy

    Jun 2, 2006 1:18 PM by Floyd Marinescu

    Take the famous Blaise Pascal quote:
    I have made this letter longer, because I have not had the time to make it shorter.
    It takes EFFORT to keep things simple. Don't let the term "simplicity" fool you. Simple != Easy.
    I can definitely sympathize with that. Take InfoQ.com for example, the UI was designed to be as simple as possible, but we had to jump through many hoops to get it that way... Even editorially, I spend a long time trying to write news items in as concise a way as possible, to make them as clear and easy to understand as I can. That takes a LOT of effort.

Educational Content

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.