“Complicated isn’t clever. It just looks clever to stupid people.”
Regular readers will have noticed how often l refer to OSS being complicated, too complicated. So if Dave Trott is right, and I do think he might be onto something, then OSS isn’t as clever as l might try to persuade you.
I recall an NMS solution that had enormous power (in theory) and had been created by some seriously bright engineers / analysts / developers. The only problem was that it was pretty close to being unusable.
Part of the problem was that it was managing a network that was convoluted but it also seemed to be designed with a bunch of even more convoluted edge cases in mind rather than streamlining on the common use cases. Was this a case of a solution looking clever to these very clever implementers or were they not so clever for developing a barely useable tool?
It’s an important line of questioning to keep asking ourself in this industry. For example, l recently created an OSS mapping spreadsheet that made perfect sense to me and suited a variety of my needs well. However, it was also needed to articulate a message to a large group of customer representatives. Unfortunately it failed. It was too complicated for them to quickly grasp so l had to hack it back to a much simpler message.
We probably all over-complicate things at times don’t we? I know l can fall into this trap unfortunately. We probably also need to be more forthright in asking others to simplify if we’re to make OSS cleverer too.[And that goes for you if I’m ever getting too complicated here on PAOSS]