If you are a developer, rather than a user, it is in your best interest to employ deep access rather than shallow access. Shallow access is more appropriate for users.

Avoid arguing that deep access is preferable than shallow access based only on performance considerations from the perspective of a developer.

In order to separate the functionality of the implementation from the data type it handles, the developer creates a class. In this way, functions and classes may handle data of any kind. corrupted file headers A design template may be thought of as a special kind of generic class that

The _____suggests splits interfaces that are very large into smaller and more specific interface so their clients will only have to know about the methods that are of use to them. (SRP, OCP, LSP, or ISP?) The Single Responsibility Principle (SRP)The Open-Closed Principle (OCP)The Liskov Substitution Principle (LSP)The Interface Segregation Principle (ISP)The Dependency Inversion Principle (DIP)

From the point of view of a developer rather than a user, it is desirable to use deep access rather than shallow access.

From a programmer point of view, make an argument that supports the use of deep access rather than shallow access; Avoid an argument that revolves around performance

While we discussed the steps to define an interface for a class, we mentioned that that a class interface typically contains only methods and publicly accessible data fields generally cause problems. 1. Explain why this practice causes problems? 2. Explain two reasons for your statement.