nothing wrong in doing things the old / analogue way but pharo offers a variety of tools to help you visualise and understand code.��
One example is when you want to know how one class is a subclass from another. Browser has a separate view for this called Hierarchy view.��
Another is when methods are get overriden either in the class you currently viewing or in a subclass, browser has special icons to inform you of that.�� Clicking on those icons will send you to the overriding methods.��
If the method has a test you can use as an example there would be an icon for it too, clicking it will run the test for you.
What if you see a method used and you want to look into its definition ? You can use the browser to do that or your printer paper but right clicking on the method and going directly to its definition is way faster also it will show you what other class defines such method.
Then of course you have the finder tool that allows you to search using just a few letters methods, classes and source and even allows you to provide an end result and gives back which method can produce that end result etc
The bottom line is that there are many pharo tools at your disposal and they are extremely powerful.��
There are also a lot of third party tools as well, for example if you want to create a diagram of the algorithm of an application / package you can do that using Roassal.��
So I would say for time being stick with Pharo learn the tools and if you are not happy then print code and use your pen to create diagrams of its logic.��