Separation of concerns between business layer, data layer and presentation layer without losing information
I’m developing an api in Fast API using sqlalchemy to manage my ORM classes and operations with the database.
Java OOP problem
I’m working on a Java programming assignment. In this assignment, there’s an immutable class Book
and a mutable class BookCopy
. You can have multiple BookCopy
of the same Book
.
Which approach do I choose for representing objects and scenes in my 3D drawing library?
I’m creating my own drawing library in C++ to provide shared rendering code for my projects.
Is it appropriate to create a getter interface to reuse the HTTP Request Param field? (ex: pagination, sort)
I’m developing a web API using Java Spring.
Why is “dependency injection” ok, but not “the opposite of preserve whole object (pass required parameters only)”?
According to Why should I use dependency injection?, “dependency injection” has some advantages, for example:
Is “parallel composition hierarchies” a code smell?
For example, suppose I have some mobile apps that uses some user data, the data class:
In “avoid primitive obsession”, what is the meaning of “make the domain model more more explicit”?
According to When is primitive obsession not a code smell? and answer in https://softwareengineering.stackexchange.com/a/365205, I know one of the advantages of avoiding primitive obsession is “make the domain model more more explicit”.
If class B extends A, can we say that B depends on A?
Let’s say we have 2 (Java) classes:
Mapping complex objects to other similar complex objects
I am working on two applications that serve the same purpose. The first application is more feature rich and its types are more complex, but uses old technologies and will be retired. It will eventually be replaced by the second application which is now lacking some of the features in the first application and (currently) has simpler types.
Best way in C# to share class implementation patterns between abstract base classes [closed]
Closed 3 days ago.