Why getter/setter/toString()?

Use encapsulation/concealing concepts to restrict access to objects.

Getter/setter is often used to limit direct access to specific data and to modify data through specific methods (public). In my case, I try to refrain from using getter/setter as much as possible, but it's not easy.

There seems to be a lot of debate about this. I think it would be better to establish your thoughts by reading many articles.

It's similar to my thoughts on getter/setter, but I think it's well organized. http://lacti.me/2011/10/03/getter-and-setter-at-java/

There are many reasons for toString() overloading, but the biggest reason is that it is the easiest to express information about an object. If you did not override the toString(), the address value would be stamped. There is a limit to checking the information about the object only with that address value. If you use the output function, it's annoying because you have to set it up one by one.

I want to know the fundamental reason..

http://javahome.tistory.com/entry/Effective-Java-%ED%95%AD%EB%AA%A9-10-toString-%EB%A9%94%EC%86%8C%EB%93%9C%EB%8A%94-%ED%95%AD%EC%83%81-%EC%98%A4%EB%B2%84%EB%9D%BC%EC%9D%B4%EB%93%9C-%ED%95%98%EC%9E%90

It's from a book by Zabyfective. Please refer to