My advice is to use the Advisor

I have noticed (too) often when talking to other APEX developers, that the Advisor functionality is not well known.

Although this is also described in a lot of Best practice  guides, the functionality is in my humble opinion highly underestimated!

The APEX Advisor

I actually don't know how long it's been there, but it is quite some time.

And it's all standard and included in the APEX Application Builder.

It is to be found under Utilities.

It kicks off following popup window

I recommend to have a look at the section Checks to perform:

It may well be possible that you have opted for whatever reason to not follow one of the pre-defined rules of the APEX Development team. You can chose not to check on those rules.

Usually I advice to select all checks and read the advice of the Advisor. You can always opt of course not to do anything with one of the remarks. Because one thing must be clear: your app can run very fine with several Advisor errors or warnings in it. You do not need to fix them all. But it is advised to solve as many as possible and you may learn something from the best practises according to the APEX Development Team. They're smart people ... believe me ;-)

Depending how large your app is - of course - running the Advisor may take some time.

In the end it provides you with a clear overview and with the option to navigate directly to where you need to be to fix the problem.

The result filter

The filter comes in very handy to keep an overview or to focus on one specific type of error (or warning).

An advisor error

I'm not walking you through every possible error an Advisor can identify. 

For each error/warning the Advisor will give you an overview of what he thinks is wrong or can be done better.

With the View button you navigate directly to the place in your application that concerns this hit.

He doesn't know everything

An example of errors an Advisor run is always indicating is the following:

What the Advisor cannot see here, is that this "EVENT_LINK" is part of a specific template. It's not necessarily a real error. So these errors can be ignored.

So okay, here you go. Hope to have convinced some developers to start using it. It's really a good practice to run it at the end (or beginning if you prefer) of every working day!

Happy to share ....