Traditionally, infrastructure is the backbone of the company. It is vital to all systems and applications for the company.
Some companies thought it is not that important. Some says it is very important but will not invest one more penny. When blaming on bad quality of network no matter LAN or WIFI connections, can't you see what had been bought for your infrastructure.
In the network arena, there are different brands for different classes of company. You can buy different brands, with different standard of quality. Some brands are specifically strong on particular area, and they are weak on particular area. You know what you are buying.
But are you prepared for suffering the weakness? The responsibility, of course shifted to relevant team, infrastructure team, because the team is paid for dealing with all these 'sufferings'. True, very true. But also sad enough. If the team is large, there are plenty of resources to deal with all those hiccups. How about small team? Especially those are exceptionally small when comparing with the size of the company without outsourcing practice.
And, when there are many misconception from all different IT teams, the scenario is much worse. Why did other IT teams think infrastructure team are all superheros? Infrastructure team knew all IT stuff?? The team knew how-to design software architecture, database administration, debugging, security architecture, etc. Maybe it is a norm and also the real role of infrastructure team.
Or, maybe only the teammate in infrastructure team thought the team size is too small. Maybe only infrastructure team thought budget was never enough. Maybe only infrastructure team thought good brands products with higher cost were better. Maybe all negativity arose were fake. Maybe all were because of laziness. Maybe the team deserved to be burnt out. Who knows.
No comments:
Post a Comment