Sometimes it’s useful to look at two areas of the code at the same time. If the areas are in different classes, just open them both. But what if they’re in the same class? For example, if you want to make a method inspired by or related to another.

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.

Until recently, ABAP has never been one for big collaborations.

ABAP Doc is an excellent way of integrating documentation into the code.

Eclipse ADT calls it Code element information.

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.