Rewrite an old Java C++ installer with a code agent in three days

What was done

According to the case study published by IBM on 20 August 2026, the installer of the MICC suite, about ten years old, was dependent on Java 8: the tool loaded with updates prevented the Java environment from being updated. The team of six developers, specialized in Java and Python, chose to rewrite only this installer, in C++, so that it works without Java virtual machine while keeping the same behavior for customers. Method followed: plan, implement, validate. IBM Bob analyzed Java code, proposed a C++ project structure and mapped dependencies; the developers approved the approach before the generation of the code. They then reviewed the implementation, reviewed the security sensitive functions and reused the existing tests. A synchronization problem with the MICC manager was diagnosed with agent help.According to IBM, a developer completed planning and generation in less than a day, and migration took a total of three days, compared to several weeks planned.

Before you start

Tool cited by the source: IBM Bob. Gather the information the prompt asks for. Strip confidential data that is not needed and check your tool’s access terms. Features and plans can change.

The method, in three steps.

1. 01

   Gather the context

   Gather the information described in the prompt.

2. 02

   Adapt the prompt

   Copy the prompt below, replace the bracketed items, then paste it into the AI assistant you use. The cited tool (IBM Bob) is not necessarily available to the public..

3. 03

   Reread before using

   Reread the result, correct it if needed and keep the final decision. Caveats are detailed below.

Your starting point.

Replace the bracketed items, then adapt the proposal to your situation. This prompt is written by the iadujour desk It is not a quotation from the source.

Here is the code of a program to migrate from
Behavior:

1. First proposes a plan: structure of the new project, correspondence of dependencies, delicate points (security, competition, system path).
2. Wait until I agree before generating the code.
3. There list the existing tests to play again and what they do not cover.

What deserves your attention