Frameworks should stay invisible

Imagine a building under construction. You see the props jutting out buzzing with construction activity. Unfinished pillars and floors cast a gaudy look. This is how anything under work-in-progress looks like. In the IT side this stage is the beta versions.

Imagine a broken traffic signal and the ensuing chaos on the road. Long disorderly queues of vehicles is a common sight. You become aware of the vehicles around you, the road infrastructure including the traffic lights, enforcement mechanisms come into vision. In the IT side this likens to a system gone into maintenance mode.

In the two examples above we become aware of the frameworks that hold things together. The former because it is work-in-progress and the latter because it is broken.

Now imagine you walk into your office and your devices automatically connect to the wifi network and you are connected to the Internet. Your device seamlessly switches from the telco network to the corporate network. Besides the Internet you are able to access all the Intranet sites without a need to login to a VPN (Virtual Private Network). All of the above normally happens without you noticing it.

This is a framework-in-action. It is invisible. It masks the complexity. It is seamless and simple to use. It demands very little or no attention from the user.

Contrast this with the two cases above where the framework comes into view. Frameworks should stay invisible.

A working framework should have the following qualities.

  • Adopts (or stays agnostic) to the consumers' disposition
  • Autonomous for most part demanding the least effort from the users
  • Covers all possible scenarios and environmental conditions and has a predictable exception handling mechanism

Popular posts from this blog

The Digital Ecosystem Blueprint

Complexity impedes Security