Quick study sessions to strengthen memory and retain key concepts.
Why might not all fields have setters in a class?
Some fields are immutable or derived, not needing external modification. Not all fields in a class require setters,…
View Card →Why are domain-specific methods preferred over generic setters?
Domain-specific methods encapsulate logic and maintain business rules. Domain-specific methods encapsulate the logic necessary for a particular operation,…
View Card →Why use private fields with public getters in Java?
Private fields with public getters protect data while allowing controlled access. Using private fields and public getters is…
View Card →What are the pitfalls of using generated boilerplate for getters and setters?
It may lead to unnecessary exposure of fields. Generated getters and setters can expose fields that shouldn't be…
View Card →Why prefer domain methods over generic setters?
They encapsulate behavior and maintain business logic. Domain methods, like 'applyDiscount()', encapsulate specific behavior and ensure that business…
View Card →Why might not every field need a setter?
To maintain control and integrity of the object's state. Not every field needs a setter because it might…
View Card →When is it appropriate to use getters in Java?
When you need controlled access to a private field. Getters provide a way to access private fields safely.…
View Card →Why is controlling field visibility important?
To protect the internal state from unintended modifications. Controlling field visibility is crucial for maintaining the integrity and…
View Card →How does encapsulation relate to object responsibility?
Encapsulation ensures objects manage their own state and behavior. Encapsulation ties closely with the principle of object responsibility,…
View Card →How would you explain a pitfall of using public setters in a domain model in an interview?
It allows external code to modify the object's state arbitrarily. Public setters can lead to inconsistent or invalid…
View Card →