Recently, I sat down with a team of veteran IBM i developers who had just completed their first month of using modern DevOps tools. “It’s like learning a new language,” one developer told me, mixing frustration with pride. “Challenging, but once things click, you wonder how you ever worked differently.”
This conversation echoes what I’ve heard from many IBM i teams transitioning to modern DevOps practices. Let’s explore the real challenges and benefits of this journey.
The Pros: Why It’s Worth the Effort
Automated Change Tracking: With open-source DevOps, you can automatically track who changed what code and when, eliminating the need for manual source comparisons or embedded code comments. You can easily search and view changes by task, developer, or date range with just a few clicks.
Enhanced Collaboration with the Rest of the Team: When IBM i developers master open DevOps tools, they can finally collaborate seamlessly with the rest of the organization. After all, over 100 million developers are currently using these tools. IBM i teams can move from isolation to full integration with the company’s development ecosystem, using the same tools and technical language as their colleagues.
Increased Development Speed: Once developers become comfortable with tools like Git, they can:
- Using Git’s powerful merge functions, multiple developers can work on the same code simultaneously without worrying about losing changes or waiting for others to finish.
- Developers can make changes confidently, knowing Git tracks every modification with sophisticated version control.
- Deploy more frequently with automated processes (no need to create objects and deploy code manually)
- Spend less time on manual tasks and more time on valuable development: By making changes easily visible and automating create and deployment processes, developers are free to spend more time developing new capabilities.
Career Growth: Modern DevOps skills make IBM i developers more valuable to their organizations and the industry as a whole. One developer recently told me, “Learning these tools opened up conversations with other development teams I never had before. I’m not just ‘the IBM i guy’ anymore.”
Better Code Quality: Modern DevOps practices introduce:
- Automated testing
- Code review processes
- Quality gates and approvals
The Cons: Real Challenges to Address
The Learning Curve: Git works differently from traditional IBM i tools. IBM i developers need to learn:
- Git concepts and commands
- CI/CD pipeline concepts
- New terminology and processes
Life will Change: After decades of using familiar tools and processes, some developers naturally resist the switch to something different. As one team lead shared, “My most experienced developer initially refused to use Git. He’d been using the same version control system for 20 years.”
Temporary Productivity Dip During the Transition Period: Some teams experience:
- Slower development cycles during the transition
- More questions and confusion about Git, Build (create) and DevOps processes
- Increased need for support: They are no longer the experts
- Initial mistakes and setbacks
Integration Complexities: Connecting IBM i systems with modern DevOps tools can present technical challenges for staff members unfamiliar with multi-platform development
Making the Transition Work
Through our experience helping numerous IBM i teams adopt modern DevOps practices, we’ve identified several keys to success:
Gradual Implementation Instead of a “Big Bang” Approach: We recommend:
- Starting with a small project or team
- Gradually expanding adoption
- Allowing time for learning and adjustment
- Celebrating small wins
Comprehensive Training: Successful transitions require:
- Structured training programs
- Hands-on practice sessions
- Regular coaching and support
- Access to expertise when needed
Leadership Support Organizations Need to:
- Provide adequate time for learning
- Set realistic expectations
- Offer encouragement and resources
- Demonstrate commitment to the change
Real Success Stories
A manufacturing company we worked with recently transitioned its IBM i team to modern DevOps practices. Initially, there was significant resistance. However, after three months of structured training and support, the team deployed code twice as frequently with fewer errors. Their lead developer, initially the biggest skeptic of modern DevOps, became the strongest advocate for the new tools.
Looking Forward
The journey to modern DevOps can be challenging, but the destination is worth it. At Eradani, we’ve developed tools and training programs specifically designed to help IBM i developers bridge this gap. Our approach acknowledges the challenges while providing the support needed to overcome them.
For example, our DevOps solution allows developers to:
- Use Git commands from familiar interfaces like PDM, RDi, and VSCode
- Gradually transition from legacy processes
- Access expert support when needed
- Maintain productivity during the learning period
Learning modern DevOps tools can be challenging initially, but the benefits are real. With the right approach, support, and tools, IBM i developers can successfully make this transition and position themselves and their organizations for future success.
Ready to start your team’s DevOps journey? Let’s talk about how we can help make the transition as smooth as possible while maximizing the benefits for your organization. Contact us at Eradani to learn more about our DevOps solutions and training programs specifically designed for IBM i teams.
Remember, every expert was once a beginner. The key is taking that first step and having the proper support along the way.
