[leibnizwasright]

I have the understanding from experience that people will always give a reason for doing something that I could not imagine.

So 1st, make questions, understand what is the objective with that code you see on screen. 2nd, make more questions too see if other use cases were considered.

3rd, there are best practices, literature that provide a common way of working, discuss how to apply this.

There are no ways of understanding without making questions.

On this specific case, besides the lack of OO design knowledge, there were also a misunderstand on the page object pattern , how web apps are build and what is the web app and what is part of the browser.

And this is why I also talk with my team on my ideas to develop something before or while developing it. It should not be a surprise, no matter how nice and commented the code is.