Planned Obsolescence for IT Architecture/Design

One of the common dilemmas that IT Architects face is of long-term vs. short-term solutions. Finding the right mix is more an art than trade. Can IT Architects take inspiration from other disciplines?

The answer is a resounding yes. Although for completely different (and often mean profit oriented reasons) the electronic industry implements ‘planned obsolescence’. Chip manufacturers have been known (infamously) to have devices have higher rates of failure after a certain period of time. The wry with mystic reports of phones starting to fail near the telecom contract providers contract expiry date.

Can’t we implement ticking alarms in our code and/or design so that the system start to fail (or call for attention) if a long term solution does not replace a short term solution within a stipulated amount of time?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s