You’ve been asked to create a new feature. You’re ready to build it. But hold your horses. Before you start, I suggest you find answers to a few questions. Finding a good answer to each of them is fundamental to ensuring that what you build is solid and elegant.
In my current project constants are all over the place, with confusing or wrong names. It’s a mess. I’ve found a way to reorganize and rearrange the constants so that the new code can use pretty constants without messing up the old code, which can continue to use the confusing ones.
There’s nothing worse than seeing people abusing variables. They’re so delicate and yet so badly treated, poor things. Here’s a way to show them some love.
Everyone uses blank lines to better organize their code. But where to use them and how many? Let’s talk about that.
Sometimes you need to take data from the database and replicate it declaratively in ABAP using the VALUE command. For example, to build ABAP Unit tests.
Historically, it has always been impossible to jump from one SAP system to another without losing context. Now it’s possible.
The tools that SAP provides for viewing the contents of database tables have always been very sketchy.
They say: Don’t go back to where you were once happy. But the truth is that in many cases, if you could go back, you would.
I like keyboard shortcuts. If I could do my job without taking my hands off my keyboard I’d be an even happier programmer.
Those who still programme monolithically probably don’t feel the need for this. But anyone who uses multiple classes with multiple methods knows that it’s normal (and even desirable) to change your mind about the name of these things. Ideas aren’t born ready-made in our heads. Ideally, code is mouldable and can be shaped until we find the desired form.
