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.
Every time you switch contexts, you lose the thread slightly. It’s human nature. So the less you do, the better.
I read somewhere that Eastern mathematicians tend to solve a different kind of mathematical problem than Western mathematicians do.
You Ain’t Gonna Need It means Do what you want, but don’t say I didn’t warn you. Just kidding. Not really.
It’s very easy to mess up with object names in SAP. I recently found a way to minimize that problem: set rules to fix per-package prefixes for certain object types.
Did you know that you can finally make radical changes to a development without fear because there is a simple way to undo all those changes?
OO exceptions always need a parent. They always have to inherit from somebody. And ABAP gives them 3 alternatives.
In SE24 the class code is partially hidden from the programmer behind a GUI. This is apparently convenient but ultimately limitative.
When a program is bad because it has duplicate code, it usually becomes shorter once we rewrite it to make it better. But, if its problem is not being properly structured into several classes and methods, if we rewrite it according to the best practices, it will probably end up longer.
Please stop. Too many regressions happen because someone forgets to CLEAR or to not CLEAR a variable.