<$BlogRSDUrl$>

Wednesday, October 04, 2006

Innovation thru constraint 

Sean McGrath
I see two ways to rationalize this. The first via philolinguistics. It could be that the very definition of innovation in the world of computing includes the idea of suceeding in the face of some constraints. After all, this is (for the most part) a real-world engineering discipline right? You know the drill: "time, cost, quality. Pick two." We eat and drink constraints in engineering. It is what makes engineering, engineering. Put another way, if there are no constraints, it ain't engineering. I can buy that.

The second way to rationalize it is the apparent truism that necessity is the mother of invention. Ingenuity appears to be boosted by the sort of strictures that plague our daily engineering lives. At least it is in the case of those engineers that posess that most precious of all engineering personaility traits - a "can do" problem-solving mentality.

So it would appear that constraints are good. This leads, of course, to the curious phenomenon whereby the very things that cause innovation to happen are the things that the innovators themselves moan about the most. I sure wish I had a supercomputer under my desk. I sure wish I had 4 gig of RAM, twice as many pixels, a faster hard disk, a quicker internet connection...

And now comes my horrible, tentative conclusion. The best way to foster innovation in an engineering crew is to give them a set of constraints. If they are not moaning about the constraints, keep adding them until they start moaning. Then you have created a wellspring for innovation to happen.

Topics: Architecture | Representation


Links to this post:

<\$BlogItemBacklinkCreate\$>

Comments: Post a Comment

This page is powered by Blogger. Isn't yours?