Debug discipline

In reply to verif_learner:

One of the issue I am facing currently in my code is that it is really sprinkled with a lot of uvm messages.
So much so that I have probably 1:0.5 ratio between functional code and debug messages.
I can definitely control the message using verbosity level during run time but my source code is still cluttered with a lot of debug messages.
I am just curious if this is anyone has good ideas to avoid this source code clutter?
For example, I can think of using some `define macros which may help to some extent.

I would suggest to get rid of all those messages and insert the proper comment/reasoning for the code. I have seen in various projects that messages added before and after every procedural statement.