DEVNET-1115 Learning@Cisco: Developers + IT Professional: The Future of the IT Workforce

Editor's Notes

• #5: Each business organization is doing things differently - shifting roles, shifting skills and shifting expectations - and these organizations must respond to their digital customers and the reality of the IOE Enterprises must use all available technologies – e.g., social, mobile, cloud… -- that enable the agility, scaling, and security necessary to meet customer, partner, employee expectations. Let’s take a closer look at IT because that’s where a lot of the critical shifts and skill gaps are happening, plus IT is near and dear to everyone’s hearts here ;) Here, the shift is away from deploying and operating systems and towards provisioning and orchestrating services. IT is more concert than collection into the future. And the success of these services and satisfaction with this concert is dependent on a skilled workforce operating together. In the next slides, you’ll see just how serious some of these IT job shortages are and will become
• #6: Massive, global-scale change occurring at rates faster than could ever be predicted top 10 jobs in 2010 did not exist in 2004: ie: Social Media/Online Manager, Elder Care Services, Sustainability Manager, SEO Optimization Specialist, Online Advertising Manager, User Experience Manager http://www.forbes.com/sites/meghancasserly/2012/05/11/10-jobs-that-didnt-exist-10-years-ago/ Source: IT Career Finder, ‘Best Computer Jobs for the Future’, May 2012, http://www.itcareerfinder.com/brain-food/blog/entry/best-computer-jobs-for-the-future.html Source: Info World, The 6 hottest new jobs in IT, June 2011, http://www.infoworld.com/t/information-technology-careers/the-6-hottest-new-jobs-in-it-052?page=0,0   Source: Modis as quoted in Network World, ‘10 hottest IT jobs: Developers, developers, developers’, August 2013,  http://www.networkworld.com/news/2013/081613-hottest-tech-skills-jobs-272921.html?source=NWWNLE_nlt_daily_pm_2013-08-16   Source: Bureau of Labor Statistics, April 2013, http://www.bls.gov/opub/btn/volume-2/careers-in-growing-field-of-information-technology-services.htm
• #8: Jeanne – This slide is not exactly what you wanted. Graphics team made each section equal. I will fix to show relative weight.
• #9: DevOps requires cross-organizational coordination and communications, thus necessitating an organizational style that fosters collaboration.” Organize the Right Teams for Successful DevOps, Gartner IDC predicts that by 2018, 90% of IT roles will be redefined. DevOps also drives workers to operate with a big picture view of not only technology, but also business. For the Adminsitrator, no longer are they concerned with only the network… or the servers… or the data center… or the database… They are concerned about the whole system – and the outcome delivered to the end user. For the Application developer, no longer are they operating in a vacuum, where program input and outputs are simply matched to basic work functions. In the DevOps envionment, developers are more in the underlying infrastructure and more wide-scale workflows and outcomes. For the Architect, no longer are they concerned with just laying a solid network or an efficient data center. They are concerned with the whole system as it relates to driving the best possible business outcomes. For the Analyst, no longer are they only concerned with system efficiency and business support. They are focused on system agility and the ability for systems to improve – not jus serve -- business processes.
• #16: Transcript: Another important question that comes to mind is we say very optimistically that onePK is a tool kit that enables you to write applications. And I'm sure that when I say that, you all think, well, me? Am I going to write applications? Should I start learning how to write code? And I think that some of us will. But today, having talked to lots of people, I think that amongst ourselves and among our customers, that there turns out to be, still, a pretty big divide between two classes of people. The first, obviously, is the network engineer. These are the people we're used to talking to and working with. And if you look at the skills matrix, they're really strong on networking skills, on IOS skills. And most of the experienced ones will have some form of scripting experience. Maybe it's Unix shell scripting. Maybe they've done a little TcL, Expect, that sort of thing. But really probably either a very small amount or no programming experience in terms of being able to write and compile, say, a C program. This kind of person will still be absolutely essential in a world that is enabled by onePK, because they have the networking skills. And we have to start thinking about ourselves now as requirements engineers in addition to network engineers. So we generate requirements, because we can understand how the network operates and what it needs. To go back to that first big category that I talked about of use cases in terms of simplified operations, nobody knows what we need to do to simplify operations better than the network engineers. So that they can define those use cases. We'll also be able to use scripting skills to be able to do the rapid prototyping of these ideas, even if we don't, maybe necessarily, write the final end application. But there is another class of people that we will have to start talking to, understanding, and working with in the brave new world of programmable network. And that is, obviously, the application developer. Low on networking and IOS skills. It may be to them, a network is just a socket that they program to, and the rest of it is just a big black box. Probably stronger on scripting skills and obviously very strong when it comes to programming. As far as being requirements engineers, they can participate too, because they understand the needs of the applications. So they can define in very great detail what the network should be doing to respond to those applications. They also understand, ultimately, how to write scalable, highly available applications. So I've met a very few people-- they exist-- that bridge this gap, who are excellent network engineers and also very good software developers. But there are not a lot. And I think for the foreseeable future, what we need to be thinking about is, how do we enable ourselves to talk to both sets of people? And then how do we enable them to talk to each other in order to define and implement the use cases that we identify today? Author's Original Notes: