Do you recognize your job description?
- Share/Email
- Tweet This
- Print
IT is undergoing one of the most significant transformations in recent memory -- yet most IT practitioners (including telecom
managers) are only dimly aware of what's happening.
Some history: After the Internet went mainstream in the early-to-mid 1990s, networking and infrastructure specialties became
mission-critical. Designing, implementing and operating IP networks, client-server computing systems and storage (including
the newly invented storage networking technologies) were major challenges. Staffs swelled, and IT managers struggled to cope
with challenges around hypergrowth, particularly when it came to rapidly rolling out infrastructure that could scale exponentially.
Meanwhile, telecom deregulation flooded the market with new players touting exotic technologies and business models -- and
the emerging competition brought prices down sharply, for those who knew how to negotiate. (Throughout the late 1990s, telecom
prices dropped an average of 20% year over year).
After the dot-com bust, the economy moved into a period of more moderate growth, and the watchwords for infrastructure teams
were consolidation and optimization. IT folks worried less about fast, scalable buildout, and more about optimizing operations
and reducing total cost of ownership As these efforts proved successful, IT departments began divesting themselves of infrastructure
engineering expertise.
With outsourcing, we're seeing the natural conclusion of that evolution: IT departments are increasingly handing off their
networks to managed services providers. All indications are that the trend will continue for the foreseeable future (the growth
in demand for managed services is hockey-stick steep). Add to that the ongoing trend towards relying on the Internet to connect
remote and distributed workers -- as a full 81% of the IT professionals I work with say they do -- and it becomes clear that
telecom and networking is increasingly about crafting credible service-level agreements, negotiating rock-solid contracts,
and effectively selecting and managing providers.
It may seem like these developments mark the end of the career of the "network engineer". Not at all. As new technologies
come on line, there's plenty of network engineering -- and architecting, design and implementation -- left to do. The trick
lies in understanding the distinctions between technologies that have become commodities (and can therefore be outsourced)
and those that are emerging as strategic differentiators.
Partner Content
Simplify Your Branch Infrastructure
Learn how to simplify your branch infrastructure while dramatically increasing app performance with Citrix Branch Repeater.
Download the Free Info Kit
Next-Gen Load Balancing
Free Guide: "Next Gen Load Balancing: 8 Things You Need to Handle Today's Network Traffic" shows you the functionality needed in your next load balancer.
Download the Free Guide
Accelerate Your Web Apps by up to 5x
Free Guide: "The Secret to Getting Maximum Speed from your Web Applications."' Learn how you can deliver Web apps up to 5x faster.
Download the Free Guide
Comments (1)
RE: Do you recognize your job description?By Anonymous on July 10, 2009, 10:21 amHi, I'm wondering if you don't mind expounding on the mobile bit. We currently in house our cellular voice and mobile data connections. We initially faux paus'ed...
Reply | Read entire comment
View all comments