Quick study sessions to strengthen memory and retain key concepts.
What does it mean for a list to be unmodifiable?
An unmodifiable list cannot be altered after it's created. Returning an unmodifiable list prevents external modifications, preserving the…
View Card →How would you explain the danger of a class with too many responsibilities in an interview?
It leads to complex, hard-to-maintain code. A class with too many responsibilities can become overly complex, making it…
View Card →How does responsibility-driven design prevent confused objects?
It ensures each class has a clear, singular purpose. Responsibility-driven design assigns specific roles to each class, avoiding…
View Card →Why should behavior be kept with the data it operates on?
Keeping behavior with data ensures that related operations are encapsulated together. This practice minimizes the risk of data…
View Card →Why can exposing an object's internal list become a real problem?
Exposing an internal list allows external modification, breaking encapsulation. When a method returns an internal list directly, it…
View Card →How can validation logic be misplaced in object design?
Validation logic should reside within the object responsible for the data. Misplacing validation logic can lead to code…
View Card →What does it mean for a class to have an invariant?
A class invariant is a condition that holds true for an object's state throughout its lifecycle. Class invariants…
View Card →Why should class fields typically be private?
Private fields prevent direct access, allowing control over how they are modified. Using private fields ensures that an…
View Card →Why is anemic data models risky in production code?
Anemic models separate data from behavior, leading to procedural rather than object-oriented designs. Anemic models are characterized by…
View Card →How does immutability contribute to safe object design?
Immutability prevents changes to an object's state, which enhances thread safety and predictability. An immutable object cannot be…
View Card →