There is necessary complexity, and unnecessary complexity. Point (1) is the latter - if you subscribe to enterprise architecture theory, then your enterprise architecture would describe what your business needs to do, and whether it's automated (IT) or manual processes+people, or whatever. Then you don't build anything unnecessary, and avoid unnecessary complexity.
Point (2) is the former. If the world wants cheap air travel (hence Airbus A380s, or Boeing 787s or whatever), or $250 computers, or aircraft carriers, then that's only going to be provided by large, complex organisations. -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Monday, 25 February 2013 10:57 PM To: NT System Admin Issues Subject: Re: MS Azure cloud evaporates On Sun, Feb 24, 2013 at 8:31 PM, Ken Schaefer <k...@adopenstatic.com> wrote: > In large, complex environments, with lots of moving parts, things go > wrong. ... Unfortunately, I don't know the answer to making it all > work. Well, as has been noted, one mechanism that's been proven to work well is to avoid complexity and seek simplicity. Unfortunately: (1) Most of the IT world is addicted to complexity. We love to build ever-bigger toys. (1)(a) Case in point: Most of these so-called "cloud" solutions add large amounts of highly-coupled, low-cohesion moving parts. (2) Large orgs are by definition complex, and they don't seem keen on the idea of committing suicide for the greater good. (Also, teenagers these days drive too fast, and need to stay off my lawn.) -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
