Let’s take a ride into the danger code. Does your company still utilize homegrown legacy apps, those that were written “in house?” Yes? Well, then it’s time to do something about that old risky COBOL-esque language, to put it out of commission. Barring that, you’ll face an altogether different kind of problem, that of keeping the risky code up to date. According to an article by Minda Zetlin for The Enterprisers Project, you’re going to need a maverick programmer. She muses:
[It is a common] concern facing a growing number of companies as the Baby Boomer generation of IT marches steadily toward retirement. “How do you deal with the fact that your human capital has a lifespan?”
Four Top Strategies
- Procure backup talent.
First, one must take stock of all the outdated applications with supporting information. In this scenario, size really does count, and knowing how large the problem is comes first. You’ll want to avoid customization, of course, since that’s exactly the kind of software you’re trying to replace. Off-the-shelf, from-a-vendor, software-as-a-service options are preferable.
Additionally, nobody really wants to document their software creations. But if you must keep a homegrown application, it really matters if you keep supporting documentation handy to maintain or change the code. This is especially important if you and your team don’t expect to be with the company forever.
Aside from just having documentation, you might want to ensure the proximity of staff that are knowledgeable about the code, or perhaps contractors who know how to deal with it. In the case that something goes wrong, you’ll want someone or some team to come to the rescue.
Read the original article here: https://enterprisersproject.com/article/2015/6/danger-lurking-your-code