In every OOP language, it's good practice to enforce that objects have always valid state and in this example a Student missing first name, last name or student number would probably not be considered valid and constructing such an invalid Student should fail fast. Having Yoda style code instead feels unnatural and is difficult to read. But there are always at least two different opinions on a topic. ;-)

resolved!

Description updated!

@jayeshcp check if you can close the issue!

true, in this case the presented solutions did't check for the case that student is null as well - so the .getFullName() will present an error on itself.

In Java, it's good practice when testing String equality to put the String constant on the left:

"John Smith".equals(student.getFullName());

...instead of...

student.getFullName().equals("John Smith");

This way, if student.getFullName() returns null, you'll get false instead of throwing a NullPointerException.

Thanks for good advice. Tryed my best to fix it.

Please correct spelling mistakes