In Eclipse ADT you can always undo
![images/thumbnail.jpg - Thumbnail](/en/2024/06/eclipse-adt-undo/images/thumbnail_hude90c15e0941e2b8d2d5a69eff4bf404_83653_300x0_resize_q75_box.jpg)
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.
Eclipse ADT has lots and lots of keyboard shortcuts
![images/thumbnail.jpg - Thumbnail](/en/2024/06/eclipse-adt-keyboard-shortcuts/images/thumbnail_hu88abb608e43828239fd92e12114da8fd_21810_300x0_resize_q75_box.jpg)
I like keyboard shortcuts. If I could do my job without taking my hands off my keyboard I’d be an even happier programmer.
Rename a lot of things automatically in Eclipse ADT
![images/thumbnail.png - Thumbnail](/en/2024/05/eclipse-adt-rename/images/thumbnail_hu182deac55a27fbf8dae0dc7f62e94095_76598_300x0_resize_box_3.png)
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.
Eclipse ADT puts ABAP Doc to good use
The magical F2 in Eclipse ADT
No constant context changes in Eclipse ADT
![images/thumbnail.jpg - Thumbnail](/en/2024/04/eclipse-adt-mudanca-de-contexto/images/thumbnail_hu5a3da1b95a5882c17452da3ef9973c62_119706_300x0_resize_q75_box.jpg)
Every time you switch contexts, you lose the thread slightly. It’s human nature. So the less you do, the better.
In Eclipse the compiler is not lazy
Languages shape thought
![images/thumbnail.jpg - Thumbnail](/en/2024/02/linguagem-molda-pensamento/images/thumbnail_huf1d6740ebbda870f9327e7478e6570b2_78945_300x0_resize_q75_box.jpg)
I read somewhere that Eastern mathematicians tend to solve a different kind of mathematical problem than Western mathematicians do.
To all those whole criticize 7.4 syntax
![images/thumbnail.jpg - Thumbnail](/en/2024/01/nova-sintaxe-complicada/images/thumbnail_hua0fb79fe1ef0ce50de699c232bc3e98e_45910_300x0_resize_q75_box.jpg)
This post is addressed to the collective character that represents all the people who have told me that they like some things in the new 7.4 functional syntax but think that you shouldn’t overdo it and should avoid using REDUCE
and all the other unnecessarily weird things because the code gets more obscure, it’s slower and they don’t see any advantages.
Are you serious?
Use BASE to not ruin what you already have
![images/thumbnail.png - Thumbnail](/en/2023/11/base/images/thumbnail_hu6ac8c219a514c622d2e5308bc049b0bf_165548_300x0_resize_box_3.png)
We used to use the APPEND
and INSERT
commands to add rows to internal tables. Now that ABAP has grown, we can use VALUE
, REDUCE
, CORRESPONDING
, etc. But what if the internal table already has rows and we don’t want to lose them?
INNER JOIN instead of FOR ALL ENTRIES
![images/thumbnail.png - Thumbnail](/en/2023/10/inner-join-itbl/images/thumbnail_hu65b170ae42d65d50954a6ce1bf521d4b_721865_300x0_resize_box_3.png)
A while ago I showed you that you could SELECT from an internal table. And then I asked myself: if that is possible, shouldn’t INNER JOIN be possible too?