ABAP
Blogs about my work with the ABAP programming language. Topics include design, best practices and real-life experiences.
-
Two pseudo comments on one ABAP statement
Reading time:
2–3 minutesPseudo comments are sometimes necessary. However, their placement isn’t always intuitive. Here’s an example.
-
Code, Comments, AI
Comments are no longer just for ourselves and our fellow developers.
-
Development objects ending in an underscore
Can the names of development objects end with an underscore? Yes, technically possible, but questionable from a professional standpoint.
-
Amazon Q Developer
GitHub Copilot, SAP Joule, and now Amazon Q Developer. More AI support for ABAP development.
-
Attributes, states and time
Reading time:
4–5 minutesA class does not need to have attributes unless there’s a specific reason for it.
-
Distinguish between the functionality and its implementing code
Reading time:
3–4 minutesIt’s easy to confuse a new feature with the code it requires. It’s important to distinguish between how the new feature is called and where it’s implemented. This article offers some insights on this topic, especially for those who want, for example, more readable and understandable customer extensions.
-
What you can find in an ABAP class
Reading time:
2–3 minutesIt’s unbelievable what you can find in a class. Nobody would expect that.
-
Mind Map using Markdown and AI
Reading time:
1–2 minutesMind maps using Markdown? Yes, please, right now!
-
The new public enemy number one: static code analysis
Reading time:
1–2 minutesStatic code analysis can sometimes be wrong. That’s no reason to ignore it altogether or even try to trick it.
-
My last “We love Formulare” podcast
Reading time:
1–2 minutesAll good things must come to an end. Episode #25 of the “We love Formulare” podcast is my last episode.