Over the number of years I have dealt with various developers/programmers as well as Architects, some of them being brilliant, some of them being very hardworking and some of them being just Nine to Five type of material. However, one thing that I have found common in most of the people I deal with or have dealt with, is the habit of putting their resume before requirements.
We being engineers have the tendency to look at everything from engineering glasses and often end up finding faults in other people work, designs and suggestions. A constructive criticism is good and is very healthy to get the output that is beneficial for all, however, tendency to recommend technologies or different approaches to solve problems often arises from that deep down urge of reflecting them on to the CVs or justifying what’s already in there.
As an architect, you have a moral obligation to be unbiased towards any technology or recommendation. The solution should always be driven by the requirements which can make an organisation happy and in turn it’s customers. As an architect, it’s your duty to educate business and fellow technology colleagues about the right choice and why it should be made.
IT industry is very rapidly changing and technologies keep getting better. In this IT world where there are N ways to solve a given problem, architects often get inclined towards the new and cool stuff. This inclination can be justified to a certain extent, however it doesn’t mean it can solve all the problems you are trying to solve just by using a new cool tech or a new buzzword in the market. Hence, Architects should be cognisant of the fact that in IT world one size doesn’t fit all.
If you are an architect or planning to take that route, make sure you keep this thumb rule in mind before everything else and you would be successful in your endeavours.