Thursday, November 01, 2007
Enterprise Architecture and Encouraging Slack...
Slack and laziness are different. Laziness implies not doing the necessary work (or doing it badly) while slack implies doing whatever would save the most effort.
Imagine a project where work (1x) would save work (2x) later. However, (a different) work (2x) would save work (4x) later. The lazy architect would do work (1x). The slack architect would, in order to exert minimal effort, would choose work (2x), to save twice as much energy later. Overall, a slack-principled architect is even "lazier" than a lazy architect. The difference is that the slack-principled architect is less concerned with immediate gain, and more concerned with overall gain.
| | View blog reactionsImagine a project where work (1x) would save work (2x) later. However, (a different) work (2x) would save work (4x) later. The lazy architect would do work (1x). The slack architect would, in order to exert minimal effort, would choose work (2x), to save twice as much energy later. Overall, a slack-principled architect is even "lazier" than a lazy architect. The difference is that the slack-principled architect is less concerned with immediate gain, and more concerned with overall gain.
