Keeping an eye on the future, SAP has made significant investments in the AI space, and Joule is a prime example of how the investment is paying off. The first thing to understand is that AI is going to stay and being relevant in the present world would need AI relevance as well. Next thing, the developers need to understand that Joule is not going to replace coders; it’s a tool and operates just as well as the operator who uses it. These are realities of modern times, and soon, old school programming will be ancient history in SAP space.

SAP envisions Joule as a tool to accelerate solution delivery, leveraging pro-code and low-code effectively, bridging the gap between changing business environments and the time taken to build solutions for dynamic businesses. Joule caters to almost the entire SAP Dev ecosystem, covering Build and ABAP while ensuring SAP-recommended patterns are also accommodated. Demos and usage experience suggest that Joule focuses a lot on simplifying non-productive, easy-to-regenerate portions of development, giving tools to developers to explore more critical pieces of logic development.

Joule also does a fairly good job in explaining code pieces – legacy code or code written by peers – which is a great asset for junior developers when expert guidance is not available. This can help developers notch up their skills. Senior developers can use these capabilities to reduce the time spent on understanding volumes of legacy code for a relatively low throughput. Imagine reviewing 3000 lines of legacy code to understand high level requirement versus reading a summary of the same in the course of sharing analysis for simplification.

With Joule’s context awareness and scalability capabilities, SAP has shown enormous trust in the potential in AI innovation powering faster transformation and clean core compliant modernisation. In the next post, I will share key highlights of SAP Joule for Developers.

~S