How can you, as a JDE World developer, help your organization through this time?With the news changing every day and more and more companies pressing pause on projects, you may find yourself with some extra time on your hands. So, what's a self-motivated JDE/RPG developer to do? We have a few ideas of how to help yourself and your organization get through this pandemic successfully.
We all know that JDE World runs on the IBM platform, and a lot of you World developers still call it AS/400. But you know that the AS/400 doesn’t exist anymore, right? That platform has been gone for a very long time. Since 2008, you’ve been working on IBM i, an integrated operating system, database, and middleware that runs on the IBM Power System hardware platform. So, when you say you’re an “AS/400” person, what you’re really saying is “I work with IBM i but I’m stuck in the past.” With a newly cleared schedule, start getting into the habit of using IBM i.
What new tools or processes have you been meaning to explore? Now is the time to get familiar with some updated technology or integration tools.
Hear us out: you're working in the 21st century, shouldn't you be using a 21st century development tool? RDi gives you a modern environment for writing RPG code, letting you modernize your system while maintaining traditional RPG, COBOL, C, C++, DDS, and SQL applications, as well as extend those with services and applications using other technologies. Why not give it a try? You might be able to help your company further connect some of your business processes.
Now is a great time to take a look at XML integration and how you can pass data back and forth from JDE World. Even if it sounds like a distant dream for your system, XML integration is a very real process that people are using today. Take this opportunity to sit with the web team (well, virtually or socially distanced at least) and learn how they do things. Getting your head outside JDE World a bit will open you up to new opportunities for data communication on the system.
How often do you write the same SQL queries over and over again? If you have the time to learn, why not explore SQL stored procedures? With a stored procedure, you simply call the procedure to execute it, instead of writing it for the thousandth time. Our team uses stored procedures to build any custom business logic that accesses another table and is used in many programs. Stored procedures are more efficient, keeps business logic consistent, and promotes stronger security, so take a look at your system and see where stored procedures may make sense.
As a member of the development team, you know how JDE World works better than anyone else in the organization. How can you use that knowledge to help improve how your company runs? While everyone may have some free time on their schedules, talk to business process owners about what they do and how they do it. You never know where your technical expertise can help alleviate some of their pain points.
As a JDE/RPG developer, you've probably had to tell people more than once that "we can't do that." Instead of focusing on what won't work, now is the time to turn that statement around and instead ask, what can we do? How can you generate new revenue? What are some new ways to solve old problems? Find new and creative ways for your company to survive during this trying time.
Along similar lines, it's important to stay open to new ideas, integrations, and technologies. Like we talked about with XML integration, storing web data in JDE World is not a bad thing. Selling online is real; companies have to sell on the web these days. That means that you have to be able to communicate data to and from JDE World in real time, not batch. How can you achieve that with your system?
Let's be honest here, most people's World documentation is not great. What better time to work on fixing that? From the highest levels down to the nittiest of gritty, take a look at all of your documentation. If you or a member of your team is looking to retire in the next few years (or even months) how hard will it be for someone new to figure out what's going on? And before you say, "it's documented in the code," why not follow the Boy Scout motto: leave it better than you found it. The best way to do that is through documentation.
The focus here should be on functional documents. Explaining why you've done something is often more important than how you did something. Now, this means opening up a Word document and putting words to page. We know it's scary, but it will be worth it. And for extra credit, why not consider a diagram of your data flow?
Look, we know you became a developer partly because it guaranteed you wouldn't have to talk to people all that often. But as a member of the JDE/RPG development team, you've likely been around your organization long enough to know what's going on in your company. While other team members may be scrambling and afraid for the future, why not be a leader? You can navigate through this challenge and help guide your business through to the other side.
So, what do you think? Are you ready to tackle some of these challenges? Even if you only have the bandwidth to handle one right now, that’s better than none. As the next few weeks unfold, use this opportunity to prove to your organization what an invaluable resource you are. It will help both you and your company move through this crisis as unscathed as possible.
No Comments Yet
Let us know what you think