In The Spotlight
For decades, applications were built using traditional programming languages like FORTRAN, COBOL, BASIC, and C, coupled with a “Waterfall” methodology where each project was broken into a linear set of phases (like design, development, testing, and deployment) that were completed sequentially.
By Roger Sanders
Over time, the languages and methodology changed, but the process remained the same: programmers wrote text-based code, compiled it, and executed the resulting application to test what they had written. (If an interpreted language like BASIC was used, the compilation step was omitted.) However, data science, machine learning, and statistical analysis demand a very different approach to software development—one rooted in rapid experimentation, human-language explanation, and visual validation that can tell a story with data. Jupyter Notebook provides an interactive canvas that makes this type of storytelling possible.
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online