Monday, March 12, 2007

Middleware and Complexity

I still have an interest in lessconfig as an idea. Sensible defaults, user-centered but system-aware design, all those things are still goals.

But now I work for a telecoms middleware company. Almost my entire working life is now taken up with...configuration. The whole reason for Sigma Systems' product's existence is configuration -- we accept orders as input, and issue network configuration commands as output. And since this is an Enterprisey kind of environment -- you don't become a successful enough telecom to warrant OSS without very very high uptime and you don't get very very high uptime without significant quantities of process -- there's lots of configuration in our application too. Configuration, metaconfiguration, metametaconfiguration -- it's easy to lose sight of what the system's actually going to be used for in the end.

And I'm not sure I can see how any of this could be simplified, in practice, without either ending up with a dangerous monoculture effect in the telecoms industry or a decrease in available services.

Some problems are just hard, I guess.


Post a Comment

<< Home