Great post. Tell me if you disagree, I work really hard to convince myself complexity is mandatory before I even attempt to tame it in the first place. It’s almost as if taming complexity is the last resort.
When gathering the business requirements from my clients, I often feel overwhelmed by information. Example of what a client might say, “I want a very simple application that integrates with facebook, manages shipping orders, plugs in HTML 5 games and launches missiles at Moscow at the midnight of every full moon”. Umm..maybe I exaggerated that a bit, but that’s definitely how I feel most of the time. First order of business, get rid of complexity: do we really need to launch missiles at moscow at midnight of every full moon?
Tame complexity as a last resort. I’d start any blog post with that. Am I wrong?
John
Great post. Tell me if you disagree, I work really hard to convince myself complexity is mandatory before I even attempt to tame it in the first place. It’s almost as if taming complexity is the last resort.
When gathering the business requirements from my clients, I often feel overwhelmed by information. Example of what a client might say, “I want a very simple application that integrates with facebook, manages shipping orders, plugs in HTML 5 games and launches missiles at Moscow at the midnight of every full moon”. Umm..maybe I exaggerated that a bit, but that’s definitely how I feel most of the time. First order of business, get rid of complexity: do we really need to launch missiles at moscow at midnight of every full moon?
Tame complexity as a last resort. I’d start any blog post with that. Am I wrong?