I would have the opinion and good practices in script programming about using print statements to materialize the control flow (I usually use an anchor mark, then the name of the function just entered, and eventually the step number in the control flow). I usually then print crucial variable to check if all is going well, and I am pretty explanatory there too, naming each variable before printing its value.
Is it ok to do this way (at least in scripts that are not made for production)? I must say that I use this even more than comments (I usually only use comments to explain what is a variable, why it should be that type or use a method instead of another, or to unravel things that could not be so obvious after three months far from the code).
Is it ok, or should I be less verbose, and more rely on comments. It's an habit I had since I have been coding using OOP, in order to clarify the flow and help me debug, but actually that might be a bad personal preference.
(I don't think this question duplicates this one: Should code comments explain the control flow?)