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.

When you have a very large method, you should subdivide it into several smaller ones.

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.

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.

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

Eclipse ADT calls it Code element information.

Did you know that in Eclipse ADT you can work even without a connection to the server?

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.

I read somewhere that Eastern mathematicians tend to solve a different kind of mathematical problem than Western mathematicians do.