Isolated failure

I wouldn’t call myself a developer by any definition, but in my line of work I stay in touch with what they are doing and how they do it.

I’m beginning to understand a concept called ‘isolated failure’ and how important it is for the end user to have a good experience.

In a nutshell most applications are a pile of functions that work together to create a user experience. Engineers and developers would prefer that if one of these functions breaks that it didn’t bring down the whole application. Makes sense.

But I think in terms of people and churchie stuff…I can’t help it, I’m a pastor.

Isolated failure seems like a good idea on the surface for a church (application). And I have been a part of churches that value it. When a leader (function) breaks, it doesn’t bring down the whole institution.

This is the best way to operate if the institution is the highest good. But it’s not.

This would be the best way to operate if it mattered that each user had a good experience instead of seeing the dirty truth.

But it’s not about the institution. It’s about Jesus.

It’s not about candy coated reality. It’s about the truth.

{photo | Behrooz Nobakht}