I know everyone loves CDSs and that it’s a sin to speak ill of them, but please let me get this off my chest.

Those who work in SAP think it’s normal for everything to be represented by obscure codes that mean nothing. But it doesn’t have to be this way. Stop it! Create human-readable codes please.

Did you know that you can set a starting point for ATC and, thanks to that, be able to run ATC in legacy code?

When a porcelain object breaks in Japan, sometimes instead of throwing it away, they mend it. But they don’t mend it just any old way; they mend it with gold. This technique is called Kintsugi.

It is a common practice in ABAP to use MODIFY instead of INSERT and UPDATE. Do you do it too? Tell me why. Is it laziness? Is it fear? Is it just a matter of “whatever”? Or is it more like “screw it”?

The broken window theory says that if a window in a building is broken and not repaired quickly, people will be tempted to throw stones and break the other windows.

In the ABAP world, the rule is to do it once and never touch it again. Once done, forever frozen. What nonsense.

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.

Every time you switch contexts, you lose the thread slightly. It’s human nature. So the less you do, the better.

Still using SAPGUI instead of Eclipse ADT? Get ready to be made fun of.