Tuesday, 13 September 2011

Making things complex

System complexity has little to do with the nuts and bolts of an application.
Take for instance the use of the modern car. You can literally have a start/stop button, the steering wheel and the gas and brake pedals and no other control is necessary to rum the car. Gear changing, lights, wipers are all automatic in higher end cars.
So the fact there maybe 10th individual software apps underneath mean nothing to most administrators of a system. If it has a simple operation and a sensible setup then the system is not complex.
Which brings me to my second point. The last thing you need to care about with a system is wondering if you are on the right one.  A half broken system is worse than a broken one. Trying to work around "features" is so annoying I would rather not use it at all. Even worse is working around self induced issues.
Maintain what you have more than work on new systems you have, and stand on your principles if those that be tell you to do otherwise.
And thus ends today's lesson

No comments: