ABAP systems form the backbone of the daily business of a large number of medium-sized and larger companies. Their main characteristic is therefore longevity: ABAP systems must be adapted to changing and evolving economic and legal requirements over years, even decades. Sharp and unstoppable declining productivity when expanding such business-critical ABAP systems is a no-go.
Such a situation is frustrating for all stakeholders and not economically viable. All alarm bells must go off for management and customers. Unreliability and dragged out delivery with massive quality defects are a recipe for increasing conflicts and chaos.
“Software is eating the world!”, Marc Andreessen
Every company today is a software company in that its existence is fundamentally dependent on software. Car manufacturers are almost proverbial producers of computers on wheels, which are moved less by fuel and more by millions of lines of code. The same applies to medium-sized companies in mechanical engineering, trading companies or pharmaceutical corporations. If software is not in the product, then it at least permeates the processes of the company.
And if software can be said to eat up the world, then it is SAP with ABAP that has managed to become the carrier of the genetic code of countless companies.
How ABAP can be used to adapt SAP to the challenges of the future is therefore essential for every SAP-oriented company. SAP is critical to the system, ABAP is the key to SAP. The fact that every ABAP application is designed to be future-proof is an absolute prerequisite for the survival of the company in a VUCA world.
It is not to be expected that ABAP systems will be future-proof “just like that” solely because developers are driven by a more or less strong will to do so. Good will alone achieves hardly anything – or even the opposite. Rather, it requires a concerted, systematic effort from the very first day of development in various respects including:
- A systematic development process
Sustainability is a requirement for software like functionality or performance. It only is created when intention and ability consistently come together.
Paradoxically though, intention and ability to be future-proof are still weak in ABAP development. Customers and management place so much emphasis on short-term productivity with regard to functional and non-functional requirements that long-term productivity is repeatedly lost sight of – and once you realize this, it is almost too late for a change of course and culture.
The principles and practices relevant to sustainability are hardly part of the training of ABAP developers and are not made up for in day-to-day business. This is contrary to the necessity companies are increasingly feeling: the ability to change from strategy to operation is the sine qua non for survival in the marketplace. Of course, this requires more than adaptable ABAP code – but without adaptable ABAP code, all other ideas of change in SAP-based companies are nothing.
The path to increasing the adaptability of ABAP systems can therefore not be taken a day too soon. The development team and ABAP system reflect this through
Getting ABAP teams on the road to systematically produce clean code is the motivation behind Clean ABAP. While for other programming platforms the train to sustainability in development has been in full swing for a long time, in the ABAP world it is still largely in the station. We want to change that! The ABAP/SAP platform deserves to be served with specific training on the subject of clean code in accordance with its importance. Because without an ABAP-focused presentation and ABAP-specific support, ABAP developers cannot be expected to quickly adopt the necessary quality-oriented culture.
Clean ABAP therefore offers its trainings exclusively in the form of complementary courses with two trainers: Damir Majer is a proven ABAP expert and Ralf Westphal is a pioneer of the Clean Code movement in Germany since 2009.
As a trainer team we are offering
- highly individual support even with a larger number of attendees for intensive learning,
- two perspectives on training content for different types of learners,
- deep competence in technology vs. method,
- a broader “target” for questions, and
- diverse didactic as well as methodical approaches for lasting attention.
All trainings are scheduled for a duration of 4 days in order to be able to present and discuss concepts in a stress-free way, but above all to practice methods and practices in depth. Each training concludes with a “masterpiece”, i.e. a more extensive task that the participants solve and present on their own “according to the rules of the art”.