Use the KISS principle!

It frightens me when I see how often technology is chosen over function. The “Keep It Simple, Stupid” principle is often mentioned, but eager architects can’t seem to understand it.

In my experience, failure in IT projects occur when an over ambitious architect meets a technically challenged boss. “Why do we need CLOUD/SOA you ask? To integrate with legacy systems!”
But often there is no legacy systems, the perceived benefits are never realized. People should stop solving problems they don’t have. SOA is just another way of solving problems. Great if there are integration problems to deal with, otherwise its just a way of transferring all your money to the pockets of software vendors (Oracle and Microsoft, I’m looking at you).
I warn often and early that businesses should start by examining needs, and establish criterias for success. What should the system be capable of? Which benefits does it offer? And most importantly, what is the simplest possible way of achieving it?
That would be the cheapest and likely the best solution.
It frightens me when I see how often technology is chosen over function. The “Keep It Simple, Stupid” principle is often mentioned, but eager architects can’t seem to understand it.
I am often referred to as an IT architect, but I feel qeasy about the term, after seeing the work of other architects around.

Lars Andersen, Owner Rimfaxe ApS