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:
Brad Appleton has blogged at length on the subject, exploring "Myths and Misunderstandings about Simplicity", including these:
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:
Ah, balance. Therein lies the Agile practitioner's challenge!
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 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!
Community comments
True, True
by Geoffrey Wiseman,
Simplicity is NOT easy
by Jason Carreira,
Re: Simplicity is NOT easy
by Floyd Marinescu,
True, True
by Geoffrey Wiseman,
Your message is awaiting moderation. Thank you for participating in the discussion.
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.
Simplicity is NOT easy
by Jason Carreira,
Your message is awaiting moderation. Thank you for participating in the discussion.
Take the famous Blaise Pascal quote:
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.
Re: Simplicity is NOT easy
by Floyd Marinescu,
Your message is awaiting moderation. Thank you for participating in the discussion.
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.