Certainly, large objects in text format are nearly impossible to discern. They might get cut off in the logs as well. Which then leaves only the option of printing properties.

Because I mainly develop SNow code outside the plaform, my preference is for viewing entire objects rather than the parts. This is purely for inspecting relationships to visualize strategy. This, of course, is easier in forms than in logs. The larger the object the more I want to see the overall structure.

In all, I prefer to:
1. Print whole JSON string to the logs when possible.
2. Grab and paste it in a JSON formatter to inspect.
3. Side by side comparison of code and JSON string.
4. Only if I'm "pseudo coding" are properties printed or/ print critical properties when debugging.

Printing properties then highlights "log management"? How can logs become an useful tool tool, rather than a hindrance. I worked for a company that rendered logs in all of their instances useless by printing unnecessarily.  Perhaps that can be another subject, if you already haven't, that you can write about?