A Playbook for Modernizing the Mainframe # part 1

Earlier this year, my colleague Sreenivasan Rajagopal blogged on “Cloud comes to Mainframe,” highlighting the incredible opportunities for mainframe if businesses could manage the platform with the same agility as the typical “cloud experience.” This vision resonates incredibly well with my engineering team and our ongoing work to design a DevOps solution for our customers, which happens to be another popular topic that also brings the promise of greater business agility.

Our goal is to bring both the cloud experience and DevOps to mainframe, and to revolutionize how the mainframe is experienced by professionals working in Development and Operations. I am incredibly excited to be sharing the journey of our team, so stay tuned over the coming months as we reveal piece by piece the playbook to modernize development on mainframe.

read further on //bit.ly/2BIeVXQ 

What Broke The Matrix Will Revive The Mainframe Experience # part 2

In the opening blog Why The Time Is Now To Modernize Development On The Mainframe, Jean Louis Vignaud kicks off our blog series with our goal to bring DevOps and “the cloud experience” to mainframe as a means for modernizing development on this mission-essential platform. Three primary stakeholders are critical to realizing a successful modernization effort, and in Part 2 of our playbook I will outline the keys to unlocking the full value of one stakeholder, the modern developer.

Many of the customers I’ve spoken with are undergoing a disruptive generational shift in their workforce. As mainframe experts retire and cede their responsibility over mission-essential applications, businesses are left with the challenge of onboarding a new generation of modern developers. Modern developers are a diverse group, with responsibilities ranging from specialized back-end applications to web/mobile applications that touch the full technology stack. However, despite these differences, all of them share a similar lack of interest in becoming experts on mainframe, and are even less inclined in adopting historical practices established by their predecessors.

read further on //bit.ly/2jdQ9qC