John MacMillan, Pennsylvania CIO<\/b><\/p>\n
It\u2019s based on the idea that the minute a service or a system or application goes live, it\u2019s immediately legacy. Now you start into productive service and realize all the things you didn\u2019t think about are like warts on a toad: they\u2019re plainly obvious and now we\u2019ve got to modernize. Usually sometime on the Monday morning after you go live, you realize this thing needs to be modernized immediately. We tend to use it like a blanket over a rhinoceros. You\u2019re trying to hide something far bigger, far more complex and far angrier than what would be obvious.<\/span><\/p>\n People tend to think of mainframes as legacy technology. We have access to a brand-new mainframe \u2014 there\u2019s no need to modernize it. So when you use the term \u201cmodernization\u201d in concert with \u201clegacy,\u201d you really have to ask the question, what\u2019s under the blanket? If you have a contemporary piece of hardware, with contemporary operating systems, contemporary development languages, what you\u2019re really talking about modernizing \u2014 probably \u2014 is the skills needed to support it. It\u2019s usually a people problem, not a technology problem.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":" John MacMillan, Pennsylvania CIO It\u2019s based on the idea that the minute a service or a system or application goes live, it\u2019s immediately legacy. Now you start into productive service and realize all the things you didn\u2019t think about are like warts on a toad: they\u2019re plainly obvious and now we\u2019ve got to modernize. Usually […]<\/p>\n","protected":false},"featured_media":0,"template":"","meta":{"disable_grayscale_images":true,"grayscale_contrast":0,"sponsored_content":false,"display_author_bio":true,"footnotes":""},"tags":[5081],"authors":[4696],"class_list":["post-45392","bio","type-bio","status-publish","hentry","tag-digital-transformation","author-colin-wood"],"yoast_head":"\n