Once I googled it, I saw it was quite an old-school system, but I understood it was still doing a lot of important work and still processing a lot of transactions daily. But it seemed that the actual interface was very dated and hadn’t changed much over the years. I wasn’t that excited about it to be honest, but I guess the retro, novelty feel was intriguing for me.

Q5. How did these expectations compare with the reality of working with the mainframe?

It was a new experience for me. There were definitely plenty of things to learn and it felt like I was acquiring a niche skill, which in some ways is good because it means you’re learning something not a lot of people know. But it was always restrictive and slow to use the old screens. It felt like you could be doing things a lot quicker but were held back because of the old green-screen interface. It was a lot harder and a lot slower compared to working with other languages I’d used.

Q6. How did you overcome this challenge? It must have been very hard.

For me it was just a case of getting used to it. I’ve worked with quite a lot of mainframe developers now, and after years of using the mainframe they really hone their skills and can zap around pretty quickly. But I think compared to using another, more modern interface, the old mainframe screens are really slow and restrictive, and you just kind of have to get used it.

Q7. What do your friends who are also developers generally think of the mainframe?

Most people I speak to haven’t heard of it or laugh if I tell them I work on the mainframe. People often say, “Oh, do companies still use that? Is that still around?” I think people who don’t work with the mainframe don’t have the most positive view of it sometimes, just because it has been around for so long. But I think a lot of developers who do work with the mainframe are aware that it is actually really important, and its size and potential is quite incredible. So, there are different views of it, but I think young, modern developers who don’t know how to use it tend to laugh.

Q8. What would you tell them to convince them of working on the mainframe?

You need to be using an IDE rather than just a green-screen emulator. Otherwise, it feels so different and slow compared to the new stacks you could be working on. It needs to feel exciting and modern. That’s what my peers are interested in working with—stuff that’s interactive. That’s the key to getting people on the mainframe.

Q9. Besides upgrading their tools, what advice would you give to IT managers for attracting and retaining next-gen mainframe developers?

Well, tools are a big part of it. Now that I have used the mainframe through an IDE, I would be really unhappy to go back to using the old green screen again. But I think also its understanding the importance of the mainframe. It really is a key part of a lot of enterprises. The majority of code in the world is written in COBOL, and the mainframe runs COBOL, so it’s still the most important computing power in the world. If you understand you work on a system that is this important, that’s a big part of it for attracting my generation. We look for jobs that are interesting where we can understand the relevance of what we’re doing.

Q10. Where do you see the mainframe headed?

One of the things I noticed, looking into the mainframe’s history, is that again and again people have prophesied its death, saying that in 10 years it won’t be used anymore. But I’m sure it will still be here. It’s still very significant, and a large number of companies are still heavily relying on it. But also, advancements such as the Internet of Things are going to produce hundreds of terabytes of new data, so a system like the mainframe will be crucial to processing that volume. I don’t really know what will happen, but I definitely wouldn’t want to be another person wrongly prophesying the mainframe’s end!

2 Pages