How to re-direct my career into mainframe modernization?

This is probably the most asked question to me by entry to mid-level developers. However, there is no straightforward answer to this. Most of you, who had joined the IT workforce as a mainframe developer in recent years, may have opted for this due to a lack of other choices. So, for some of you, mainframe modernization may sound like an escape route to a better and more sophisticated career. 

If I look back at my journey, I admit that I was lucky to be part of projects that involved modernization. I did not realize the value of such projects initially. Over time, with guidance from many of my mentors and well-wishers, I got to know that some of them were first-of-a-kind and progressive projects in terms of what the customer’s competitors did. 

If I were joining the IT workforce today as a mainframe developer, after knowing what I do now, I would follow the below re-direction path and suggest the same for the audience.



Evaluate:

Understand the roadmap of your current project and the application you work on specifically. Try to find answers to questions like: 

  • Is the application going through functional changes? 
  • Is the application planned for sunset in the coming years? 
  • Are there any modernization activities happening already in the application?
  • Is the application critical to the business?

These questions can be answered by your project manager, application architect, business analyst, product owner or technical leaders of the application.

Ask for modernization work:

Once you know the answers to the current state of your application, request to involve you in modernization activities for the application. If there is none, ask for a switch to a modernization project instead. 

 You can also consider requesting a change in technology if modernization projects are not available. This will mean you may not work in mainframe modernization though.

Ask for a pattern change:

If you are already working on a modernization project, you may become a "specialist". It is also important to explore other patterns of modernization and not stick to this specific pattern only. Ask for a shift to another type of modernization project to expand your horizon.

Build  a network:

While it is impossible to work on all patterns of modernization, it is important to understand them. Your professional networks and learning skills will help you achieve that. This gives you the confidence to work on any given pattern. Remember, information exchange is mutual. You share as well as receive. The network you create would be strong when there are contributions from all sides.

Note: The views expressed here are based on my experience and are neither exhaustive nor may be in line with definitions of modernization available in the market.

Comments

Popular posts from this blog

What skills to develop to become an architect?

What resources are available for learning?

Do I really have career growth if I continue in mainframe projects?