What is your design objective?

by Sajin on July 23, 2009

Increasingly, people remind me of what this gentleman said.

Making the simple complex is commonplace; making the complicated simple, awesomely simple, that’s creativity.
-Charles Mingus

What is it with software folks that make them design everything in layers? So much that 3 layers is so passe these days. “Don’t talk to me if you don’t have at least 7″ is the attitude. And when you take your design to your team, the less one understands the more it is appreciated. Too often you hear comments like, “his designs are great, no one can understand a thing – where the data flows in or where the event gets handled”.

The school of thought that we are here to find a solution and not to implement a technology seems to be fast dying. We are all here to implement the smartest looking permutation of all latest technologies, right? You can look at a technical architecture and predict with a fair degree of accuracy when it was done – not by design maturity or by pattern evolutions, just by looking at the components. You could even say what the agenda of the MSDN forum during that time looked like.

I fully understand there are pressures at times that force you to include certain things as part of your solution, which may not be best for the client. I’ve had an instance where the VP calls you and says “no matter how, product-x should be part of your solution; else it’ll affect our relation with company-x”. Those are not common enough to cause the scenario above though.

I haven’t stopped dreaming of a world where people create solutions and appreciate it for how beautifully simple it is to build and to use. A world where people remember the famous wordpress quote – Code is Poetry.

{ 1 comment… read it below or add one }

Santosh July 23, 2009 at 7:01 pm

Though it appears to be that the simplest thing is to keep things simple, but being simple is not all that simple [:)]

Leave a Comment

Previous post:

Next post: